Autoupdate *that*, Google!
Oct. 17th, 2006 11:10 pm![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png){kind=small}
torkellGoogle's autoupdater is a persistent little git, I'll give it that.
The old version of the toolbar is stored as C:\Program Files\Google\GoogleToolbar1.dll. What appears to happen is the updater creates GoogleToolbar2.dll, and registers that in COM. No idea if the old file is deregistered.
Plan A of reregister the old version and hope it didn't notice was doomed from the beginning. The updater saw through that attempt and behaved as normal
Plan B of the same, but then copy the old to where it expects the new and deny writes using NTFS permissions also failed. Instead of creating GoogleToolbar2.dll, GoogleToolbar3.dll was created.
Plan C, however, involves following Plan A and then using NTFS permissions to deny all modifications to the entirety of C:\Program Files\Google.
This appears to be quite successful. The updater can't really do anything if it can't create the new file, or modify or delete the old one. Worst it can do is clobber the registery settings for the toolbar. And that can probably be fixed by applying a similar ACL to HKEY_CURRENT_USER\Software\Google.
Autoupdate that, Google!
The old version of the toolbar is stored as C:\Program Files\Google\GoogleToolbar1.dll. What appears to happen is the updater creates GoogleToolbar2.dll, and registers that in COM. No idea if the old file is deregistered.
Plan A of reregister the old version and hope it didn't notice was doomed from the beginning. The updater saw through that attempt and behaved as normal
Plan B of the same, but then copy the old to where it expects the new and deny writes using NTFS permissions also failed. Instead of creating GoogleToolbar2.dll, GoogleToolbar3.dll was created.
Plan C, however, involves following Plan A and then using NTFS permissions to deny all modifications to the entirety of C:\Program Files\Google.
This appears to be quite successful. The updater can't really do anything if it can't create the new file, or modify or delete the old one. Worst it can do is clobber the registery settings for the toolbar. And that can probably be fixed by applying a similar ACL to HKEY_CURRENT_USER\Software\Google.
Autoupdate that, Google!
![[identity profile]](https://www.dreamwidth.org/img/silk/identity/openid.png){kind=small}
From Dom - your housemate
Date: 2006-10-17 10:28 pm (UTC)Re: From Dom - your housemate
Date: 2006-10-17 10:34 pm (UTC)Re: From Dom - your housemate
Date: 2006-10-17 10:36 pm (UTC)no subject
Date: 2006-10-17 10:33 pm (UTC)Yeah… my dad’s been really annoyed by this behaviour lately as well. Not to mention that the new toolbar doesn’t import his look-and-feel options and clutters everything :/
no subject
Date: 2006-10-17 10:37 pm (UTC)Which reminds me, I'd better copy the file to use next time I reinstall windows.
no subject
Date: 2006-10-18 03:57 pm (UTC)*is an Opera user*
By the way, how do you apply an ACL to a program? Or must you just say that `whoami` is unable to edit this key?
no subject
Date: 2006-10-18 05:24 pm (UTC)He thinks IE is the best browser ever…
I use Konqueror and Firefox and both have 1) search toolbars I never use 2) search keywords.
no subject
Date: 2006-10-18 06:30 pm (UTC)no subject
Date: 2006-10-18 08:26 pm (UTC)no subject
Date: 2006-10-18 08:30 pm (UTC)Supposedly some new system in the works is going to allow that (maybe in 2.0 already? dunno).
no subject
Date: 2006-10-18 06:29 pm (UTC)no subject
Date: 2006-10-17 11:09 pm (UTC)Haha, that icon still strikes me with the “huh! did I post?” feeling XD
no subject
Date: 2006-10-18 06:38 pm (UTC)no subject
Date: 2006-10-18 06:40 pm (UTC)Oh, I know it does :) Thing is though, he nicked the icon from me (which is, actually, perfectly fine with me, but I still get surprised by it).