Article View: chi.internet
Article #219Re: Google Chrome oddity
From: Kristian M Zoerhoff
Date: Tue, 02 Oct 2012 16:47
Date: Tue, 02 Oct 2012 16:47
38 lines
3183 bytes
3183 bytes
On 2012-10-02 11:00, Cydrome Leader wrote: > Mark Anderson <mea@nospambradnylion.com> wrote: >> In article presence@MUNGEpanix.com says... >>>> Since no one posts here I thought I'd try and add something interesting. >>>> I put my PC on a quiet subnet to check on something and noticed google >>>> updates was phoning home every single minute using http with a rather >>>> lengthy session. This chatter was filling up my logs so I investigated >>> >>> snooping on you no doubt. >>> >>> don't trust google. >> >> I try to keep the snooping to a minimum but realize being snooped upon >> is one of the costs of using the tubes. I like running a clean PC -- no >> useless running process, no bullshit traffic. A clean PC is a secure >> PC. Windows is very chatty on the LAN and pretty god damned stupid >> about it. There's a good reason why Windows users get hacked on >> unsecured networks -- they broadcast all kinds of useless bullshit so >> the bad guys don't even need a scanner to ID them as a target. >> >> I almost have my laptop completely silent. I still have some IGMP and >> LLMNR traffic to that multi-cast address that I can't stop because >> apparently I'm using the el cheapo Home version of Windows 7 so I can't >> make the necessary registry changes. Fucking greedy Windows >> motherfuckers. Firefox keeps phoning home for update info even after I >> turned that off in the options. I'm not so concerned about that but >> don't understand why they can't just phone home once when the browser >> starts and be done with it. > > just use IE and stop dicking around. You might as well fuck a syphilitic hooker sans condom. IE is first-class garbage, and a giant pulsing sphincter of a security hole. > other browsers are junk. Chrome with plugins disabled works fine, and it's even better with AdBlock+ and DoNotTrack+. Firefox's memory bloat is inexcusable.
Technical Details
Message-ID:
<k4f5q9$4f0$1@ftupet.ftupet.com>Path:
arc1-ca.pugleaf.net!g9ni15792pbh.1!nntp.google.com!news.glorb.com!news.ripco.com!not-for-mailReferences:
<MPG.2ad036cf48a1c7c89899cc@news.speakeasy.net> <k4dqb3$igj$1@reader1.panix.com> <MPG.2ad44eaeeb23716b9899cf@news.speakeasy.net> <k4f33n$8at$2@reader1.panix.com>Show Full Headers
Complete Article Headers
X-Google-Thread: 10d5fa,e60788e9872e549b
X-Google-NewGroupId: yes
X-Google-Attributes: gid837b0c45a0,domainid0,public,usenet
X-Google-Language: ENGLISH,ASCII-7-bit
Received: by 10.66.72.130 with SMTP id d2mr4441774pav.33.1349196602211;
Tue, 02 Oct 2012 09:50:02 -0700 (PDT)
Path: arc1-ca.pugleaf.net!g9ni15792pbh.1!nntp.google.com!news.glorb.com!news.ripco.com!not-for-mail
From: Kristian M Zoerhoff <kmz@lavabit.com>
Newsgroups: chi.internet
Subject: Re: Google Chrome oddity
Date: Tue, 02 Oct 2012 11:47:04 -0500
Organization: ftupet.com
Lines: 40
Message-ID: <k4f5q9$4f0$1@ftupet.ftupet.com>
References: <MPG.2ad036cf48a1c7c89899cc@news.speakeasy.net> <k4dqb3$igj$1@reader1.panix.com> <MPG.2ad44eaeeb23716b9899cf@news.speakeasy.net> <k4f33n$8at$2@reader1.panix.com>
NNTP-Posting-Host: ftupet.com
Mime-Version: 1.0
X-Trace: remote5bge0.ripco.com 1349196601 23719 66.246.138.5 (2 Oct 2012 16:50:01 GMT)
X-Complaints-To: usenet@ripco.com
NNTP-Posting-Date: Tue, 2 Oct 2012 16:50:01 +0000 (UTC)
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:15.0) Gecko/20120907 Thunderbird/15.0.1
In-Reply-To: <k4f33n$8at$2@reader1.panix.com>
X-Enigmail-Version: 1.4.4
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit