- Sep 24, 2013
-
-
Nick Mathewson authored
-
-
- Sep 23, 2013
-
-
Nick Mathewson authored
Makes mingw64 a bit happier.
-
Nick Mathewson authored
-
Nick Mathewson authored
-
- Sep 21, 2013
-
-
Nick Mathewson authored
-
Nick Mathewson authored
This avoids skew warnings as authorities test reachability. Fix 9798; fix not on any released Tor.
-
Roger Dingledine authored
-
Roger Dingledine authored
this was causing directory authorities to send a time of 0 on all connections they generated themselves, which means everybody reachability test caused a time skew warning in the log for that relay. (i didn't just revert, because the changes file has been modified by other later commits.)
-
- Sep 20, 2013
-
-
Nick Mathewson authored
-
Nick Mathewson authored
-
Nick Mathewson authored
-
Nick Mathewson authored
Implements part of proposal 222. We can do this safely, since REND_CACHE_MAX_SKEW is 24 hours.
-
Nick Mathewson authored
This isn't actually much of an issue, since only relays send AUTHENTICATE cells, but while we're removing timestamps, we might as well do this too. Part of proposal 222. I didn't take the approach in the proposal of using a time-based HMAC, since that was a bad-prng-mitigation hack from SSL3, and in real life, if you don't have a good RNG, you're hopeless as a Tor server.
-
Nick Mathewson authored
For now, round down to the nearest 10 minutes. Later, eliminate entirely by setting a consensus parameter. (This rounding is safe because, in 0.2.2, where the timestamp mattered, REND_REPLAY_TIME_INTERVAL was a nice generous 60 minutes.)
-
Nick Mathewson authored
Implements part of proposal 222.
-
Nick Mathewson authored
a9910d89 added trickery to make us work with interned strings and seccomp; it requires libevent 2. Fix for 9785; bug not in any released tor.
-
- Sep 19, 2013
-
-
Nick Mathewson authored
-
Nick Mathewson authored
-
Nick Mathewson authored
I broke this when I added separate test-mode support by having the benchmarks get built with TEST_CFLAGS.
-
- Sep 17, 2013
-
-
Nick Mathewson authored
-
Nick Mathewson authored
tor_malloc returns void *; in C, it is not necessary to cast a void* to another pointer type before assigning it. tor_malloc fails with an error rather than returning NULL; it's not necessary to check its output. (In one case, doing so annoyed Coverity.)
-
- Sep 16, 2013
-
-
Nick Mathewson authored
Whenever we had an non-option commandline arguments *and* option-bearing commandline arguments on the commandline, we would save only the latter across invocations of options_init_from_torrc, but take their existence as license not to re-parse the former. Yuck! Incidentally, this fix lets us throw away the backup_arg[gv] logic. Fix for bug 9746; bugfix on d98dfb37, not in any released Tor. Found by Damian. Thanks, Damian!
-
Nick Mathewson authored
-
Nick Mathewson authored
-
Nick Mathewson authored
-
Nick Mathewson authored
-
- Sep 13, 2013
-
-
Nick Mathewson authored
-
Nick Mathewson authored
Bugfix on 12938354, which implemented 6752: Not in any released tor.
-
Nick Mathewson authored
Conflicts: src/or/config.c src/or/main.c
-
Nick Mathewson authored
-
Nick Mathewson authored
-
Nick Mathewson authored
-
Nick Mathewson authored
-
Nick Mathewson authored
This just goes to show: never cast a function pointer. Found while testing new command line parse logic. Bugfix on 12938354, which implemented 6752: Not in any released tor.
-
Nick Mathewson authored
And have these various commandline options imply "hush", not "quiet", since we like to see warnings.
-
Nick Mathewson authored
(incomplete)
-
Nick Mathewson authored
Fixes bug 9573. Bugfix on 59453ac6 in 0.0.9pre5, which fixed a crash in a silly way.
-
Nick Mathewson authored
-
Nick Mathewson authored
These were previously allowed only in the initial position: --help, -h , --version, --digests, --list-torrc-options
-