Bad bad Google! (and Microsoft!)

Hum… I used to think Google is definitely doing "No Evil" but now, I’m slightly less certain whether they will keep to their motto.
 
Why?  Well it all began when I’m trying to download the latest episode of CommandN and a torrent in the background that aren’t taking up all my bandwidth.  I fired up my BITS script (link) for the CommandN episode to see if BITS can use my spare bandwidth and not slow down my BitTorrent download and, to my surprise, saw the 2 extra entries below:
 

{0753610B-D279-44DA-A208-1DEF90639BC7} TalkDownload TRANSFERRED 1 / 1 896720 / 896720
{16AAECCC-539C-48C3-AFBC-867D36FBE451} TalkDownload TRANSFERRED 1 / 1 896720 / 896720

 
I then thought, "Hang on a sec. when did I create 2 BITS job with the name "TalkDownload" ?"  After a while of thinking, I decided to fire up bitsadmin and list the jobs current active in full.  I got this (Note the #### is output I’ve deleted for security reasons):
 

C:>bitsadmin /list /verbose

BITSADMIN version 2.0 [ 6.6.2600.2180 ]
BITS administration utility.
(C) Copyright 2000-2004 Microsoft Corp.

GUID: {0753610B-D279-44DA-A208-1DEF90639BC7} DISPLAY: TalkDownload
TYPE: DOWNLOAD STATE: TRANSFERRED OWNER: ####
PRIORITY: NORMAL FILES: 1 / 1 BYTES: 896720 / 896720
CREATION TIME: 09/02/2006 19:16:34 MODIFICATION TIME: 09/02/2006 19:16:58
COMPLETION TIME: 09/02/2006 19:16:58 ACL FLAGS:
NOTIFY INTERFACE: UNREGISTERED NOTIFICATION FLAGS: 3
RETRY DELAY: 600 NO PROGRESS TIMEOUT: 1209600 ERROR COUNT: 0
PROXY USAGE: PRECONFIG PROXY LIST: NULL PROXY BYPASS LIST: NULL
DESCRIPTION:
JOB FILES:
896720 / 896720 WORKING http://dl.google.com/googletalk/googletalk-setup.exe -> C:Program FilesGoogleGoogle Desktop Searchgooglet
alk-setup.exe
NOTIFICATION COMMAND LINE: none

GUID: {16AAECCC-539C-48C3-AFBC-867D36FBE451} DISPLAY: TalkDownload
TYPE: DOWNLOAD STATE: TRANSFERRED OWNER: ####
PRIORITY: NORMAL FILES: 1 / 1 BYTES: 896720 / 896720
CREATION TIME: 08/03/2006 01:15:17 MODIFICATION TIME: 08/03/2006 01:15:39
COMPLETION TIME: 08/03/2006 01:15:39 ACL FLAGS:
NOTIFY INTERFACE: UNREGISTERED NOTIFICATION FLAGS: 3
RETRY DELAY: 600 NO PROGRESS TIMEOUT: 1209600 ERROR COUNT: 0
PROXY USAGE: PRECONFIG PROXY LIST: NULL PROXY BYPASS LIST: NULL
DESCRIPTION:
JOB FILES:
896720 / 896720 WORKING http://dl.google.com/googletalk/googletalk-setup.exe -> C:Program FilesGoogleGoogle Desktop Searchgooglet
alk-setup.exe
NOTIFICATION COMMAND LINE: none

GUID: {739803AA-AAF8-4C90-B20D-EF7346B03479} DISPLAY: commandn
TYPE: DOWNLOAD STATE: TRANSFERRING OWNER: ####
PRIORITY: NORMAL FILES: 0 / 1 BYTES: 4276 / 178455180
CREATION TIME: 19/03/2006 00:04:28 MODIFICATION TIME: 19/03/2006 00:04:47
COMPLETION TIME: UNKNOWN ACL FLAGS:
NOTIFY INTERFACE: UNREGISTERED NOTIFICATION FLAGS: 3
RETRY DELAY: 60 NO PROGRESS TIMEOUT: 31536000 ERROR COUNT: 0
PROXY USAGE: PRECONFIG PROXY LIST: NULL PROXY BYPASS LIST: NULL
DESCRIPTION:
JOB FILES:
4276 / 178455180 WORKING http://206.51.230.104/EP37/commandN-37-XviD.avi -> C:####commandN-37-XviD.avi
NOTIFICATION COMMAND LINE: 'C:####Jobscommandn.bat'

Listed 3 job(s).

 
Ok… so it’s from Google – which is a relief as I though something bad has happened to my system….
 
Out of curiosity, I then did a directory listing in my GDS installation folder and gotten the 2 entries below:
 

07/02/2006 18:10 896,720 BIT2.tmp
28/02/2006 04:04 896,720 BIT3.tmp

 
Right, so for some reason, whichever application started the job never actually completed it – hence the "BIT*.tmp" files.  (And yes, I know the file dates aren’t consistent with the BITS jobs created, but the digital certificates of the 2 .tmp files are valid to Google – I’ll look into the "missing" file on 08/03/2006…  However, the file creation / modification dates aren’t exactly reliable, as they can be changed if you know how – but I digress).
 
Anyway, from looking at the dates from the bitsadmin output, I remember that’s when I upgraded GDS.  So I took a look at the file creation date of the GDS installation file.  And it reads:
 

08 March 2006, 01:09:46

 
After some cross reference from my system’s event logs, the timeline goes as follows on 08/03/2006:
01:09:46 – new version of GDS downloaded -> upgraded almost immediately
01:12:12 – System reboot initiated
01:15:08 – Reboot finished – desktop ready to use again
01:15:39 – BITS job finished
 
So in 2 and a bit minutes, the GDS installation downloaded the GoogleTalk installation of 896720 bytes – which is entirely possible with a 2 Mbps downlink.
 
So from this, I can preliminary conclude GDS setup the TalkDownload BITS job and downloaded the GoogleTalk installation – and this is triggered because of the upgrade to GDS.
 
And now… you might ask "So the hell what!?" – and my answer?  Well… I found out that the download is not caused by some malware on my system and that GDS decided I need GoogleTalk…  But most importantly, I’m disappointed by Google, who is doing things "behind my back", so to speak.
 
 
Just out of interest, if you haven’t upgraded to MSN Messenger 7.5, apart from the weekly nagging for the upgrade, you might have noticed a file in "%HomePath%Local SettingsTemp" called "Install_MSN_Messenger.exe".  And if you execute it, it’s the MSN Messenger 7.5 installer, which, I must say, pisses me off since I hadn’t tell anything that I want to upgrade to 7.5 (and I definitely wouldn’t have given permission for the download!).
 
 
So I guess my point I’m trying to make is actually rather simple:
 
Application developers, DON’T code your application to do something the user hadn’t EXPLICITLY told it to do!
 
 
Now if that misbehaving application weren’t GDS and MSN Messenger (or from a source I trust), it would have definitely be uninstalled the moment I found out what it is doing – and whoever made that application would have lost a user / customer.
Advertisements

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: