- tor-relays - lists.torproject.org

NSA knew about Heartbleed
by Jesse Victors 13 Apr '14

13 Apr '14

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 Saw this article: http://www.bloomberg.com/news/2014-04-11/nsa-said-to-have-used-heartbleed-b… "The U.S. National Security Agency knew for at least two years about a flaw in the way that many websites send sensitive information, now dubbed the Heartbleed bug, and regularly used it to gather critical intelligence, two people familiar with the matter said. The NSA said in response to a Bloomberg News article that it wasn?t aware of Heartbleed until the vulnerability was made public by a private security report. The agency?s reported decision to keep the bug secret in pursuit of national security interests threatens to renew the rancorous debate over the role of the government?s top computer experts." Thanks NSA, glad you've got our backs there. If you run a relay and you have been on one of the affected versions of OpenSSL, I would urge you to STRONGLY CONSIDER your relay compromised. Delete your keys per the recommendations and let Tor generate new ones. It's better to cripple the network temporarily while we come back from this, rather than preserving the uptime with possibly compromised keys. Security matters here. Please follow the best practice recommendations. If you run a web server, rekey your SSL certificates. Basically, if you were affected, consider encryption to have been bypassed and passwords and other sensitive information compromised. We cannot afford to take chances here. If the NSA knew it, you can also bet that someone else with a good static analyzer discovered it as well, I'll let you imagine one. Good luck out there everyone, we really need to revoke our keys if we were affected. Seriously, guys. It's worth it. On a lighter note, https://xkcd.com/1354/ Stay safe. Live long and prosper. Jesse V. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.14 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQF8BAEBCgBmBQJTSImHXxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQxMjgyMjhENjEyODQ1OTU1NzBCMjgwRkFB RDk3MzY0RkMyMEJFQzgwAAoJEK2XNk/CC+yA0nIIAKj1lOXRGcwMFd39CxjnymSN FVzrPUa/JomCJHqW/A0xSFdxbVAZIvio6C1phuWHmiiDKhsBuBGwLNzXQMGFltaw BnaTO1lLCvvSbEdmXPg12hR3YqR1d5D7Xnb0iTlSfrjZ7gGDEsXoJG3pU/V/RCFo IOEqxfZtVcI3DdrImlwcR6gPw6ip9JlTo49w8ncy6/K4cHED2liCQ13JvWjaQzSl uB06eWNsNo1IhPCKkZ7gFzharhN/4kAQrytC+ZcTmIrXdPrsd1lUaVICHWK9AEon sciDu5lI77srXWwt77YVAKw6Jrls41N3USgvKBSrxZhfBVQlCPOmoXtTHdwbhks= =pmBQ -----END PGP SIGNATURE-----

10 13

Relays vulnerable to OpenSSL bug: Please upgrade
by Moritz Bartl 13 Apr '14

13 Apr '14

https://blog.torproject.org/blog/openssl-bug-cve-2014-0160 A new OpenSSL vulnerability on 1.0.1 through 1.0.1f is out today, which can be used to reveal memory to a connected client or server. If you're using an older OpenSSL version, you're safe. Note that this bug affects way more programs than just Tor — expect everybody who runs an https webserver to be scrambling today. If you need strong anonymity or privacy on the Internet, you might want to stay away from the Internet entirely for the next few days while things settle. Here are our first thoughts on what Tor components are affected: Clients: Tor Browser shouldn't be affected, since it uses libnss rather than openssl. But Tor clients could possibly be induced to send sensitive information like "what sites you visited in this session" to your entry guards. If you're using TBB we'll have new bundles out shortly; if you're using your operating system's Tor package you should get a new OpenSSL package and then be sure to manually restart your Tor. Relays and bridges: Tor relays and bridges could maybe be made to leak their medium-term onion keys (rotated once a week), or their long-term relay identity keys. An attacker who has your relay identity key can publish a new relay descriptor indicating that you're at a new location (not a particularly useful attack). An attacker who has your relay identity key, has your onion key, and can intercept traffic flows to your IP address can impersonate your relay (but remember that Tor's multi-hop design means that attacking just one relay in the client's path is not very useful). In any case, best practice would be to update your OpenSSL package, discard all the files in keys/ in your DataDirectory, and restart your Tor to generate new keys. Hidden services: Tor hidden services might leak their long-term hidden service identity keys to their guard relays. Like the last big OpenSSL bug, this shouldn't allow an attacker to identify the location of the hidden service, but an attacker who knows the hidden service identity key can impersonate the hidden service. Best practice would be to move to a new hidden-service address at your convenience. Directory authorities: In addition to the keys listed in the "relays and bridges" section above, Tor directory authorities might leak their medium-term authority signing keys. Once you've updated your OpenSSL package, you should generate a new signing key. Long-term directory authority identity keys are offline so should not be affected (whew). More tricky is that clients have your relay identity key hard-coded, so please don't rotate that yet. We'll see how this unfolds and try to think of a good solution there. Tails is still tracking Debian oldstable, so it should not be affected by this bug. Orbot looks vulnerable; we'll try to publish more details here soon. It looks like most of the webservers in the https://www.torproject.org/ rotation need upgrades too, and maybe we'll need to throw away our torproject SSL web cert and get a new one — hopefully we'll deal with all that soon. -- Moritz Bartl https://www.torservers.net/

20 29

Should I Worry @ INTRODUCE1 Warnings
by Tami Kennedy 12 Apr '14

12 Apr '14

Hello, non-exit relay (Tor 0.2.4.21) started seeing these log Warning entries. Concern or normal? Apr 05 06:02:40.810 Warning Rejecting INTRODUCE1 on non-OR or non-edge circuit 2147503731 Apr 05 06:49:47.107 Warning Rejecting INTRODUCE1 on non-OR or non-edge circuit 2147493910 -Tami

4 3

Re: [tor-relays] NSA knew about Heartbleed
by Eric Giannini 12 Apr '14

12 Apr '14

This is an excellent email. ------------------------------ On Fri, Apr 11, 2014 5:32 PM PDT Jesse Victors wrote: > >-----BEGIN PGP SIGNED MESSAGE----- >Hash: SHA512 > > >Saw this article: >http://www.bloomberg.com/news/2014-04-11/nsa-said-to-have-used-heartbleed-b… > >"The U.S. National Security Agency knew for at least two years about a >flaw in the way that many websites send sensitive information, now >dubbed the Heartbleed bug, and regularly used it to gather critical >intelligence, two people familiar with the matter said. The NSA said in >response to a Bloomberg News article that it wasn?t aware of Heartbleed >until the vulnerability was made public by a private security report. >The agency?s reported decision to keep the bug secret in pursuit of >national security interests threatens to renew the rancorous debate over >the role of the government?s top computer experts." > >Thanks NSA, glad you've got our backs there. > >If you run a relay and you have been on one of the affected versions of >OpenSSL, I would urge you to STRONGLY CONSIDER your relay compromised. >Delete your keys per the recommendations and let Tor generate new ones. >It's better to cripple the network temporarily while we come back from >this, rather than preserving the uptime with possibly compromised keys. >Security matters here. Please follow the best practice recommendations. >If you run a web server, rekey your SSL certificates. Basically, if you >were affected, consider encryption to have been bypassed and passwords >and other sensitive information compromised. We cannot afford to take >chances here. If the NSA knew it, you can also bet that someone else >with a good static analyzer discovered it as well, I'll let you imagine one. > >Good luck out there everyone, we really need to revoke our keys if we >were affected. Seriously, guys. It's worth it. > >On a lighter note, https://xkcd.com/1354/ > >Stay safe. Live long and prosper. >Jesse V. > >-----BEGIN PGP SIGNATURE----- >Version: GnuPG v1.4.14 (GNU/Linux) >Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ > >iQF8BAEBCgBmBQJTSImHXxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w >ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQxMjgyMjhENjEyODQ1OTU1NzBCMjgwRkFB >RDk3MzY0RkMyMEJFQzgwAAoJEK2XNk/CC+yA0nIIAKj1lOXRGcwMFd39CxjnymSN >FVzrPUa/JomCJHqW/A0xSFdxbVAZIvio6C1phuWHmiiDKhsBuBGwLNzXQMGFltaw >BnaTO1lLCvvSbEdmXPg12hR3YqR1d5D7Xnb0iTlSfrjZ7gGDEsXoJG3pU/V/RCFo >IOEqxfZtVcI3DdrImlwcR6gPw6ip9JlTo49w8ncy6/K4cHED2liCQ13JvWjaQzSl >uB06eWNsNo1IhPCKkZ7gFzharhN/4kAQrytC+ZcTmIrXdPrsd1lUaVICHWK9AEon >sciDu5lI77srXWwt77YVAKw6Jrls41N3USgvKBSrxZhfBVQlCPOmoXtTHdwbhks= >=pmBQ >-----END PGP SIGNATURE----- > >_______________________________________________ >tor-relays mailing list >tor-relays(a)lists.torproject.org >https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays

1 0

Long-term effect of Heartbleed on Tor
by Tom van der Woerdt 10 Apr '14

10 Apr '14

What's the long-term effect of Heartbleed on Tor? * Should we consider every key that was created before Tuesday a bad key and lower their consensus weight? * Should authorities scan for bad OpenSSL versions and force their weight down to 20? A lot of relays will continue running bad OpenSSL versions which seriously hurts the security of Tor. A month from now the NSA/CGHQ/CIVD/etc may know the private keys of a large chunk of these relays and possibly be able to decode a big chunk of traffic... Tom

6 7

Re: [tor-relays] Strange Problem Browsing Blocked Websites‏
by sssheep 10 Apr '14

10 Apr '14

On Thu, 10 Apr 2014 04:26:27 +0000 (UTC) Enrique Fynn <enriquefynn(a)gmail.com> wrote: > On 10 April 2014 01:01, Tor Relays at brwyatt.net <tor(a)brwyatt.net> > wrote: > > > > If I remember correctly, Firefox has a bug where it won't do DNS > > lookups over a SOCKS proxy. It will, however do DNS lookups through > > an HTTP proxy that supports it, such as Polipo. If you configure > > Polipo to act as an HTTP proxy that forwards to the Tor SOCKS > > proxy, and add Polipo to your Firefox config as an HTTP proxy (you > > can leave Tor's SOCKS proxy entry), this may resolve the issue your > > are seeing, assuming DNS blocking/filtering in your country. > > > > Bryan > > That's not a bug, it's firefox default behavior. To change this: > 1- Go to about:config > 2- Set network.proxy.socks_remote_dns to true > This is set already in TBB which you should be using. It exists for a reason, use it instead of attempting to create your own solution.

1 0

Strange Problem Browsing Blocked Websites‏
by Ferdi GULER 10 Apr '14

10 Apr '14

Hello All, Today I have installed tor on my raspberry pi and also set it up as a relay. I can monitor tor traffic using arm so it means it is working. My SocksPort configuration is 9050, 192.168.1.187:9050 where 192.168.1.187 is internal ip of my raspberry pi.In order to anonymize my browsing traffic on my main windows PC, I configured Firefox to use my raspberry pi as proxy on port 9050. When I visit the page https://check.torproject.org/, it says my configuration is successful and I see different ip address. From that point I assume everything should work properly but if I try to browse web sites that are blocked in my country such as youtube it just does not connect. However if I use VPN I can see those blocked web sites. So could anyone please tell me what is wrong with my configuration? I'm realy confused... Thanks in advance!

4 4

Atlas Entry
by Tor Relay 09 Apr '14

09 Apr '14

My several attempts to update to TBB 3.5.4 (XP)unsuccessfully made Tor exit upon starting, so I fell back to 3.5.3. Atlas shows that my efforts hadn't gone unnoticed; OnionTorte now appears four times w/ my IP address. 0D50D43BAA728D6E0C4EB181AB79E5C1D7036D08 is the correct one but it somehow has my bandwidth as 489 KB when it should be 921.6 KB, reflecting my RelayBandwidthRate. Does anybody have a way of clearing the ghost entries and setting Atlas straight on my bandwidth? Thanks, P -- Dirt kicked to the curb goes into the gutter. Professionals kicked to the curb go into retail.

2 1

Re: [tor-relays] Relays vulnerable to OpenSSL bug: Please upgrade
by tor＠t-3.net 09 Apr '14

09 Apr '14

On 04/09/2014 04:39 AM, Roger Dingledine wrote:> On Tue, Apr 08, 2014 at 07:31:43PM -0600, Jesse Victors wrote: >> I'd recommend that every relay operator delete their keys as well, > > Not every. Those on OpenSSL 0.9.8, e.g. because they're using Debian > oldstable, were never vulnerable to this bug. I imagine there are some > FreeBSD or the like people out there in a similar boat. And Centos > people, etc. > > --Roger > > _______________________________________________ > tor-relays mailing list > tor-relays(a)lists.torproject.org > https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays > > > The most up-to-date CentOS was supposedly vulnerable? Same as RedHat. But I don't know how to test for the vulnerability itself so I don't really know. Redhat's emailed warning to update OpenSSL went out yesterday as "Security Advisory - RHSA-2014:0376-1". CentOS' updated OpenSSL was available right away as well, and the CentOS 6.5 boxes pulled it right down in an update. I did have some slightly older CentOS 5 boxes which had a version of SSL that was reportedly not vulnerable. Page heartbleed.com said: How about operating systems? Some operating system distributions that have shipped with potentially vulnerable OpenSSL version: Debian Wheezy (stable), OpenSSL 1.0.1e-2+deb7u4 Ubuntu 12.04.4 LTS, OpenSSL 1.0.1-4ubuntu5.11 CentOS 6.5, OpenSSL 1.0.1e-15 Fedora 18, OpenSSL 1.0.1e-4 OpenBSD 5.3 (OpenSSL 1.0.1c 10 May 2012) and 5.4 (OpenSSL 1.0.1c 10 May 2012) FreeBSD 10.0 - OpenSSL 1.0.1e 11 Feb 2013 NetBSD 5.0.2 (OpenSSL 1.0.1e) OpenSUSE 12.2 (OpenSSL 1.0.1c) Operating system distribution with versions that are not vulnerable: Debian Squeeze (oldstable), OpenSSL 0.9.8o-4squeeze14 SUSE Linux Enterprise Server FreeBSD 8.4 - OpenSSL 0.9.8y 5 Feb 2013 FreeBSD 9.2 - OpenSSL 0.9.8y 5 Feb 2013 FreeBSD Ports - OpenSSL 1.0.1g (At 7 Apr 21:46:40 2014 UTC)

2 1

any action required for AWS cloud relays?
by lee colleton 09 Apr '14

09 Apr '14

I have relay(s) running in AWS. Will they auto-update? Do I need to take any action?

3 3