Hi folks,
I just released 0.2.4.17-rc. Hopefully there will be debs of it soon.
It comes with a new feature:
- Relays now process the new NTor circuit-level handshake requests
with higher priority than the old TAP circuit-level handshake
requests. We still process some TAP
On Thu, Sep 05, 2013 at 06:54:57AM -0400, Roger Dingledine wrote:
In my spare time I'm also working on a blog post to explain what's going
on and what measures we're taking to keep things afloat.
https://blog.torproject.org/blog/how-to-handle-millions-new-tor-clients
--Roger
On 09/05/2013 03:20 PM, Roger Dingledine wrote:
On Thu, Sep 05, 2013 at 06:54:57AM -0400, Roger Dingledine wrote:
In my spare time I'm also working on a blog post to explain what's going
on and what measures we're taking to keep things afloat.
On Thu, Sep 5, 2013 at 7:12 PM, Lunar lu...@torproject.org wrote:
For those in a hurry, automatically built packages are available by
adding the following in your sources.list:
I see the following messages, which I was not seeing earlier. It
eventually completes bootstrapping, 100%:
Sep 05
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Just to add my experiences to the mix:
I started running a RPi relay back in January. It ran fine for several
months, until I started to get these circuit creation storms
periodically. It would come at random times, maybe once a week, and
would
Don't know if this is update specific or just because of the new users
in the network:
17:00:25 [WARN] Your Guard curiosity3
($07AE80AA2F475282E3C08F589826C8FB19E8086B) is failing a very large
amount of circuits. Most likely this means
the Tor network is overloaded, but it could also mean an
Hi all,
After running my relay for a bit on my home connection I found that
Tor would happily consume all the bandwidth available, which
(coupled with the number of connections overwhelming my home router,
I suspect) caused my internet connection to be unusable for other
things.
So I set the
On Thu, 05 Sep 2013 17:04:15 +0200
virii vi...@enn.lu wrote:
Don't know if this is update specific or just because of the new users
in the network:
I had this on 0.2.4.16, so not update-specific.
--
With respect,
Roman
signature.asc
Description: PGP signature
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Upgraded to 0.2.4.17-rc and almost immediately got the following in my
syslog:
debian kernel: [5000394.949751] TCP: Possible SYN flooding on port 443.
Sending cookies. Check SNMP counters.
No idea what it means. 443 is my or port. Tor is running
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Roger Dingledine:
Hi folks,
I just released 0.2.4.17-rc. Hopefully there will be debs of it
soon.
I will get binary debs for Raspbian completed this evening, and this
time sign them with my public key[1] for anyone who chooses to trust
me.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Nice, thank you :)
Let's see, how Tor reacts on this :D
Roger Dingledine a...@mit.edu schrieb:
Hi folks,
I just released 0.2.4.17-rc. Hopefully there will be debs of it soon.
It comes with a new feature:
- Relays now process the new NTor
On Thu, Sep 05, 2013 at 06:54:57AM -0400, Roger Dingledine wrote:
So the more relays that upgrade to 0.2.4.17-rc, the more stable and fast
Tor will be for 0.2.4 users, despite the huge circuit overload that the
network is seeing.
Please consider upgrading. If you do, though, please also keep
Updated torland family. Hope that the new version helps. One of the last
messages before update to 0.2.4.17-rc:
Sep 05 21:06:29.000 [warn] Your computer is too slow to handle this many
circuit creation requests! Please consider using the
MaxAdvertisedBandwidth config option or choosing a more
On Sep 5, 2013, at 20:13 , Kevin C. Krinke wrote:
Machine's performance and resource usage are all within allowed norms (in
fact running better than the 2.3.x release).
I concur with Kevin that this built is running smoothly:
Sep 05 21:24:37.000 [notice] Circuit handshake stats since last
On Thursday 05 September 2013 22:27:53 tor-admin wrote:
Updated torland family. Hope that the new version helps. One of the last
messages before update to 0.2.4.17-rc:
Sep 05 21:06:29.000 [warn] Your computer is too slow to handle this many
circuit creation requests! Please consider using
Hello, Tor community. Quick, possibly noobish question. I'd like to use
my desktop and connect ARM (running on the desktop) to the control port
of a server running Tor on the same LAN, but it's refusing the
connection. I'm running /sudo -u tor arm -i 10.0.0.3:9051/, and it outputs:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 06.09.2013 06:01, Robert Charlton wrote:
Hello, Tor community. Quick, possibly noobish question. I'd like to
use my desktop and connect ARM (running on the desktop) to the
control port of a server running Tor on the same LAN, but it's
refusing
17 matches
Mail list logo
