Blue Stone writes "I recently noticed and was alarmed to see Google displaying the name of the (small) town in which I live in its search results (previously it had been very innacurate). Despite disabling the geo.location function in Firefox (unethically enabled by default) and ensuring that all private data was deleted (history, super-cookies, no toolbars) on accquiring a new IP address Google still knew where I was. My IP addresses come from a large national ISP and I'm solely using Firefox with geolocation disabled. Where is Google getting my location from and more importantly, how do I stop it creeping me out and behaving like a (giant, corporate) stalker?" top
Currently the security services can demand the Oyster records of specific individuals under investigation to establish where they have been [3,000 requests for passenger journey data in 2006] but cannot trawl the whole database. But supporters of calls for more sharing of data argue that apparently trivial snippets — like the journeys an individual makes around the capital — could become important pieces of the jigsaw when fitted into a pattern of other publicly held information on an individual's movements, habits, education and other personal details. That could lead, they argue, to the unmasking of otherwise undetected suspects.
As mentioned in the previous entry, I updated Zone Alarm after high DPCs caused by version 7.5s outdated True Vector service (vsmon.exe) caused my system to become unusable. The problem disappeared and everything was fine until a new problem occurred: Firefox would hang after ~30 minutes usage, refusing to load new pages. Firefox would also refuse to quit or start again, requiring a restart of the computer to fix this... before it would happen again. Ridiculous.
I did a little Googling and the evidence seemed to mount up against the new version of True Vector. Suggested solution: use a different firewall. Uninstalled Zone Alarm. Installed Comodo Firewall. Using it in Custom Policy Mode pretty much replicates Zone Alarm's pop-up allow/deny dialogue (with the minor niggle that the 'allow permamnently' tick-box's state is persistent (from a previous answer) instead of always defaulting to 'do not remember this answer' - and so allow or deny on a case by case basis unless a deliberate exception is chosen.
Firefox no longer hangs. Seems to confirm that True Vector was indeed the culprit. Silly Check Point.
The Comodo firewall seeemed to have issues with Avast! antivirus (not exactly confirmed - it caused running firewall after initial reboot to fail) so I uninstalled Avast! (which I liked) and used Comodo's antivirus - along with the entire Internet Security Suite (using the built-in Defence+ instead of Windows Defender). I do like all the information that Comodo gives me (details of every connection etc.) although some aspects of it are slightly non-intuitive (especially compared to ZA's user-friendly interface).
One day and one night running successfully. Early days.
After the latest round of updates from Microsoft, Vista's Deferred Proceedure Calls would go though the roof on certain network activity. Actually it was rather too high before the latest updates (as of the date of writing) but they increased exponentially after the updates.
Before the updates, and for some time now, on loading a webpage in either Firefox or IE, especially one that had heavy image content, audio would stutter (in Winamp and other audio programs) and the mouse pointer would jitter. On my Quad core Core 2 Duo Quad Q6600, Core0 would be at around 85%. The others would spike at around 50 to 75%. The fault was due entirely to high DPCs. Running Azureus would result in similar high DPC. It was suggested that the shitty audio drivers (Sigmatel) were to blame. This turned out not to be the case.
After the updates, the situation worsened, with Core0 pegging at 100% and the others reaching up into the 80s. I could do nothing else while a graphic heavy webpage was loading, or a torrent was downloading (seeding was without incident) as my mouse pointer lurched all over the place and the system was almost entirely unresponsive. Process Monitor revealed that the vsmon.exe (Zone Alarm) was doing an awful lot of something.
I checked for an update for Zone Alarm (7.5) and updated to version 8 and all these problems went away. Whatever Microsoft had been tinkering with had severely fuxx0red with what Vsmon.exe was trying to do, and it couldn't keep on top of things anymore.
Once again, Zone Alarm, that free, ubiquitous (and actually not too shabby) firewall had proved to be the culprit. Nothing to do with Azureus, Firefox, Sigmatel audio drivers, my chipset or Vista.