Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss
Why Is Google Connecting to My Mac?
2,978 views
Skip to first unread message
Mark Dintenfass
Jul 12, 2012, 4:00:27 PM7/12/12
to
I'm running a MacPro with Little Snitch installed and for several weeks
now there have been numerous and frequent attempts by Google to
establish a connection. At first I okayed the requests, then I started
denying them, and they're still appearing up to a dozen times a day. I
have a Google account, but I don't use any of the Google cloud
services. What's going on here?
--
--md
_________
Remove xx's from address to reply
now there have been numerous and frequent attempts by Google to
establish a connection. At first I okayed the requests, then I started
denying them, and they're still appearing up to a dozen times a day. I
have a Google account, but I don't use any of the Google cloud
services. What's going on here?
--
--md
_________
Remove xx's from address to reply
J.J. O'Shea
Jul 12, 2012, 4:29:10 PM7/12/12
to
On Thu, 12 Jul 2012 16:00:27 -0400, Mark Dintenfass wrote
(in article <120720121500273941%mdint...@xxnew.rr.com>):
> I'm running a MacPro with Little Snitch installed and for several weeks
> now there have been numerous and frequent attempts by Google to
> establish a connection. At first I okayed the requests, then I started
> denying them, and they're still appearing up to a dozen times a day. I
> have a Google account, but I don't use any of the Google cloud
> services. What's going on here?
>
>
Do you have any Google software?
--
email to oshea dot j dot j at gmail dot com.
(in article <120720121500273941%mdint...@xxnew.rr.com>):
> I'm running a MacPro with Little Snitch installed and for several weeks
> now there have been numerous and frequent attempts by Google to
> establish a connection. At first I okayed the requests, then I started
> denying them, and they're still appearing up to a dozen times a day. I
> have a Google account, but I don't use any of the Google cloud
> services. What's going on here?
>
>
--
email to oshea dot j dot j at gmail dot com.
Harald Hanche-Olsen
Jul 12, 2012, 5:14:32 PM7/12/12
to
[Mark Dintenfass <mdint...@xxnew.rr.com>]
> I'm running a MacPro with Little Snitch installed and for several weeks
> now there have been numerous and frequent attempts by Google to
> establish a connection.
On what port?
--
* Harald Hanche-Olsen <URL:http://www.math.ntnu.no/~hanche/>
- It is undesirable to believe a proposition
when there is no ground whatsoever for supposing it is true.
-- Bertrand Russell
> I'm running a MacPro with Little Snitch installed and for several weeks
> now there have been numerous and frequent attempts by Google to
> establish a connection.
--
* Harald Hanche-Olsen <URL:http://www.math.ntnu.no/~hanche/>
- It is undesirable to believe a proposition
when there is no ground whatsoever for supposing it is true.
-- Bertrand Russell
Mark Dintenfass
Jul 12, 2012, 8:23:33 PM7/12/12
to
Mark Dintenfass
Jul 12, 2012, 8:24:07 PM7/12/12
to
In article <pcoa9z4...@math.ntnu.no>, Harald Hanche-Olsen
<han...@math.ntnu.no> wrote:
> [Mark Dintenfass <mdint...@xxnew.rr.com>]
>
> > I'm running a MacPro with Little Snitch installed and for several weeks
> > now there have been numerous and frequent attempts by Google to
> > establish a connection.
>
> On what port?
Various port #s show up in Little Snitch.
> [Mark Dintenfass <mdint...@xxnew.rr.com>]
>
> > I'm running a MacPro with Little Snitch installed and for several weeks
> > now there have been numerous and frequent attempts by Google to
> > establish a connection.
>
> On what port?
Jolly Roger
Jul 13, 2012, 12:20:20 AM7/13/12
to
In article <120720121924073113%mdint...@xxnew.rr.com>,
A good way *not* to get help from anyone is to make helping you like
pulling teeth. ; )
--
Send responses to the relevant news group rather than email to me.
E-mail sent to this address may be devoured by my very hungry SPAM
filter. Due to Google's refusal to prevent spammers from posting
messages through their servers, I often ignore posts from Google
Groups. Use a real news client if you want me to see your posts.
JR
Mark Dintenfass <mdint...@xxnew.rr.com> wrote:
> In article <pcoa9z4...@math.ntnu.no>, Harald Hanche-Olsen
> <han...@math.ntnu.no> wrote:
>
> > [Mark Dintenfass <mdint...@xxnew.rr.com>]
> >
> > > I'm running a MacPro with Little Snitch installed and for several weeks
> > > now there have been numerous and frequent attempts by Google to
> > > establish a connection.
> >
> > On what port?
>
> Various port #s show up in Little Snitch.
And they are?
> In article <pcoa9z4...@math.ntnu.no>, Harald Hanche-Olsen
> <han...@math.ntnu.no> wrote:
>
> > [Mark Dintenfass <mdint...@xxnew.rr.com>]
> >
> > > I'm running a MacPro with Little Snitch installed and for several weeks
> > > now there have been numerous and frequent attempts by Google to
> > > establish a connection.
> >
> > On what port?
>
> Various port #s show up in Little Snitch.
A good way *not* to get help from anyone is to make helping you like
pulling teeth. ; )
--
Send responses to the relevant news group rather than email to me.
E-mail sent to this address may be devoured by my very hungry SPAM
filter. Due to Google's refusal to prevent spammers from posting
messages through their servers, I often ignore posts from Google
Groups. Use a real news client if you want me to see your posts.
JR
Jolly Roger
Jul 13, 2012, 12:23:25 AM7/13/12
to
In article <120720121923331054%mdint...@xxnew.rr.com>,
Do you mean the web site, <http://maps.google.com>?
Or do you mean Google eMaps, <https://sites.google.com/site/emanuelet/>?
Or do you mean Google Earth, <http://www.google.com/earth/>?
Or do you mean Google eMaps, <https://sites.google.com/site/emanuelet/>?
Or do you mean Google Earth, <http://www.google.com/earth/>?
Warren Oates
Jul 13, 2012, 6:43:52 AM7/13/12
to
In article <jollyroger-4C0B7...@news.individual.net>,
--
... do not cover a warm kettle or your stock may sour. -- Julia Child
Jolly Roger <jolly...@pobox.com> wrote:
> In article <120720121923331054%mdint...@xxnew.rr.com>,
> Mark Dintenfass <mdint...@xxnew.rr.com> wrote:
>
> > In article <jtnc2...@news4.newsguy.com>, J.J. O'Shea
> > <try.n...@but.see.sig> wrote:
> >
> > > On Thu, 12 Jul 2012 16:00:27 -0400, Mark Dintenfass wrote
> > > (in article <120720121500273941%mdint...@xxnew.rr.com>):
> > >
> > > > I'm running a MacPro with Little Snitch installed and for several weeks
> > > > now there have been numerous and frequent attempts by Google to
> > > > establish a connection. At first I okayed the requests, then I started
> > > > denying them, and they're still appearing up to a dozen times a day. I
> > > > have a Google account, but I don't use any of the Google cloud
> > > > services. What's going on here?
> > > >
> > > >
> > >
> > > Do you have any Google software?
> >
> > Only Google maps.
>
> Do you mean the web site, <http://maps.google.com>?
>
> Or do you mean Google eMaps, <https://sites.google.com/site/emanuelet/>?
>
> Or do you mean Google Earth, <http://www.google.com/earth/>?
It's probably the updater software.
> In article <120720121923331054%mdint...@xxnew.rr.com>,
> Mark Dintenfass <mdint...@xxnew.rr.com> wrote:
>
> > In article <jtnc2...@news4.newsguy.com>, J.J. O'Shea
> > <try.n...@but.see.sig> wrote:
> >
> > > On Thu, 12 Jul 2012 16:00:27 -0400, Mark Dintenfass wrote
> > > (in article <120720121500273941%mdint...@xxnew.rr.com>):
> > >
> > > > I'm running a MacPro with Little Snitch installed and for several weeks
> > > > now there have been numerous and frequent attempts by Google to
> > > > establish a connection. At first I okayed the requests, then I started
> > > > denying them, and they're still appearing up to a dozen times a day. I
> > > > have a Google account, but I don't use any of the Google cloud
> > > > services. What's going on here?
> > > >
> > > >
> > >
> > > Do you have any Google software?
> >
> > Only Google maps.
>
> Do you mean the web site, <http://maps.google.com>?
>
> Or do you mean Google eMaps, <https://sites.google.com/site/emanuelet/>?
>
> Or do you mean Google Earth, <http://www.google.com/earth/>?
--
... do not cover a warm kettle or your stock may sour. -- Julia Child
Mark Dintenfass
Jul 13, 2012, 7:33:10 AM7/13/12
to
> In article <120720121923331054%mdint...@xxnew.rr.com>,
> Mark Dintenfass <mdint...@xxnew.rr.com> wrote:
>
> > In article <jtnc2...@news4.newsguy.com>, J.J. O'Shea
> > <try.n...@but.see.sig> wrote:
> >
> > > On Thu, 12 Jul 2012 16:00:27 -0400, Mark Dintenfass wrote
> > > (in article <120720121500273941%mdint...@xxnew.rr.com>):
> > >
> > > > I'm running a MacPro with Little Snitch installed and for several weeks
> > > > now there have been numerous and frequent attempts by Google to
> > > > establish a connection. At first I okayed the requests, then I started
> > > > denying them, and they're still appearing up to a dozen times a day. I
> > > > have a Google account, but I don't use any of the Google cloud
> > > > services. What's going on here?
> > > >
> > > >
> > >
> > > Do you have any Google software?
> >
> > Only Google maps.
>
> Do you mean the web site, <http://maps.google.com>?
>
> Or do you mean Google eMaps, <https://sites.google.com/site/emanuelet/>?
>
> Or do you mean Google Earth, <http://www.google.com/earth/>?
Sorry, I meant Google Earth.
> Mark Dintenfass <mdint...@xxnew.rr.com> wrote:
>
> > In article <jtnc2...@news4.newsguy.com>, J.J. O'Shea
> > <try.n...@but.see.sig> wrote:
> >
> > > On Thu, 12 Jul 2012 16:00:27 -0400, Mark Dintenfass wrote
> > > (in article <120720121500273941%mdint...@xxnew.rr.com>):
> > >
> > > > I'm running a MacPro with Little Snitch installed and for several weeks
> > > > now there have been numerous and frequent attempts by Google to
> > > > establish a connection. At first I okayed the requests, then I started
> > > > denying them, and they're still appearing up to a dozen times a day. I
> > > > have a Google account, but I don't use any of the Google cloud
> > > > services. What's going on here?
> > > >
> > > >
> > >
> > > Do you have any Google software?
> >
> > Only Google maps.
>
> Do you mean the web site, <http://maps.google.com>?
>
> Or do you mean Google eMaps, <https://sites.google.com/site/emanuelet/>?
>
> Or do you mean Google Earth, <http://www.google.com/earth/>?
In article <jollyroger-3DA91...@news.individual.net>,
Jolly Roger <jolly...@pobox.com> wrote:
> > Various port #s show up in Little Snitch.
>
> And they are?
Sorry again. I'm really not trying to be difficult.
> > Various port #s show up in Little Snitch.
>
> And they are?
The main problem seems to be numerous attempts by ksfetch and ksurl
seeking connection for ports 80 and 443. Little Snitch config shows the
applications seeking these connections no longer exist. There are also
numerous connection requests from four different versions of Google
Earth, also for ports 80 and 443. Below is a complete listing from
Little Snitch's configuration of all Google connection attempts.
Thank you for whatever help you can give me.
------
action: allow
process: /Applications/Google Earth.app/Contents/MacOS/Google Earth
destination: ssl-google-analytics.l.google.com
port: 443
protocol: 6
help: wants to connect to ssl-google-analytics.l.google.com on TCP port
443 (https).
action: allow
process: /Applications/Google Earth.app/Contents/MacOS/Google Earth
destination: ssl.google-analytics.com
port: 443
protocol: 6
help: wants to connect to ssl.google-analytics.com on TCP port 443
(https).
action: allow
process: /Applications/Google Earth.app/Contents/MacOS/Google Earth
destination: www.keyhole.com
port: 443
protocol: 6
help: wants to connect to www.keyhole.com on TCP port 443 (https).
action: allow
process: /Applications/Google Earth.app/Contents/MacOS/Google Earth
destination: c.commondatastorage.googleapis.com
port: 80
protocol: 6
help: wants to connect to c.commondatastorage.googleapis.com on TCP
port 80 (http).
action: allow
process: /Applications/Google Earth.app/Contents/MacOS/Google Earth
destination: cbk0.google.com
port: 80
protocol: 6
help: wants to connect to cbk0.google.com on TCP port 80 (http).
action: allow
process: /Applications/Google Earth.app/Contents/MacOS/Google Earth
destination: csi.l.google.com
port: 80
protocol: 6
help: wants to connect to csi.l.google.com on TCP port 80 (http).
action: allow
process: /Applications/Google Earth.app/Contents/MacOS/Google Earth
destination: earth.google.com
port: 80
protocol: 6
help: wants to connect to earth.google.com on TCP port 80 (http).
action: allow
process: /Applications/Google Earth.app/Contents/MacOS/Google Earth
destination: i.ytimg.com
port: 80
protocol: 6
help: wants to connect to i.ytimg.com on TCP port 80 (http).
action: allow
process: /Applications/Google Earth.app/Contents/MacOS/Google Earth
destination: kh.google.com
port: 80
protocol: 6
help: wants to connect to kh.google.com on TCP port 80 (http).
action: allow
process: /Applications/Google Earth.app/Contents/MacOS/Google Earth
destination: maps.gstatic.com
port: 80
protocol: 6
help: wants to connect to maps.gstatic.com on TCP port 80 (http).
action: allow
process: /Applications/Google Earth.app/Contents/MacOS/Google Earth
destination: mt0.google.com
port: 80
protocol: 6
help: wants to connect to mt0.google.com on TCP port 80 (http).
action: allow
process: /Applications/Google Earth.app/Contents/MacOS/Google Earth
destination: mw1.google.com
port: 80
protocol: 6
help: wants to connect to mw1.google.com on TCP port 80 (http).
action: allow
process: /Applications/Google Earth.app/Contents/MacOS/Google Earth
destination: mw2.google.com
port: 80
protocol: 6
help: wants to connect to mw2.google.com on TCP port 80 (http).
action: allow
process: /Applications/Google Earth.app/Contents/MacOS/Google Earth
destination: pagead.l.google.com
port: 80
protocol: 6
help: wants to connect to pagead.l.google.com on TCP port 80 (http).
action: allow
process: /Applications/Google Earth.app/Contents/MacOS/Google Earth
destination: s2.googleusercontent.com
port: 80
protocol: 6
help: wants to connect to s2.googleusercontent.com on TCP port 80
(http).
action: allow
process: /Applications/Google Earth.app/Contents/MacOS/Google Earth
destination: upload.wikimedia.org
port: 80
protocol: 6
help: wants to connect to upload.wikimedia.org on TCP port 80 (http).
action: allow
process: /Applications/Google Earth.app/Contents/MacOS/Google Earth
destination: www.everytrail.com
port: 80
protocol: 6
help: wants to connect to www.everytrail.com on TCP port 80 (http).
action: allow
process: /Applications/Google Earth.app/Contents/MacOS/Google Earth
destination: www.google-analytics.com
port: 80
protocol: 6
help: wants to connect to www.google-analytics.com on TCP port 80
(http).
action: allow
process: /Applications/Google Earth.app/Contents/MacOS/Google Earth
destination: www.google.com
port: 80
protocol: 6
help: wants to connect to www.google.com on TCP port 80 (http).
action: allow
process: /Library/Internet Plug-Ins/Google Earth Web
Plug-in.plugin/Contents/MacOS/Google Earth for
Plugin.app/Contents/MacOS/Google Earth
destination: csi.l.google.com
port: 80
protocol: 6
help: wants to connect to csi.l.google.com on TCP port 80 (http).
action: allow
process:
/Library/Google/GoogleSoftwareUpdate/GoogleSoftwareUpdate.bundle/Content
s/Resources/GoogleSoftwareUpdateAgent.app/Contents/MacOS/GoogleSoftwareU
pdateAgent
destination: tools.l.google.com
port: 443
protocol: 6
help: wants to connect to tools.l.google.com on TCP port 443 (https).
action: allow
process:
/Library/Google/GoogleSoftwareUpdate/GoogleSoftwareUpdate.bundle/Content
s/Resources/GoogleSoftwareUpdateAgent.app/Contents/MacOS/GoogleSoftwareU
pdateAgent
via: /tmp/UpdateEngine-ksurl.DHFt5eENOH/ksurl
destination: cache.pack.google.com
port: 80
protocol: 6
help: wants to connect to cache.pack.google.com on TCP port 80 (http).
action: allow
process:
/Library/Google/GoogleSoftwareUpdate/GoogleSoftwareUpdate.bundle/Content
s/Resources/GoogleSoftwareUpdateAgent.app/Contents/MacOS/GoogleSoftwareU
pdateAgent
via: /tmp/UpdateEngine-ksurl.5FnCwX3hvk/ksurl
destination: any
port: any
protocol: any
help: wants to connect to cache.pack.google.com on TCP port 80 (http).
action: allow
process:
/Library/Google/GoogleSoftwareUpdate/GoogleSoftwareUpdate.bundle/Content
s/Resources/GoogleSoftwareUpdateAgent.app/Contents/MacOS/GoogleSoftwareU
pdateAgent
via: /tmp/UpdateEngine-ksurl.abCePHslDC/ksurl
destination: any
port: any
protocol: any
help: wants to connect to cache.l.google.com on TCP port 80 (http).
action: allow
process:
//Library/Google/GoogleSoftwareUpdate/GoogleSoftwareUpdate.bundle/Conten
ts/Resources/GoogleSoftwareUpdateAgent.app/Contents/MacOS/GoogleSoftware
UpdateAgent
destination: tools.l.google.com
port: 443
protocol: 6
help: wants to connect to tools.l.google.com on TCP port 443 (https).
action: allow
process:
//Library/Google/GoogleSoftwareUpdate/GoogleSoftwareUpdate.bundle/Conten
ts/Resources/GoogleSoftwareUpdateAgent.app/Contents/MacOS/GoogleSoftware
UpdateAgent
via: /tmp/UpdateEngine-ksurl.rgFA3AtO47/ksurl
destination: cache.l.google.com
port: 80
protocol: 6
help: wants to connect to cache.l.google.com on TCP port 80 (http).
action: allow
process:
//Library/Google/GoogleSoftwareUpdate/GoogleSoftwareUpdate.bundle/Conten
ts/Resources/GoogleSoftwareUpdateAgent.app/Contents/MacOS/GoogleSoftware
UpdateAgent
via: /tmp/UpdateEngine-ksurl.4FjlnOGOXb/ksurl
destination: cache.l.google.com
port: 80
protocol: 6
help: wants to connect to cache.l.google.com on TCP port 80 (http).
action: allow
process:
//Library/Google/GoogleSoftwareUpdate/GoogleSoftwareUpdate.bundle/Conten
ts/Resources/GoogleSoftwareUpdateAgent.app/Contents/MacOS/GoogleSoftware
UpdateAgent
via: /tmp/UpdateEngine-ksurl.AC7lVUGes1/ksurl
destination: cache.pack.google.com
port: 80
protocol: 6
help: wants to connect to cache.pack.google.com on TCP port 80 (http).
action: allow
process:
//Library/Google/GoogleSoftwareUpdate/GoogleSoftwareUpdate.bundle/Conten
ts/Resources/GoogleSoftwareUpdateAgent.app/Contents/MacOS/GoogleSoftware
UpdateAgent
via: /tmp/UpdateEngine-ksurl.3hRd6lRszp/ksurl
destination: cache.pack.google.com
port: 80
protocol: 6
help: wants to connect to cache.pack.google.com on TCP port 80 (http).
action: allow
process:
/Users/Mark//Library/Google/GoogleSoftwareUpdate/GoogleSoftwareUpdate.bu
ndle/Contents/Resources/GoogleSoftwareUpdateAgent.app/Contents/MacOS/Goo
gleSoftwareUpdateAgent
destination: tools.google.com
port: 443
protocol: 6
help: wants to connect to tools.google.com on TCP port 443 (https).
action: allow
process:
/Users/Mark//Library/Google/GoogleSoftwareUpdate/GoogleSoftwareUpdate.bu
ndle/Contents/Resources/GoogleSoftwareUpdateAgent.app/Contents/MacOS/Goo
gleSoftwareUpdateAgent
via: /tmp/.ksda.1F5/ksurl
destination: cache.pack.google.com
port: 80
protocol: 6
help: wants to connect to cache.pack.google.com on TCP port 80 (http).
action: allow
process:
/Users/Mark//Library/Google/GoogleSoftwareUpdate/GoogleSoftwareUpdate.bu
ndle/Contents/Resources/GoogleSoftwareUpdateAgent.app/Contents/MacOS/Goo
gleSoftwareUpdateAgent
via: /tmp/.ksda.1F5/ksurl
destination: dl.google.com
port: 80
protocol: 6
help: wants to connect to dl.google.com on TCP port 80 (http).
action: allow
process:
//Library/Google/GoogleSoftwareUpdate/GoogleSoftwareUpdate.bundle/Conten
ts/MacOS/GoogleSoftwareUpdateDaemon
destination: tools.l.google.com
port: 443
protocol: 6
help: wants to connect to tools.l.google.com on TCP port 443 (https).
action: allow
process:
/Library/Google/GoogleSoftwareUpdate/GoogleSoftwareUpdate.bundle/Content
s/MacOS/GoogleSoftwareUpdateDaemon
destination: tools.google.com
port: 443
protocol: 6
help: wants to connect to tools.google.com on TCP port 443 (https).
action: allow
process:
/Library/Google/GoogleSoftwareUpdate/GoogleSoftwareUpdate.bundle/Content
s/MacOS/GoogleSoftwareUpdateDaemon
destination: any
port: any
protocol: any
help: wants to connect to tools.l.google.com on TCP port 443 (https).
action: allow
process: /Library/Application
Support/Google/GoogleTalkPlugin.app/Contents/MacOS/GoogleTalkPlugin
destination: relay.google.com
port: 80
protocol: 6
help: wants to connect to relay.google.com on TCP port 80 (http).
action: allow
process: /Library/Application
Support/Google/GoogleTalkPlugin.app/Contents/MacOS/GoogleTalkPlugin
destination: stun.l.google.com
port: 19302
protocol: 17
help: wants to connect to stun.l.google.com on UDP port 19302.
action: allow
process: /Library/Application
Support/Google/GoogleTalkPlugin.app/Contents/MacOS/GoogleTalkPlugin
destination: 192.168.1.2
port: 62867
protocol: 17
help: wants to connect to 192.168.1.2 on UDP port 62867.
action: allow
process: /Library/Application
Support/Google/GoogleTalkPlugin.app/Contents/MacOS/GoogleTalkPlugin
destination: 192.168.1.2
port: 62869
protocol: 17
help: wants to connect to 192.168.1.2 on UDP port 62869.
action: allow
process: /Library/Application
Support/Google/GoogleTalkPlugin.app/Contents/MacOS/GoogleTalkPlugin
destination: any
port: any
protocol: any
help: wants to connect to 192.168.1.2 on UDP port 62871.
action: allow
process: /Applications/Google Earth.app/Contents/MacOS/Google Earth
destination: ssl-google-analytics.l.google.com
port: 443
protocol: 6
help: wants to connect to ssl-google-analytics.l.google.com on TCP port
443 (https).
action: allow
process: /Applications/Google Earth.app/Contents/MacOS/Google Earth
destination: ssl.google-analytics.com
port: 443
protocol: 6
help: wants to connect to ssl.google-analytics.com on TCP port 443
(https).
action: allow
process: /Applications/Google Earth.app/Contents/MacOS/Google Earth
destination: www.keyhole.com
port: 443
protocol: 6
help: wants to connect to www.keyhole.com on TCP port 443 (https).
action: allow
process: /Applications/Google Earth.app/Contents/MacOS/Google Earth
destination: c.commondatastorage.googleapis.com
port: 80
protocol: 6
help: wants to connect to c.commondatastorage.googleapis.com on TCP
port 80 (http).
action: allow
process: /Applications/Google Earth.app/Contents/MacOS/Google Earth
destination: cbk0.google.com
port: 80
protocol: 6
help: wants to connect to cbk0.google.com on TCP port 80 (http).
action: allow
process: /Applications/Google Earth.app/Contents/MacOS/Google Earth
destination: csi.l.google.com
port: 80
protocol: 6
help: wants to connect to csi.l.google.com on TCP port 80 (http).
action: allow
process: /Applications/Google Earth.app/Contents/MacOS/Google Earth
destination: earth.google.com
port: 80
protocol: 6
help: wants to connect to earth.google.com on TCP port 80 (http).
action: allow
process: /Applications/Google Earth.app/Contents/MacOS/Google Earth
destination: i.ytimg.com
port: 80
protocol: 6
help: wants to connect to i.ytimg.com on TCP port 80 (http).
action: allow
process: /Applications/Google Earth.app/Contents/MacOS/Google Earth
destination: kh.google.com
port: 80
protocol: 6
help: wants to connect to kh.google.com on TCP port 80 (http).
action: allow
process: /Applications/Google Earth.app/Contents/MacOS/Google Earth
destination: maps.gstatic.com
port: 80
protocol: 6
help: wants to connect to maps.gstatic.com on TCP port 80 (http).
action: allow
process: /Applications/Google Earth.app/Contents/MacOS/Google Earth
destination: mt0.google.com
port: 80
protocol: 6
help: wants to connect to mt0.google.com on TCP port 80 (http).
action: allow
process: /Applications/Google Earth.app/Contents/MacOS/Google Earth
destination: mw1.google.com
port: 80
protocol: 6
help: wants to connect to mw1.google.com on TCP port 80 (http).
action: allow
process: /Applications/Google Earth.app/Contents/MacOS/Google Earth
destination: mw2.google.com
port: 80
protocol: 6
help: wants to connect to mw2.google.com on TCP port 80 (http).
action: allow
process: /Applications/Google Earth.app/Contents/MacOS/Google Earth
destination: pagead.l.google.com
port: 80
protocol: 6
help: wants to connect to pagead.l.google.com on TCP port 80 (http).
action: allow
process: /Applications/Google Earth.app/Contents/MacOS/Google Earth
destination: s2.googleusercontent.com
port: 80
protocol: 6
help: wants to connect to s2.googleusercontent.com on TCP port 80
(http).
action: allow
process: /Applications/Google Earth.app/Contents/MacOS/Google Earth
destination: upload.wikimedia.org
port: 80
protocol: 6
help: wants to connect to upload.wikimedia.org on TCP port 80 (http).
action: allow
process: /Applications/Google Earth.app/Contents/MacOS/Google Earth
destination: www.everytrail.com
port: 80
protocol: 6
help: wants to connect to www.everytrail.com on TCP port 80 (http).
action: allow
process: /Applications/Google Earth.app/Contents/MacOS/Google Earth
destination: www.google-analytics.com
port: 80
protocol: 6
help: wants to connect to www.google-analytics.com on TCP port 80
(http).
action: allow
process: /Applications/Google Earth.app/Contents/MacOS/Google Earth
destination: www.google.com
port: 80
protocol: 6
help: wants to connect to www.google.com on TCP port 80 (http).
action: allow
process: /Library/Internet Plug-Ins/Google Earth Web
Plug-in.plugin/Contents/MacOS/Google Earth for
Plugin.app/Contents/MacOS/Google Earth
destination: csi.l.google.com
port: 80
protocol: 6
help: wants to connect to csi.l.google.com on TCP port 80 (http).
action: allow
process:
/Library/Google/GoogleSoftwareUpdate/GoogleSoftwareUpdate.bundle/Content
s/Resources/GoogleSoftwareUpdateAgent.app/Contents/MacOS/GoogleSoftwareU
pdateAgent
destination: tools.l.google.com
port: 443
protocol: 6
help: wants to connect to tools.l.google.com on TCP port 443 (https).
action: allow
process:
/Library/Google/GoogleSoftwareUpdate/GoogleSoftwareUpdate.bundle/Content
s/Resources/GoogleSoftwareUpdateAgent.app/Contents/MacOS/GoogleSoftwareU
pdateAgent
via: /tmp/UpdateEngine-ksurl.DHFt5eENOH/ksurl
destination: cache.pack.google.com
port: 80
protocol: 6
help: wants to connect to cache.pack.google.com on TCP port 80 (http).
action: allow
process:
/Library/Google/GoogleSoftwareUpdate/GoogleSoftwareUpdate.bundle/Content
s/Resources/GoogleSoftwareUpdateAgent.app/Contents/MacOS/GoogleSoftwareU
pdateAgent
via: /tmp/UpdateEngine-ksurl.5FnCwX3hvk/ksurl
destination: any
port: any
protocol: any
help: wants to connect to cache.pack.google.com on TCP port 80 (http).
action: allow
process:
/Library/Google/GoogleSoftwareUpdate/GoogleSoftwareUpdate.bundle/Content
s/Resources/GoogleSoftwareUpdateAgent.app/Contents/MacOS/GoogleSoftwareU
pdateAgent
via: /tmp/UpdateEngine-ksurl.abCePHslDC/ksurl
destination: any
port: any
protocol: any
help: wants to connect to cache.l.google.com on TCP port 80 (http).
action: allow
process:
//Library/Google/GoogleSoftwareUpdate/GoogleSoftwareUpdate.bundle/Conten
ts/Resources/GoogleSoftwareUpdateAgent.app/Contents/MacOS/GoogleSoftware
UpdateAgent
destination: tools.l.google.com
port: 443
protocol: 6
help: wants to connect to tools.l.google.com on TCP port 443 (https).
action: allow
process:
//Library/Google/GoogleSoftwareUpdate/GoogleSoftwareUpdate.bundle/Conten
ts/Resources/GoogleSoftwareUpdateAgent.app/Contents/MacOS/GoogleSoftware
UpdateAgent
via: /tmp/UpdateEngine-ksurl.rgFA3AtO47/ksurl
destination: cache.l.google.com
port: 80
protocol: 6
help: wants to connect to cache.l.google.com on TCP port 80 (http).
action: allow
process:
//Library/Google/GoogleSoftwareUpdate/GoogleSoftwareUpdate.bundle/Conten
ts/Resources/GoogleSoftwareUpdateAgent.app/Contents/MacOS/GoogleSoftware
UpdateAgent
via: /tmp/UpdateEngine-ksurl.4FjlnOGOXb/ksurl
destination: cache.l.google.com
port: 80
protocol: 6
help: wants to connect to cache.l.google.com on TCP port 80 (http).
action: allow
process:
//Library/Google/GoogleSoftwareUpdate/GoogleSoftwareUpdate.bundle/Conten
ts/Resources/GoogleSoftwareUpdateAgent.app/Contents/MacOS/GoogleSoftware
UpdateAgent
via: /tmp/UpdateEngine-ksurl.AC7lVUGes1/ksurl
destination: cache.pack.google.com
port: 80
protocol: 6
help: wants to connect to cache.pack.google.com on TCP port 80 (http).
action: allow
process:
//Library/Google/GoogleSoftwareUpdate/GoogleSoftwareUpdate.bundle/Conten
ts/Resources/GoogleSoftwareUpdateAgent.app/Contents/MacOS/GoogleSoftware
UpdateAgent
via: /tmp/UpdateEngine-ksurl.3hRd6lRszp/ksurl
destination: cache.pack.google.com
port: 80
protocol: 6
help: wants to connect to cache.pack.google.com on TCP port 80 (http).
action: allow
process:
/Users/Mark//Library/Google/GoogleSoftwareUpdate/GoogleSoftwareUpdate.bu
ndle/Contents/Resources/GoogleSoftwareUpdateAgent.app/Contents/MacOS/Goo
gleSoftwareUpdateAgent
destination: tools.google.com
port: 443
protocol: 6
help: wants to connect to tools.google.com on TCP port 443 (https).
action: allow
process:
/Users/Mark//Library/Google/GoogleSoftwareUpdate/GoogleSoftwareUpdate.bu
ndle/Contents/Resources/GoogleSoftwareUpdateAgent.app/Contents/MacOS/Goo
gleSoftwareUpdateAgent
via: /tmp/.ksda.1F5/ksurl
destination: cache.pack.google.com
port: 80
protocol: 6
help: wants to connect to cache.pack.google.com on TCP port 80 (http).
action: allow
process:
/Users/Mark//Library/Google/GoogleSoftwareUpdate/GoogleSoftwareUpdate.bu
ndle/Contents/Resources/GoogleSoftwareUpdateAgent.app/Contents/MacOS/Goo
gleSoftwareUpdateAgent
via: /tmp/.ksda.1F5/ksurl
destination: dl.google.com
port: 80
protocol: 6
help: wants to connect to dl.google.com on TCP port 80 (http).
action: allow
process:
//Library/Google/GoogleSoftwareUpdate/GoogleSoftwareUpdate.bundle/Conten
ts/MacOS/GoogleSoftwareUpdateDaemon
destination: tools.l.google.com
port: 443
protocol: 6
help: wants to connect to tools.l.google.com on TCP port 443 (https).
action: allow
process:
/Library/Google/GoogleSoftwareUpdate/GoogleSoftwareUpdate.bundle/Content
s/MacOS/GoogleSoftwareUpdateDaemon
destination: tools.google.com
port: 443
protocol: 6
help: wants to connect to tools.google.com on TCP port 443 (https).
action: allow
process:
/Library/Google/GoogleSoftwareUpdate/GoogleSoftwareUpdate.bundle/Content
s/MacOS/GoogleSoftwareUpdateDaemon
destination: any
port: any
protocol: any
help: wants to connect to tools.l.google.com on TCP port 443 (https).
action: allow
process: /Library/Application
Support/Google/GoogleTalkPlugin.app/Contents/MacOS/GoogleTalkPlugin
destination: relay.google.com
port: 80
protocol: 6
help: wants to connect to relay.google.com on TCP port 80 (http).
action: allow
process: /Library/Application
Support/Google/GoogleTalkPlugin.app/Contents/MacOS/GoogleTalkPlugin
destination: stun.l.google.com
port: 19302
protocol: 17
help: wants to connect to stun.l.google.com on UDP port 19302.
action: allow
process: /Library/Application
Support/Google/GoogleTalkPlugin.app/Contents/MacOS/GoogleTalkPlugin
destination: 192.168.1.2
port: 62867
protocol: 17
help: wants to connect to 192.168.1.2 on UDP port 62867.
action: allow
process: /Library/Application
Support/Google/GoogleTalkPlugin.app/Contents/MacOS/GoogleTalkPlugin
destination: 192.168.1.2
port: 62869
protocol: 17
help: wants to connect to 192.168.1.2 on UDP port 62869.
action: allow
process: /Library/Application
Support/Google/GoogleTalkPlugin.app/Contents/MacOS/GoogleTalkPlugin
destination: any
port: any
protocol: any
help: wants to connect to 192.168.1.2 on UDP port 62871.
Jolly Roger
Jul 13, 2012, 12:56:34 PM7/13/12
to
In article <130720120633101217%mdint...@xxnew.rr.com>,
> In article <jollyroger-3DA91...@news.individual.net>,
> Jolly Roger <jolly...@pobox.com> wrote:
>
> > > Various port #s show up in Little Snitch.
> >
> > And they are?
>
> Sorry again. I'm really not trying to be difficult.
>
> The main problem seems to be numerous attempts by ksfetch and ksurl
> seeking connection for ports 80 and 443. Little Snitch config shows the
> applications seeking these connections no longer exist. There are also
> numerous connection requests from four different versions of Google
> Earth, also for ports 80 and 443. Below is a complete listing from
> Little Snitch's configuration of all Google connection attempts.
>
> Thank you for whatever help you can give me.
Apparently, ksfetch is part of Google Chrome (though it may also be used
for other Google software, I suppose):
<http://www.fauxzen.com/little-snitch-google-chrome-ksfetch-issues/>
ksurl is part of Google's aoftware update code base:
<http://code.google.com/p/update-engine/source/browse/trunk/Core/Support/
ksurl-main.m?spec=svn3&r=3>
Mark Dintenfass <mdint...@xxnew.rr.com> wrote:
> In article <jollyroger-4C0B7...@news.individual.net>,
> Jolly Roger <jolly...@pobox.com> wrote:
>
> > In article <120720121923331054%mdint...@xxnew.rr.com>,
> > Mark Dintenfass <mdint...@xxnew.rr.com> wrote:
> >
> > > In article <jtnc2...@news4.newsguy.com>, J.J. O'Shea
> > > <try.n...@but.see.sig> wrote:
> > >
> > > > On Thu, 12 Jul 2012 16:00:27 -0400, Mark Dintenfass wrote
> > > > (in article <120720121500273941%mdint...@xxnew.rr.com>):
> > > >
> > > > > I'm running a MacPro with Little Snitch installed and for
> > > > > several weeks now there have been numerous and frequent
> > > > > attempts by Google to establish a connection. At first I
> > > > > okayed the requests, then I started denying them, and they're
> > > > > still appearing up to a dozen times a day. I have a Google
> > > > > account, but I don't use any of the Google cloud services.
> > > > > What's going on here?
> > > >
> > > > Do you have any Google software?
> > >
> > > Only Google maps.
> >
> > Do you mean the web site, <http://maps.google.com>?
> >
> > Or do you mean Google eMaps, <https://sites.google.com/site/emanuelet/>?
> >
> > Or do you mean Google Earth, <http://www.google.com/earth/>?
>
> Sorry, I meant Google Earth.
Do you also have Google Chrome installed?
> In article <jollyroger-4C0B7...@news.individual.net>,
> Jolly Roger <jolly...@pobox.com> wrote:
>
> > In article <120720121923331054%mdint...@xxnew.rr.com>,
> > Mark Dintenfass <mdint...@xxnew.rr.com> wrote:
> >
> > > In article <jtnc2...@news4.newsguy.com>, J.J. O'Shea
> > > <try.n...@but.see.sig> wrote:
> > >
> > > > On Thu, 12 Jul 2012 16:00:27 -0400, Mark Dintenfass wrote
> > > > (in article <120720121500273941%mdint...@xxnew.rr.com>):
> > > >
> > > > > I'm running a MacPro with Little Snitch installed and for
> > > > > several weeks now there have been numerous and frequent
> > > > > attempts by Google to establish a connection. At first I
> > > > > okayed the requests, then I started denying them, and they're
> > > > > still appearing up to a dozen times a day. I have a Google
> > > > > account, but I don't use any of the Google cloud services.
> > > > > What's going on here?
> > > >
> > > > Do you have any Google software?
> > >
> > > Only Google maps.
> >
> > Do you mean the web site, <http://maps.google.com>?
> >
> > Or do you mean Google eMaps, <https://sites.google.com/site/emanuelet/>?
> >
> > Or do you mean Google Earth, <http://www.google.com/earth/>?
>
> Sorry, I meant Google Earth.
> In article <jollyroger-3DA91...@news.individual.net>,
> Jolly Roger <jolly...@pobox.com> wrote:
>
> > > Various port #s show up in Little Snitch.
> >
> > And they are?
>
> Sorry again. I'm really not trying to be difficult.
>
> The main problem seems to be numerous attempts by ksfetch and ksurl
> seeking connection for ports 80 and 443. Little Snitch config shows the
> applications seeking these connections no longer exist. There are also
> numerous connection requests from four different versions of Google
> Earth, also for ports 80 and 443. Below is a complete listing from
> Little Snitch's configuration of all Google connection attempts.
>
> Thank you for whatever help you can give me.
for other Google software, I suppose):
<http://www.fauxzen.com/little-snitch-google-chrome-ksfetch-issues/>
ksurl is part of Google's aoftware update code base:
<http://code.google.com/p/update-engine/source/browse/trunk/Core/Support/
ksurl-main.m?spec=svn3&r=3>
Mark Dintenfass
Jul 13, 2012, 2:06:03 PM7/13/12
to
In article <jollyroger-A7C55...@news.individual.net>,
>
> > In article <jollyroger-3DA91...@news.individual.net>,
> > Jolly Roger <jolly...@pobox.com> wrote:
> >
> > > > Various port #s show up in Little Snitch.
> > >
> > > And they are?
> >
> > Sorry again. I'm really not trying to be difficult.
> >
> > The main problem seems to be numerous attempts by ksfetch and ksurl
> > seeking connection for ports 80 and 443. Little Snitch config shows the
> > applications seeking these connections no longer exist. There are also
> > numerous connection requests from four different versions of Google
> > Earth, also for ports 80 and 443. Below is a complete listing from
> > Little Snitch's configuration of all Google connection attempts.
> >
> > Thank you for whatever help you can give me.
>
> Apparently, ksfetch is part of Google Chrome (though it may also be used
> for other Google software, I suppose):
>
> <http://www.fauxzen.com/little-snitch-google-chrome-ksfetch-issues/>
>
> ksurl is part of Google's aoftware update code base:
>
> <http://code.google.com/p/update-engine/source/browse/trunk/Core/Support/
> ksurl-main.m?spec=svn3&r=3>
Thanks for the help.
Jolly Roger <jolly...@pobox.com> wrote:
> In article <130720120633101217%mdint...@xxnew.rr.com>,
> Mark Dintenfass <mdint...@xxnew.rr.com> wrote:
>
> > In article <jollyroger-4C0B7...@news.individual.net>,
> >
> In article <130720120633101217%mdint...@xxnew.rr.com>,
> Mark Dintenfass <mdint...@xxnew.rr.com> wrote:
>
> > In article <jollyroger-4C0B7...@news.individual.net>,
> >
> > Sorry, I meant Google Earth.
>
> Do you also have Google Chrome installed?
No.
>
> Do you also have Google Chrome installed?
>
> > In article <jollyroger-3DA91...@news.individual.net>,
> > Jolly Roger <jolly...@pobox.com> wrote:
> >
> > > > Various port #s show up in Little Snitch.
> > >
> > > And they are?
> >
> > Sorry again. I'm really not trying to be difficult.
> >
> > The main problem seems to be numerous attempts by ksfetch and ksurl
> > seeking connection for ports 80 and 443. Little Snitch config shows the
> > applications seeking these connections no longer exist. There are also
> > numerous connection requests from four different versions of Google
> > Earth, also for ports 80 and 443. Below is a complete listing from
> > Little Snitch's configuration of all Google connection attempts.
> >
> > Thank you for whatever help you can give me.
>
> Apparently, ksfetch is part of Google Chrome (though it may also be used
> for other Google software, I suppose):
>
> <http://www.fauxzen.com/little-snitch-google-chrome-ksfetch-issues/>
>
> ksurl is part of Google's aoftware update code base:
>
> <http://code.google.com/p/update-engine/source/browse/trunk/Core/Support/
> ksurl-main.m?spec=svn3&r=3>
frau.dr...@googlemail.com
Jul 19, 2012, 7:01:14 PM7/19/12
to
On Friday, July 13, 2012 6:20:20 AM UTC+2, Jolly Roger wrote:
> In article <120720121924073113%mdint...@xxnew.rr.com>,
> Mark Dintenfass <mdint...@xxnew.rr.com> wrote:
>
> > In article <pcoa9z4...@math.ntnu.no>, Harald Hanche-Olsen
> > <han...@math.ntnu.no> wrote:
> >
> > > [Mark Dintenfass <mdint...@xxnew.rr.com>]
> > >
> > > > I'm running a MacPro with Little Snitch installed and for several weeks
> > > > now there have been numerous and frequent attempts by Google to
> > > > establish a connection.
> > >
> > > On what port?
> >
> > Various port #s show up in Little Snitch.
From what I've seen it seem to be related to having installed google chrome (regardless of whether it's ever been used), although uninstalling it doesn't get rid of the hourly connection requests (which can't be stopped, since they're always sent from a new process). It also seems to be related to an updater.
Right now I've got a request on TCP port 443, if you must know.
> In article <120720121924073113%mdint...@xxnew.rr.com>,
> Mark Dintenfass <mdint...@xxnew.rr.com> wrote:
>
> > In article <pcoa9z4...@math.ntnu.no>, Harald Hanche-Olsen
> > <han...@math.ntnu.no> wrote:
> >
> > > [Mark Dintenfass <mdint...@xxnew.rr.com>]
> > >
> > > > I'm running a MacPro with Little Snitch installed and for several weeks
> > > > now there have been numerous and frequent attempts by Google to
> > > > establish a connection.
> > >
> > > On what port?
> >
> > Various port #s show up in Little Snitch.
>
> And they are?
>
> A good way *not* to get help from anyone is to make helping you like
> pulling teeth. ; )
>
> --
> Send responses to the relevant news group rather than email to me.
> E-mail sent to this address may be devoured by my very hungry SPAM
> filter. Due to Google's refusal to prevent spammers from posting
> And they are?
>
> A good way *not* to get help from anyone is to make helping you like
> pulling teeth. ; )
>
> --
> Send responses to the relevant news group rather than email to me.
> E-mail sent to this address may be devoured by my very hungry SPAM
> messages through their servers, I often ignore posts from Google
> Groups. Use a real news client if you want me to see your posts.
>
> JR
A bad way to give help is to act like a total ass. This problem is well documented elsewhere. Lots of people are complaining about it. You could easily have found the information needed to give a helpful reply in the time it took you to give a snarky, unhelpful reply, twice.
> Groups. Use a real news client if you want me to see your posts.
>
> JR
From what I've seen it seem to be related to having installed google chrome (regardless of whether it's ever been used), although uninstalling it doesn't get rid of the hourly connection requests (which can't be stopped, since they're always sent from a new process). It also seems to be related to an updater.
Right now I've got a request on TCP port 443, if you must know.
frau.dr...@googlemail.com
Jul 19, 2012, 7:22:19 PM7/19/12
to
there are some helpful suggestions at:
https://productforums.google.com/forum/?fromgroups#!topic/chrome/yVump44eeOc
https://productforums.google.com/forum/?fromgroups#!topic/chrome/yVump44eeOc
Jolly Roger
Jul 19, 2012, 7:52:14 PM7/19/12
to
In article <be7118ff-e6c9-4dab...@googlegroups.com>,
> This problem is well
> documented elsewhere. Lots of people are complaining about it. You could
> easily have found the information needed to give a helpful reply in the time
> it took you to give a snarky, unhelpful reply, twice.
And he couldn't have?
Last I checked, I'm not every lazy person's secretary.
And before you tell me I should have kept my mouth shut rather than
replying again, I'll gladly point out that you don't follow that advice
yourself.
> From what I've seen it seem to be related to having installed google chrome
> (regardless of whether it's ever been used), although uninstalling it doesn't
> get rid of the hourly connection requests (which can't be stopped, since
> they're always sent from a new process). It also seems to be related to an
> updater.
>
> Right now I've got a request on TCP port 443, if you must know.
frau.dr...@googlemail.com wrote:
> On Friday, July 13, 2012 6:20:20 AM UTC+2, Jolly Roger wrote:
> > In article <120720121924073113%mdint...@xxnew.rr.com>,
> > Mark Dintenfass <mdint...@xxnew.rr.com> wrote:
> >
> > > In article <pcoa9z4...@math.ntnu.no>, Harald Hanche-Olsen
> > > <han...@math.ntnu.no> wrote:
> > >
> > > > [Mark Dintenfass <mdint...@xxnew.rr.com>]
> > > >
> > > > > I'm running a MacPro with Little Snitch installed and
> > for several weeks
> > > > > now there have been numerous and frequent attempts by Google
> > to
> > > > > establish a connection.
> > > >
> > > > On what port?
> > >
> > > Various port #s show up in Little Snitch.
> >
> > And they are?
> >
> > A good way *not* to get help from anyone is to make helping you like
> > pulling teeth. ; )
>
> On Friday, July 13, 2012 6:20:20 AM UTC+2, Jolly Roger wrote:
> > In article <120720121924073113%mdint...@xxnew.rr.com>,
> > Mark Dintenfass <mdint...@xxnew.rr.com> wrote:
> >
> > > In article <pcoa9z4...@math.ntnu.no>, Harald Hanche-Olsen
> > > <han...@math.ntnu.no> wrote:
> > >
> > > > [Mark Dintenfass <mdint...@xxnew.rr.com>]
> > > >
> > > > > I'm running a MacPro with Little Snitch installed and
> > for several weeks
> > > > > now there have been numerous and frequent attempts by Google
> > to
> > > > > establish a connection.
> > > >
> > > > On what port?
> > >
> > > Various port #s show up in Little Snitch.
> >
> > And they are?
> >
> > A good way *not* to get help from anyone is to make helping you like
> > pulling teeth. ; )
>
> A bad way to give help is to act like a total ass.
What makes you think I was "giving help"?
> This problem is well
> documented elsewhere. Lots of people are complaining about it. You could
> easily have found the information needed to give a helpful reply in the time
> it took you to give a snarky, unhelpful reply, twice.
Last I checked, I'm not every lazy person's secretary.
And before you tell me I should have kept my mouth shut rather than
replying again, I'll gladly point out that you don't follow that advice
yourself.
> From what I've seen it seem to be related to having installed google chrome
> (regardless of whether it's ever been used), although uninstalling it doesn't
> get rid of the hourly connection requests (which can't be stopped, since
> they're always sent from a new process). It also seems to be related to an
> updater.
>
> Right now I've got a request on TCP port 443, if you must know.
--
Send responses to the relevant news group rather than email to me.
E-mail sent to this address may be devoured by my very hungry SPAM
filter. Due to Google's refusal to prevent spammers from posting
Send responses to the relevant news group rather than email to me.
E-mail sent to this address may be devoured by my very hungry SPAM
Jolly Roger
Jul 19, 2012, 7:57:40 PM7/19/12
to
> From what I've seen it seem to be related to having installed google chrome
> (regardless of whether it's ever been used), although uninstalling it doesn't
> get rid of the hourly connection requests (which can't be stopped, since
> they're always sent from a new process). It also seems to be related to an
> updater.
Apparently you missed my other response, where I said what you just
> (regardless of whether it's ever been used), although uninstalling it doesn't
> get rid of the hourly connection requests (which can't be stopped, since
> they're always sent from a new process). It also seems to be related to an
> updater.
said. I guess you were too busy calling me a total ass to see it.
I'll go ahead repeat myself (not for your benefit, but for anyone else
who happens to read this sub-thread looking for advice I gave in the
other sub-thread):
Apparently, ksfetch is part of Google Chrome (though it may also be used
for other Google software, I suppose):
<http://www.fauxzen.com/little-snitch-google-chrome-ksfetch-issues/>
ksurl is part of Google's aoftware update code base:
<http://code.google.com/p/update-engine/source/browse/trunk/Core/Support/
ksurl-main.m?spec=svn3&r=3>
> Right now I've got a request on TCP port 443, if you must know.
I truly couldn't care less.
Bye now.
--
Send responses to the relevant news group rather than email to me.
E-mail sent to this address may be devoured by my very hungry SPAM
Wilbur Eleven
Jul 20, 2012, 7:13:46 AM7/20/12
to
> A bad way to give help is to act like a total ass. This problem is well
> documented elsewhere. Lots of people are complaining about it. You could
> easily have found the information needed to give a helpful reply in the time
> it took you to give a snarky, unhelpful reply, twice.
Maybe you should learn to gather your thought before you start asking
> documented elsewhere. Lots of people are complaining about it. You could
> easily have found the information needed to give a helpful reply in the time
> it took you to give a snarky, unhelpful reply, twice.
random questions.
Anyway, what you're experiencing is the NSA checking up on your porn
habits. You look at a lot of spanking videos with your mother, right?
--
Fine then, I'm drinking coffee and rolling cigarettes and looking
out at the hot baked street and a lady just walked by wiggling it
in tight white pants, and we are not dead yet.
Mark Dintenfass
Jul 21, 2012, 9:51:36 AM7/21/12
to
In article <91bfcea7-b45f-4866...@googlegroups.com>,
your home Library folder, get info on it, and and deny permissions for
"everyone." I did the same thing in the root Library. That worked for
me.
BTW, thanks for the support, though arguing with Jolly Roger seems
counter-productive.
<frau.dr...@googlemail.com> wrote:
> there are some helpful suggestions at:
> https://productforums.google.com/forum/?fromgroups#!topic/chrome/yVump44eeOc
The solution is indeed there. You have to find GoogleSoftwareUpdate in
> there are some helpful suggestions at:
> https://productforums.google.com/forum/?fromgroups#!topic/chrome/yVump44eeOc
your home Library folder, get info on it, and and deny permissions for
"everyone." I did the same thing in the root Library. That worked for
me.
BTW, thanks for the support, though arguing with Jolly Roger seems
counter-productive.
Dav
Aug 2, 2012, 3:53:00 PM8/2/12
to xxmdin...@xxnew.rr.com
My guess is that it's probably nothing really serious. It's probably not an FBI agent tracking you.
It would probably be that Google wants to get usage statistics, and it wants to see if you are using the latest version of Google Earth.
You probably don't need to worry about it very much.
It would probably be that Google wants to get usage statistics, and it wants to see if you are using the latest version of Google Earth.
You probably don't need to worry about it very much.
dess...@conroeisd.net
May 2, 2016, 7:44:39 PM5/2/16
to
Your Name
May 2, 2016, 9:39:31 PM5/2/16
to
In article <56fc3eec-7b91-4228...@googlegroups.com>,
Mail, Google web browser searching with auto-suggestions ... there lots
of stuff it could be.
<dess...@conroeisd.net> wrote:
> On Thursday, July 12, 2012 at 3:00:27 PM UTC-5, Mark Dintenfass wrote:
> > I'm running a MacPro with Little Snitch installed and for several weeks
> > now there have been numerous and frequent attempts by Google to
> > establish a connection. At first I okayed the requests, then I started
> > denying them, and they're still appearing up to a dozen times a day. I
> > have a Google account, but I don't use any of the Google cloud
> > services. What's going on here?
Google cloud / drive, Google calendar synced to iCal, Google emails in
> On Thursday, July 12, 2012 at 3:00:27 PM UTC-5, Mark Dintenfass wrote:
> > I'm running a MacPro with Little Snitch installed and for several weeks
> > now there have been numerous and frequent attempts by Google to
> > establish a connection. At first I okayed the requests, then I started
> > denying them, and they're still appearing up to a dozen times a day. I
> > have a Google account, but I don't use any of the Google cloud
> > services. What's going on here?
Mail, Google web browser searching with auto-suggestions ... there lots
of stuff it could be.
Jolly Roger
May 2, 2016, 9:46:16 PM5/2/16
to
Your Name <Your...@YourISP.com> wrote:
>
> Google cloud / drive, Google calendar synced to iCal, Google emails in
> Mail, Google web browser searching with auto-suggestions ... there lots
> of stuff it could be.
You are responding to a Google Groups nitwit reply to a post over four
>
> Google cloud / drive, Google calendar synced to iCal, Google emails in
> Mail, Google web browser searching with auto-suggestions ... there lots
> of stuff it could be.
years old. ; )
--
E-mail sent to this address may be devoured by my ravenous SPAM filter.
I often ignore posts from Google. Use a real news client instead.
JR
0 new messages