From: mjt on
On Thu, 8 Jul 2010 16:00:19 +0000 (UTC)
Clark Smith <noaddress(a)nowhere.net> wrote:

> Chrome has been accused of being, among other things, spyware
> from Google - some people report that Chrome calls home as often as
> every few seconds, transferring goodness knows what kind of data.

Chrome doesn't call home.

> Can the same thing be said about Chromium? Since Chromium is
> open source, this should be relatively straightforward to ascertain
> for those with the necessary expertise - of which I am not one.

Chromium doesn't call home.

--
Accident, n.:
A condition in which presence of mind is good,
but absence of body is better.
<<< Remove YOURSHOES to email me >>>

From: Clark Smith on
On Thu, 08 Jul 2010 14:39:33 -0500, mjt wrote:

> On Thu, 8 Jul 2010 16:00:19 +0000 (UTC) Clark Smith
> <noaddress(a)nowhere.net> wrote:
>
>> Chrome has been accused of being, among other things, spyware
>> from Google - some people report that Chrome calls home as often as
>> every few seconds, transferring goodness knows what kind of data.
>
> Chrome doesn't call home.

How do you know that?


>
>> Can the same thing be said about Chromium? Since Chromium is
>> open source, this should be relatively straightforward to ascertain for
>> those with the necessary expertise - of which I am not one.
>
> Chromium doesn't call home.

From: Sam on
Keith Keller writes:

> That's not really the point, of course. The point is that nobody
> outside Google can actually verify what Chrome does or does not do by
> reading the code, so the only options we have are to trust Google, or to
> sniff our own packets.

Sniffing packets is not rocket science. I'm sure that someone already tried
that. And if they saw something nefarious, we would know by now.

From: Sam on
Clark Smith writes:

> On Thu, 08 Jul 2010 14:39:33 -0500, mjt wrote:
>
>> On Thu, 8 Jul 2010 16:00:19 +0000 (UTC) Clark Smith
>> <noaddress(a)nowhere.net> wrote:
>>
>>> Chrome has been accused of being, among other things, spyware
>>> from Google - some people report that Chrome calls home as often as
>>> every few seconds, transferring goodness knows what kind of data.
>>
>> Chrome doesn't call home.
>
> How do you know that?

Well, maybe he captured all packets while browsing in Chrome, for a few
hours, and got bored.

From: mjt on
On Thu, 8 Jul 2010 21:56:55 +0000 (UTC)
Clark Smith <noaddress(a)nowhere.net> wrote:

> > Chrome doesn't call home.
>
> How do you know that?

Wireshark.

--
Basic, n.:
A programming language. Related to certain social diseases in
that those who have it will not admit it in polite company.
<<< Remove YOURSHOES to email me >>>

First  |  Prev  |  Next  |  Last
Pages: 1 2 3 4
Prev: process reappears
Next: Stop Wi-Fi LED blinking