<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">On 2014-02-28 08:21,
<a class="moz-txt-link-abbreviated" href="mailto:paulrcc@hushmail.com">paulrcc@hushmail.com</a> wrote:<br>
</div>
<blockquote cite="mid:20140228162158.9027AA0159@smtp.hushmail.com"
type="cite"><span style="font-family: Arial; font-size: 13px;">On
02/19/2014 at 10:40 PM, "Daniel Kahn Gillmor"
<a class="moz-txt-link-rfc2396E" href="mailto:dkg@fifthhorseman.net"><dkg@fifthhorseman.net></a> wrote:
<blockquote style="border-left:solid 1px
#ccc;margin-left:10px;padding-left:10px;">On 02/19/2014 08:41
AM, <a class="moz-txt-link-abbreviated" href="mailto:paulrcc@hushmail.com">paulrcc@hushmail.com</a> wrote:<br>
> I use Firefox plugin and I detected connections to
localhost:9050 when<br>
> HTTPS-Everywhere plugin is enabled. When plugin is
disabled, this does<br>
> not occur. Observatory is disabled.<br>
<br>
localhost:9050 is a common port for the system tor socks proxy
to run<br>
on. Are you sure you didn't also do some sort of tor
configuration or<br>
reconfigure your proxy settings around the same time as
installing<br>
https-everywhere<br>
</blockquote>
<br>
No, I did no proxy configuration. I just installed Firefox with
HTTPS Everywhere and when the plugin is enabled my firewall
detects connections to 127.0.0.1:9050.</span><br>
</blockquote>
<br>
Given that HTTPS Everywhere has some internal Tor support, I wonder
if it's simply checking to see if a typical Tor install is
available?<br>
<pre class="moz-signature" cols="72">--
Dave Warren
<a class="moz-txt-link-freetext" href="http://www.hireahit.com/">http://www.hireahit.com/</a>
<a class="moz-txt-link-freetext" href="http://ca.linkedin.com/in/davejwarren">http://ca.linkedin.com/in/davejwarren</a>
</pre>
</body>
</html>