* Nick Mathewson wrote:
> There's a new alpha Tor release! Because it's an alpha, you should
> only run it if you're ready to find more bugs than usual, and
> report them on gitlab.torproject.org.
it isnt mentioned in the changelog, but this is rather important:
Mar 19 18:57:00.911 [warn] Onio
* Marco Gruß wrote:
> the other day I just for the fun of it tried using a public
> relay as a non-obfuscated bridge - it actually works.
As it should.
> Curious: Would be using a public relay I implicitly trust (operated
> by a friend, operated by me, operated by the NSA) as a bridge be a
> g
* nusenu wrote:
> nusenu:
> > this has been caused by a measurement infrastructure problem (op-hk
> > outage) - question answered by kasten
> this should read: "Karsten"
you and your replay attacks...
--
left blank, right bald
--
tor-talk mailing list - tor-talk@lists.torproject.org
To unsub
* InterN0T wrote:
> The real question is, what are they going to spend that million on?
Some fine cigars & whiskey (alfa foxtrot) and a reliable ISP -
probably not in that order.
--
tor-talk mailing list - tor-talk@lists.torproject.org
To unsubscribe or change other settings go to
https://lists
* krugar wrote:
> cheers :S
I fully concur :-/
--
tor-talk mailing list - tor-talk@lists.torproject.org
To unsusbscribe or change other settings go to
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-talk
* The Doctor wrote:
> Did something go pear-shaped with check.torproject.org? I've not
> been able to get it to respond (through the TBB or otherwise) for
> the past day or so.
It just works for me. Does https://check.extc.org/ work for you?
--
Tahoe-LAFS - You see this name, you think dirty.
* Andreas Krey wrote:
> I'm more interested in why I get smothered in circuits all of a sudden.
No idea what might be the root cause, but I've stumbled upon the very
same log message a few times.
Have a look at this:
https://lists.torproject.org/pipermail/tor-relays/2012-May/001352.html
HTH
-
