<div dir="ltr"><a href="https://github.com/EFForg/https-everywhere/blob/9651d668da793c7791f778f4fae0b654099122d9/src/components/ssl-observatory.js#L852">https://github.com/EFForg/https-everywhere/blob/9651d668da793c7791f778f4fae0b654099122d9/src/components/ssl-observatory.js#L852</a><br>
</div><div class="gmail_extra"><br><br><div class="gmail_quote">On Fri, Feb 28, 2014 at 1:57 PM, Seth David Schoen <span dir="ltr"><<a href="mailto:schoen@eff.org" target="_blank">schoen@eff.org</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="HOEnZb"><div class="h5">Dave Warren writes:<br>
<br>
> On 2014-02-28 08:21, <a href="mailto:paulrcc@hushmail.com">paulrcc@hushmail.com</a> wrote:<br>
> >On 02/19/2014 at 10:40 PM, "Daniel Kahn Gillmor"<br>
> ><<a href="mailto:dkg@fifthhorseman.net">dkg@fifthhorseman.net</a>> wrote:<br>
> ><br>
> >    On 02/19/2014 08:41 AM, <a href="mailto:paulrcc@hushmail.com">paulrcc@hushmail.com</a> wrote:<br>
> >    > I use Firefox plugin and I detected connections to<br>
> >    localhost:9050 when<br>
> >    > HTTPS-Everywhere plugin is enabled. When plugin is disabled,<br>
> >    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>
> ><br>
> ><br>
> >No, I did no proxy configuration. I just installed Firefox with<br>
> >HTTPS Everywhere and when the plugin is enabled my firewall<br>
> >detects connections to <a href="http://127.0.0.1:9050" target="_blank">127.0.0.1:9050</a>.<br>
><br>
> Given that HTTPS Everywhere has some internal Tor support, I wonder<br>
> if it's simply checking to see if a typical Tor install is<br>
> available?<br>
<br>
</div></div>Yes, this has to do with the Observatory wanting to submit cert<br>
observations via Tor.  If the Observatory is enabled with default<br>
settings, it looks for a Tor proxy on localhost:9050.  You should<br>
be able to stop this (if it isn't what you want) with the HTTPS<br>
Everywhere SSL Observatory Preferences by disabling all Observatory<br>
reporting.<br>
<br>
Note that if Tor isn't installed, the failed connections to port<br>
9050 won't harm anything -- depending on your Observatory settings,<br>
they'd just cause HTTPS Everywhere to conclude that you don't have Tor<br>
installed and then not submit any observations to the Observatory.<br>
<br>
You can see the details of the implementation of this functionality in<br>
<br>
<a href="https://gitweb.torproject.org/https-everywhere.git/blob/HEAD:/src/components/ssl-observatory.js" target="_blank">https://gitweb.torproject.org/https-everywhere.git/blob/HEAD:/src/components/ssl-observatory.js</a><br>

<span class="HOEnZb"><font color="#888888"><br>
--<br>
Seth Schoen  <<a href="mailto:schoen@eff.org">schoen@eff.org</a>><br>
Senior Staff Technologist                       <a href="https://www.eff.org/" target="_blank">https://www.eff.org/</a><br>
Electronic Frontier Foundation                  <a href="https://www.eff.org/join" target="_blank">https://www.eff.org/join</a><br>
815 Eddy Street, San Francisco, CA  94109       <a href="tel:%2B1%20415%20436%209333%20x107" value="+14154369333">+1 415 436 9333 x107</a><br>
_______________________________________________<br>
HTTPS-Everywhere mailing list<br>
<a href="mailto:HTTPS-Everywhere@lists.eff.org">HTTPS-Everywhere@lists.eff.org</a><br>
<a href="https://lists.eff.org/mailman/listinfo/https-everywhere" target="_blank">https://lists.eff.org/mailman/listinfo/https-everywhere</a><br>
</font></span></blockquote></div><br></div>