- Nov 23, 2010
-
-
Roger Dingledine authored
-
- Nov 21, 2010
-
-
Roger Dingledine authored
-
Roger Dingledine authored
-
Nick Mathewson authored
-
Nick Mathewson authored
-
Nick Mathewson authored
This may fix bug 2204, and resolve the incompatibility with openssl 0.9.8p/1.0.0b.
-
- Nov 19, 2010
-
-
Nick Mathewson authored
-
Nick Mathewson authored
-
Robert Ransom authored
-
Robert Ransom authored
Spotted by Nick Mathewson.
-
Nick Mathewson authored
-
- Nov 17, 2010
-
-
Robert Ransom authored
Fixes bug #2195.
-
Robert Ransom authored
-
Karsten Loesing authored
-
- Nov 16, 2010
-
-
Roger Dingledine authored
-
Roger Dingledine authored
-
Roger Dingledine authored
-
Roger Dingledine authored
-
Roger Dingledine authored
-
Roger Dingledine authored
-
Nick Mathewson authored
Sebastian notes (and I think correctly) that one of our ||s should have been an &&, which simplifies a boolean expression to decide whether to replace bridges. I'm also refactoring out the negation at the start of the expression, to make it more readable.
-
- Nov 15, 2010
-
-
Nick Mathewson authored
-
Nick Mathewson authored
-
Nick Mathewson authored
-
Nick Mathewson authored
-
Nick Mathewson authored
-
Pick 5 seconds as the limit. 5 seconds is a compromise here between making sure the user notices that the bad behaviour is (still) happening and not spamming their log too much needlessly (the log message is pretty long). We also keep warning every time if safesocks is specified, because then the user presumably wants to hear about every blocked instance. (This is based on the original patch by Sebastian, then backported to 0.2.2 and with warnings split into their own function.)
-
Karsten Loesing authored
-
Karsten Loesing authored
Our checks that we don't exceed the 50 KB size limit of extra-info descriptors apparently failed. This patch fixes these checks and reserves another 250 bytes for appending the signature. Fixes bug 2183.
-
- Nov 12, 2010
-
-
Nick Mathewson authored
In all likelihood, this bug would make Tor assert, but if it doesn't, let's not have two bugs.
-
Nick Mathewson authored
-
Nick Mathewson authored
-
Nick Mathewson authored
-
Nick Mathewson authored
-
Robert Ransom authored
If buf_shrink_freelists calls log_warn for some reason, we don't want the log call itself to throw buf_shrink_freelists further off the rails.
-
Robert Ransom authored
Sending a log message to a control port can cause Tor to allocate a buffer, thereby changing the length of the freelist behind buf_shrink_freelists's back, thereby causing an assertion to fail. Fixes bug #1125.
-
Robert Ransom authored
If buf_shrink_freelists calls log_warn for some reason, we don't want the log call itself to throw buf_shrink_freelists further off the rails.
-
Robert Ransom authored
Sending a log message to a control port can cause Tor to allocate a buffer, thereby changing the length of the freelist behind buf_shrink_freelists's back, thereby causing an assertion to fail. Fixes bug #1125.
-
- Nov 11, 2010
-
-
Nick Mathewson authored
-
Roger Dingledine authored
-