summaryrefslogtreecommitdiff
AgeCommit message (Collapse)Author
2010-01-19bump to 0.2.2.7-alphator-0.2.2.7-alphaRoger Dingledine
2010-01-19note the two new fixes are in 0.2.2.7-alpha tooRoger Dingledine
2010-01-19Merge branch 'maint-0.2.1'Roger Dingledine
Conflicts: ChangeLog
2010-01-19spread guard rotation out throughout the monthRoger Dingledine
2010-01-19weight guard choice by bandwidth; discard old guardsRoger Dingledine
2010-01-19add changelog entries for my commits from last weekRoger Dingledine
2010-01-19clean 0.2.2.7-alpha changelog; add 0.2.2.6 blurbRoger Dingledine
also reorder the stable changelog entries so they're in temporal order
2010-01-19Merge branch 'maint-0.2.1' into masterRoger Dingledine
Conflicts: ChangeLog configure.in contrib/tor-mingw.nsi.in src/win32/orconfig.h
2010-01-19bump to 0.2.1.22, and give it a changelogtor-0.2.1.22Roger Dingledine
2010-01-19downgrade a warningRoger Dingledine
this case can now legitimately happen, if you have a cached v2 status from moria1, and you run with the new list of dirservers that's missing the old moria1. it's nothing to worry about; the file will die off in a month or two.
2010-01-19rotate keys for moria1 and gabelmooRoger Dingledine
2010-01-19Fix build on Solaris by disabling support for DisableAllSwapSebastian Hahn
Fixes bug 1198. Solaris doesn't have RLIMIT_MEMLOCK for get/setrlimit, so disable support because we don't know if all memory can be locked.
2010-01-18Build Bug: -lm should come after passing ../common/libor.a to linkerMichael Witten
The following commit: commit e56747f9cf29ed788baf8805bfe391925d8a19da Author: Nick Mathewson <nickm@torproject.org> Date: Tue Dec 15 14:32:55 2009 -0500 Refactor a bit so that it is safe to include math.h, and mostly not needed. introduced this line: tor_resolve_LDADD = -lm ../common/libor.a @TOR_LIB_WS32@ which caused the build to fail, because only ../common/libor.a (via the embedded ../common/util.o via ../common/util.c) referenced libm's `lround' and `log' symbols, so that the linker (GNU ld) didn't bother to import those symbols before reading ../common/libor.a, thus leaving those symbols undefined. The solution was to swap the order, producing the line: tor_resolve_LDADD = ../common/libor.a -lm @TOR_LIB_WS32@ Signed-off-by: Michael Witten <mfwitten@gmail.com>
2010-01-18Log a notice when we get a new control connectionSebastian Hahn
2010-01-17stop bridge authorities from leaking their bridge listRoger Dingledine
2010-01-16Merge remote branch 'origin/maint-0.2.1'Nick Mathewson
Conflicts: ChangeLog configure.in contrib/tor-mingw.nsi.in src/win32/orconfig.h
2010-01-15whitespace fixesRoger Dingledine
2010-01-15fix an impossible-to-actually-trigger overflow in descriptor generationRoger Dingledine
2010-01-15resolve path weighting edge case; fixes bug 1203Roger Dingledine
2010-01-15trivial cleanupsRoger Dingledine
2010-01-15fix some typos in our spec filesRoger Dingledine
2010-01-15man page entries for PerConnBW{Rate,Burst}Roger Dingledine
2010-01-15remove redundant validate_addr_policies() checksRoger Dingledine
2010-01-15don't warn if stats/bridge-stats is missingRoger Dingledine
if we try to read it to publish stats and it's not there, that means there are no stats to publish. reported by swisstorexit.
2010-01-15don't list windows capabilities in windows unameRoger Dingledine
we never used them, and maybe it's a bad idea to publish them
2010-01-15ship the bridges spec file in the tarball tooRoger Dingledine
2010-01-02don't div by 0 during path selectionRoger Dingledine
2010-01-02when loading bridge stats, mkdir $datadir/stats firstRoger Dingledine
2009-12-29add config options to override.Roger Dingledine
somebody should add man page entries.
2009-12-29add separate per-conn write limitingRoger Dingledine
2009-12-25Authorities now support conditional consensusesSebastian Hahn
Mark them this way in add_trusted_dir_server
2009-12-25Remove some old, commented out codeSebastian Hahn
2009-12-25Remove online config descriptions.Sebastian Hahn
They weren't in sync with reality nor manpage, and only useful to a human who could simply have checked the manpage.
2009-12-25Fix a typoSebastian Hahn
2009-12-23New consensus params "bwconnrate" and "bwconnburst"Roger Dingledine
...to let us rate-limit client connections as they enter the network. It's controlled in the consensus so we can turn it on and off for experiments. It's starting out off. Based on proposal 163.
2009-12-21make the os x tiger compiler shut upRoger Dingledine
it's wrong, but that's our problem not its problem
2009-12-21a changelog and doc fixes for the strictnodes workRoger Dingledine
2009-12-21fix compileRoger Dingledine
2009-12-21Use nodes in ExitNodes even if they're not fast/stableRoger Dingledine
2009-12-21Use nodes in EntryNodes even if they're not fast/stableRoger Dingledine
2009-12-21instrument entry_is_live to tell why our guard isn't liveRoger Dingledine
2009-12-21Be more willing to use an unsuitable circuit for exit.Roger Dingledine
Specifically, there are two cases: a) are we willing to start a new circuit at a node not in your ExitNodes config option, and b) are we willing to make use of a circuit that's already established but has an unsuitable exit. Now we discard all your circuits when you set ExitNodes, so the only way you could end up with an exit circuit that ends at an unsuitable place is if we explicitly ran out of exit nodes, StrictNodes was 0, and we built this circuit to solve a stream that needs solving. Fixes bug in dc322931, which would ignore the just-built circuit because it has an unsuitable exit.
2009-12-21Abandon circs if the user changes Exclude*NodesRoger Dingledine
If ExcludeNodes or ExcludeExitNodes changes on a config reload, mark and discard all our origin circuits.
2009-12-21comments and cleanups, no actual changesRoger Dingledine
2009-12-21Make EntryNodes config option much more aggressive.Roger Dingledine
Before it would prepend your requested entrynodes to your list of guard nodes, but feel free to use others after that. Now it chooses only from your EntryNodes if any of those are available, and only falls back to others if a) they're all down and b) StrictNodes is not set. Also, now we refresh your entry guards from EntryNode at each consensus fetch (rather than just at startup and then they slowly rot as the network changes). The goal here is to make users less likely to set StrictNodes, since it's doing closer to what they expect it should be doing.
2009-12-21Switch to a StrictNodes config option.Roger Dingledine
This is step one of handling ExcludedNodes better. This first step is just to make EntryNodes and ExitNodes do what they did before.
2009-12-21bump to 0.2.1.21 so we can releasetor-0.2.1.21Roger Dingledine
2009-12-19fix some typosRoger Dingledine
2009-12-19start to document commonly used "param" argumentsRoger Dingledine
2009-12-18Merge branch 'ewma'Nick Mathewson
7apu2bq3rhoylwmucxizk54afw5jyda7pho4j5zdcqpwkufke7zdzwad.onion