summaryrefslogtreecommitdiff
AgeCommit message (Collapse)Author
2012-09-05fold in last changes filetor-0.2.3.21-rcRoger Dingledine
2012-09-05Merge branch 'maint-0.2.3' into release-0.2.3Roger Dingledine
2012-09-05Update the minimum bandwidth for a public relayRoger Dingledine
The current cutoff is 30KB, but in reality a useful cutoff is probably more like 50KB or 100KB.
2012-09-05Avoid segfault if EntryGuardPathBias precedes EntryGuardNick Mathewson
Fix for bug 6774; bugfix on 0.2.3.17-beta.
2012-09-04one more changes fileRoger Dingledine
2012-09-04Merge branch 'maint-0.2.3' into release-0.2.3Roger Dingledine
2012-09-04bump to 0.2.3.21-rcRoger Dingledine
2012-09-04fold in recent 0.2.3 changes filesRoger Dingledine
2012-09-04Merge branch 'maint-0.2.3' into release-0.2.3Roger Dingledine
2012-09-04Merge remote-tracking branch 'arma/bug6743' into maint-0.2.3Nick Mathewson
2012-09-03fix whitespace and trivial typoRoger Dingledine
2012-09-01Make begindir_cutoff the same as general_cutoffRoger Dingledine
Allow one-hop directory fetching circuits the full "circuit build timeout" period, rather than just half of it, before failing them and marking the relay down. This fix should help reduce cases where clients declare relays (or worse, bridges) unreachable because the TLS handshake takes a few seconds to complete. Fixes bug 6743 (one piece of bug 3443); bugfix on 0.2.2.2-alpha, where we changed the timeout from a static 30 seconds.
2012-09-01retroactively fix version typo in changelogRoger Dingledine
2012-08-31Merge branch 'bug6732' into maint-0.2.3Nick Mathewson
2012-08-31Document consensus and microdesc filesNick Mathewson
Bugfix for #6732.
2012-08-27Quiet "Set buildtimeout to low val" warnings: make them infoNick Mathewson
Fix for #6251
2012-08-27Merge branch 'disable_pathbias_warnings_v2' into maint-0.2.3Nick Mathewson
2012-08-27Downgrade path-bias warning messages to INFO for now.Nick Mathewson
We've had over two months to fix them, and didn't. Now we need 0.2.3.x stable. Yes, it would be cool to get this working in 0.2.3.x, but not at the expense of delaying every other feature that _does_ work in 0.2.3.x. We can do a real fix in 0.2.4.
2012-08-27Merge branch 'bug6710_023' into maint-0.2.3Nick Mathewson
2012-08-27Merge remote-tracking branch 'origin/maint-0.2.2' into maint-0.2.3Nick Mathewson
Conflicts: src/or/policies.c
2012-08-27Merge branch 'bug6690_022' into maint-0.2.2Nick Mathewson
2012-08-27go back in time and revise the 0.2.2.38 blurb tooRoger Dingledine
2012-08-27i should have removed these changes files during 0.2.3.20 releaseRoger Dingledine
2012-08-27Fix changes file for 6710: before 0.0.8pre1, you couldn't extend toNick Mathewson
a router that another router wasn't already connected to.
2012-08-27Do not assert when comparing a null address/port against a policyNick Mathewson
This can create a remote crash opportunity for/against directory authorities.
2012-08-27Disable extending to private/internal addresses by defaultNick Mathewson
This is important, since otherwise an attacker can use timing info to probe the internal network. Also, add an option (ExtendAllowPrivateAddresses) so that TestingTorNetwork won't break. Fix for bug 6710; bugfix on all released versions of Tor.
2012-08-24Merge remote-tracking branch 'public/bug6472' into maint-0.2.3Nick Mathewson
2012-08-22Remove #6480 fix from 0.2.2.38 changelog - it was not includedPeter Palfrader
(Forward-port change from release-0.2.2 into release-0.2.3)
2012-08-21Merge remote-tracking branch 'public/bug6404' into maint-0.2.3Nick Mathewson
2012-08-17whitespace fixNick Mathewson
2012-08-17When iterating over connections pending DNS, skip marked onesNick Mathewson
Failure to do this would lead to double-free cases and similar, especially when the exit's DNS was broken. See bug 6472 for full details; this is a fix for 6472. Anonymous patch from "cypherpunks" on trac.
2012-08-17Consider IPv6 OR ports when deciding whether a routerinfo change is cosmetic.Linus Nordberg
Closes #6423.
2012-08-17Merge branch 'bug6379' into maint-0.2.3Nick Mathewson
2012-08-17Fix more warnings from openbsd_mallocNick Mathewson
Apparently, (void)writev is not enough to suppress the "you are ignoring the return value!" warnings on Linux. Instead, remove the whole warning/error logic when compiling openbsd_malloc for Tor: we can't use it.
2012-08-17Merge remote-tracking branch 'public/bug6244_part_c' into maint-0.2.3Nick Mathewson
2012-08-17Merge remote-tracking branch 'public/bug6507' into maint-0.2.3Nick Mathewson
2012-08-17Whitespace and build fixes on 6475 patchNick Mathewson
2012-08-17Merge remote-tracking branch 'mikeperry/bug6475' into maint-0.2.3Nick Mathewson
2012-08-17Merge remote-tracking branch 'public/bug6514' into maint-0.2.3Nick Mathewson
2012-08-16Address Nick's comments from code review.Mike Perry
Also promote log messages to notice and rate-limit them.
2012-08-15Bug 6475: Explicitly track our path bias state.Mike Perry
This is done to avoid spurious warns. Additional log lines are also added to try to track down the codepaths where we are somehow overcounting success counts.
2012-08-15Fix warnings and 64-bit problems in openbsd-malloc codeNick Mathewson
The warning fixes are: - Only define issetugid if it's missing. - Explicitly ignore the return value of writev. - Explicitly cast the retval of readlink() to int. The 64-bit problems are related to just storing a size_t in an int. Not cool! Use a size_t instead. Fix for bug 6379. Bugfix on 0.2.0.20-rc, which introduced openbsd-malloc.
2012-08-15Fix wildcarded address mappings from the control portNick Mathewson
Apparently, we weren't actually detecting wildcardedness when parsing them: whoops! bug 6244. Bugfix on 0.2.3.9-alpha
2012-08-15Raise the part of torrc mapaddress handling that knows wildcardsNick Mathewson
This patch extracts the inner part of config_register_addressmaps -- the part that knows about detecting wildcard addresses addresses -- and makes it into a new function. The new function is deliberately not moved or reindented, so that the diff is smaller. I need this to fix bug 6244.
2012-08-14Update description of what we did to upper limit on md sizeNick Mathewson
Spotted by asn
2012-08-14Fix memory leak in dirvote_create_microdescriptorNick Mathewson
Found by George, who gets a cookie.
2012-08-13forward-port the 0.2.2.38 changelogRoger Dingledine
2012-08-09Reject attempts to say FooPort and FooPort 0 in the same cfg domainNick Mathewson
2012-08-09Fix spaces from last patchNick Mathewson
2012-08-09Don't infer we have a FooPort from the presence of a FooPort lineNick Mathewson
Thanks to the changes we started making with SocksPort and friends in 0.2.3.3-alpha, any of our code that did "if (options->Sockport)" became wrong, since "SocksPort 0" would make that test true whereas using the default SocksPort value would make it false. (We didn't actually do "if (options->SockPort)" but we did have tests for TransPort. When we moved DirPort, ORPort, and ControlPort over to the same system in 0.2.3.9-alpha, the problem got worse, since our code is littered with checks for DirPort and ORPort as booleans. This code renames the current linelist-based FooPort options to FooPort_lines, and adds new FooPort_set options which get set at parse-and-validate time on the or_options_t. FooPort_set is true iff we will actually try to open a listener of the given type. (I renamed the FooPort options rather than leave them alone so that every previous user of a FooPort would need to get inspected, and so that any new code that forgetfully uses FooPort will need fail to compile.) Fix for bug 6507.