On Wed, Apr 9, 2014 at 3:31 PM, Geri toxir...@gmail.com wrote:
Hi Guys,
im running also a few guard relays and they are listed in here - but today
i've patched and restarted all the nodes - so these logs arent actually
anymore.
what does it mean, available for challenger?
Note that this
After updating the OpenSSL, I chopped our relay's keys at noon EST
yesterday. The traffic has indeed collapsed since then. Old
configuration was averaging around 55Mb/s per my Cacti. A URL here:
https://atlas.torproject.org/#details/566B0F92197A9D855846E68D2AEEF8266B147D35
This morning my
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
Hi,
I recall that Roger Dingledine pointed out that this is a stress situation
for the whole network, but the flags should be in order in just a few days
time.
Better to update OpenSSL right now, discard everything in /keys and wait
for the recovery. I expect that the vast majority of the
I've also noticed a big uptick in traffic in the last 24/48 hours which has
somewhat overwhelmed my poor Raspberry Pi :( guess we sit tight and wait
for things to settle.
On 9 Apr 2014 15:27, Sebastian Urbach sebast...@urbach.org wrote:
Hi,
I recall that Roger Dingledine pointed out that this
Hi,
I want to clarify my mail from earlier today regarding the recovery of the
network / relays.
I wrote that i expect business as usual within 2-3 days for the vast
majority of the relays. That does not mean that everything is the way it
was before.
When the content of the /keys
Sorry, I mean this in light of CVE-2014-0160 the Heartbleed OpenSSL bug
On Wed, Apr 9, 2014 at 11:04 AM, lee colleton l...@colleton.net wrote:
I have relay(s) running in AWS. Will they auto-update? Do I need to take
any action?
___
tor-relays
The Tor Cloud AMIs (if that's what you're using) are configured to
auto-update and restart if necessary.
But it probably can't hurt to check that you have the fixed OpenSSL
package.
Best regards,
Alexander
---
PGP Key: 0xC55A356B | https://dietrich.cx/pgp
On 2014-04-09 20:05, lee
2014-04-09 20:51 GMT+02:00 Paul Pearce pea...@cs.berkeley.edu:
* Should authorities scan for bad OpenSSL versions and force their weight
down to 20?
I'd be interested in hearing people's thoughts on how to do such
scanning ethically (and perhaps legally). I was under the impression
the
TvdW
* Should we consider every key that was created before Tuesday
You'd need to also know the key was created by vulnerable
openssl 1.0.1 versions, didn't already disable heartbeat, etc.
That data isn't announced in the consensus. And those that
weren't vulnerable may be happy continuing with
On Wed, Apr 9, 2014 at 3:21 PM, Ferdi GULER ferdigu...@outlook.com wrote:
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
On Wed, Apr 9, 2014 at 10:33 AM, Tor Relay
t...@microcephalic-endeavors.com wrote:
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
On 10 April 2014 01:01, Tor Relays at brwyatt.net t...@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
On Thu, 10 Apr 2014 01:20:51 -0300, Enrique Fynn enriquef...@gmail.com
wrote:
On 10 April 2014 01:01, Tor Relays at brwyatt.net t...@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
14 matches
Mail list logo
