On 24/04/2017 5:33 AM, Frank-Rainer Grahl wrote:
Likely the initial blocklist, safebrowsing and tracking protection
updates. You can add a bool browser.safebrowsing.debug in about:config
and set it to true. You should see some additional messages during start
in the console then.
FRG
Richmond wrote:
There is a thread in the firefox group about firefox connecting to
cloudfront. While looking into that I checked on seamonkey and I see the
same:
tcp 0 0 192.168.1.3:54212
server-54-192-129-202.ams50.r.cloudfront.net:https ESTABLISHED
2341/seamonkey
tcp 0 0 192.168.1.3:50642
server-54-192-185-116.cdg51.r.cloudfront.net:https ESTABLISHED
2341/seamonkey
tcp 0 0 192.168.1.3:47018
ec2-54-68-119-170.us-west-2.compute.amazonaws.com:https ESTABLISHED
2341/seamonkey
This is a new profile and I have set the home page to blank. These
connections are made when I launch seamonkey before I do anything else.
What are they about? Is it copies from firefox core code?
Sorry, Frank-Rainer, but are you suggesting that, straight out of the
box, my SeaMonkey is "phoning home" to these three (and, possible,
other) servers every time I connect to the Internet WITHOUT MY PERMISSION??
If so, can you please provide further information ....
1. How can I stop this "phoning home",
2. What might I break if I disable this "phoning home", and,
3. What SM function may break if I disable this function??
(So much of the SPAM I receive seems to originate from amazonaws that I
would rather avoid it if I can!!)
--
Daniel
User agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:49.0) Gecko/20100101
SeaMonkey/2.46 Build identifier: 20161213183751
_______________________________________________
support-seamonkey mailing list
[email protected]
https://lists.mozilla.org/listinfo/support-seamonkey
