Age | Commit message (Collapse) | Author | |
---|---|---|---|
2012-09-05 | fold in last changes filetor-0.2.3.21-rc | Roger Dingledine | |
2012-09-05 | Merge branch 'maint-0.2.3' into release-0.2.3 | Roger Dingledine | |
2012-09-05 | Update the minimum bandwidth for a public relay | Roger Dingledine | |
The current cutoff is 30KB, but in reality a useful cutoff is probably more like 50KB or 100KB. | |||
2012-09-05 | Avoid segfault if EntryGuardPathBias precedes EntryGuard | Nick Mathewson | |
Fix for bug 6774; bugfix on 0.2.3.17-beta. | |||
2012-09-04 | one more changes file | Roger Dingledine | |
2012-09-04 | Merge branch 'maint-0.2.3' into release-0.2.3 | Roger Dingledine | |
2012-09-04 | bump to 0.2.3.21-rc | Roger Dingledine | |
2012-09-04 | fold in recent 0.2.3 changes files | Roger Dingledine | |
2012-09-04 | Merge branch 'maint-0.2.3' into release-0.2.3 | Roger Dingledine | |
2012-09-04 | Merge remote-tracking branch 'arma/bug6743' into maint-0.2.3 | Nick Mathewson | |
2012-09-03 | fix whitespace and trivial typo | Roger Dingledine | |
2012-09-01 | Make begindir_cutoff the same as general_cutoff | Roger 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-01 | retroactively fix version typo in changelog | Roger Dingledine | |
2012-08-31 | Merge branch 'bug6732' into maint-0.2.3 | Nick Mathewson | |
2012-08-31 | Document consensus and microdesc files | Nick Mathewson | |
Bugfix for #6732. | |||
2012-08-27 | Quiet "Set buildtimeout to low val" warnings: make them info | Nick Mathewson | |
Fix for #6251 | |||
2012-08-27 | Merge branch 'disable_pathbias_warnings_v2' into maint-0.2.3 | Nick Mathewson | |
2012-08-27 | Downgrade 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-27 | Merge branch 'bug6710_023' into maint-0.2.3 | Nick Mathewson | |
2012-08-27 | Merge remote-tracking branch 'origin/maint-0.2.2' into maint-0.2.3 | Nick Mathewson | |
Conflicts: src/or/policies.c | |||
2012-08-27 | Merge branch 'bug6690_022' into maint-0.2.2 | Nick Mathewson | |
2012-08-27 | go back in time and revise the 0.2.2.38 blurb too | Roger Dingledine | |
2012-08-27 | i should have removed these changes files during 0.2.3.20 release | Roger Dingledine | |
2012-08-27 | Fix changes file for 6710: before 0.0.8pre1, you couldn't extend to | Nick Mathewson | |
a router that another router wasn't already connected to. | |||
2012-08-27 | Do not assert when comparing a null address/port against a policy | Nick Mathewson | |
This can create a remote crash opportunity for/against directory authorities. | |||
2012-08-27 | Disable extending to private/internal addresses by default | Nick 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-24 | Merge remote-tracking branch 'public/bug6472' into maint-0.2.3 | Nick Mathewson | |
2012-08-22 | Remove #6480 fix from 0.2.2.38 changelog - it was not included | Peter Palfrader | |
(Forward-port change from release-0.2.2 into release-0.2.3) | |||
2012-08-21 | Merge remote-tracking branch 'public/bug6404' into maint-0.2.3 | Nick Mathewson | |
2012-08-17 | whitespace fix | Nick Mathewson | |
2012-08-17 | When iterating over connections pending DNS, skip marked ones | Nick 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-17 | Consider IPv6 OR ports when deciding whether a routerinfo change is cosmetic. | Linus Nordberg | |
Closes #6423. | |||
2012-08-17 | Merge branch 'bug6379' into maint-0.2.3 | Nick Mathewson | |
2012-08-17 | Fix more warnings from openbsd_malloc | Nick 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-17 | Merge remote-tracking branch 'public/bug6244_part_c' into maint-0.2.3 | Nick Mathewson | |
2012-08-17 | Merge remote-tracking branch 'public/bug6507' into maint-0.2.3 | Nick Mathewson | |
2012-08-17 | Whitespace and build fixes on 6475 patch | Nick Mathewson | |
2012-08-17 | Merge remote-tracking branch 'mikeperry/bug6475' into maint-0.2.3 | Nick Mathewson | |
2012-08-17 | Merge remote-tracking branch 'public/bug6514' into maint-0.2.3 | Nick Mathewson | |
2012-08-16 | Address Nick's comments from code review. | Mike Perry | |
Also promote log messages to notice and rate-limit them. | |||
2012-08-15 | Bug 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-15 | Fix warnings and 64-bit problems in openbsd-malloc code | Nick 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-15 | Fix wildcarded address mappings from the control port | Nick Mathewson | |
Apparently, we weren't actually detecting wildcardedness when parsing them: whoops! bug 6244. Bugfix on 0.2.3.9-alpha | |||
2012-08-15 | Raise the part of torrc mapaddress handling that knows wildcards | Nick 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-14 | Update description of what we did to upper limit on md size | Nick Mathewson | |
Spotted by asn | |||
2012-08-14 | Fix memory leak in dirvote_create_microdescriptor | Nick Mathewson | |
Found by George, who gets a cookie. | |||
2012-08-13 | forward-port the 0.2.2.38 changelog | Roger Dingledine | |
2012-08-09 | Reject attempts to say FooPort and FooPort 0 in the same cfg domain | Nick Mathewson | |
2012-08-09 | Fix spaces from last patch | Nick Mathewson | |
2012-08-09 | Don't infer we have a FooPort from the presence of a FooPort line | Nick 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. |