I'm supposedly running one of the still affected tor-relays and since my relay is also a guard, I'm in the latest blocklist[1] (pre-upgrade fingerprint). I did upgrade the system on April 9th to openssl 1.0.1-4ubuntu5.12 - base system is an ubuntu 12.04.
According to the changelog[2], this should have fixed the heartbleed issue and according to this scanner[3], it should be as well. I did create new keys anyway, but just to be sure: Is the host[4] still affected as given in the blocklist?
Best, Lars __________________________________ [1] https://atlas.torproject.org/#details/9AB511B6894566C1CF56043CE60077D213CF1A... [2] https://launchpad.net/ubuntu/+source/openssl/1.0.1-4ubuntu5.12 [3] https://filippo.io/Heartbleed/#tor.kumbier.it [4] tor running on 5.9.165.90:443
Am 17.04.2014 20:08, schrieb Tom van der Woerdt:
A lot of relay operators were contacted within 12 hours of the heartbleed bug being published. Of course, not everyone lists their mail address in the directory, so those didn't get contacted.
Tom
AJ B schreef op 17/04/14 20:04:
Can we do anything to attempt to contact those relay operators that are still affected by Heartbleed?
I might be a little late to the discussion and this has already taken place, just wanted to check.
On Thu, Apr 17, 2014 at 9:47 AM, Saint Aardvark the Carpeted aardvark@saintaardvarkthecarpeted.com wrote:
Tobias, thanks so much for the explanation!
-- Saint Aardvark the Carpeted http://saintaardvarkthecarpeted.com Because the plural of Anecdote is Myth.
tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays