Age | Commit message (Collapse) | Author | |
---|---|---|---|
2012-01-05 | Merge branch 'maint-0.2.1' into release-0.2.1release-0.2.1 | Roger Dingledine | |
2012-01-05 | add a changes file for ticket 4825 | Roger Dingledine | |
2012-01-05 | Merge branch 'maint-0.2.1' into release-0.2.1 | Roger Dingledine | |
2012-01-05 | Update to the January 2012 GeoIP database. | Karsten Loesing | |
2011-12-28 | Bug 4786 fix: don't convert EARLY to RELAY on v1 connections | Nick Mathewson | |
We used to do this as a workaround for older Tors, but now it's never the correct thing to do (especially since anything that didn't understand RELAY_EARLY is now deprecated hard). | |||
2011-12-15 | Tweak changelog a littletor-0.2.1.32 | Nick Mathewson | |
2011-12-15 | Copy 0.2.1.32 changelog entry into releasenotes | Nick Mathewson | |
2011-12-15 | Bump the version to 0.2.1.32 | Nick Mathewson | |
2011-12-15 | Changelog and blurb for 0.2.1.32 | Nick Mathewson | |
2011-12-15 | Merge branch 'maint-0.2.1' into release-0.2.1 | Nick Mathewson | |
2011-12-15 | Add a fix for the buf_pullup bug that Vektor reported | Nick Mathewson | |
2011-12-14 | Update the release-0.2.1 changelog while I am at it | Nick Mathewson | |
2011-12-14 | Merge branch 'maint-0.2.1' into release-0.2.1 | Nick Mathewson | |
2011-12-08 | Update to the December 2011 GeoIP database. | Karsten Loesing | |
2011-11-14 | Merge remote-tracking branch 'karsten/geoip-november2011' into maint-0.2.1 | Nick Mathewson | |
2011-11-07 | Update to the November 2011 GeoIP database. | Karsten Loesing | |
2011-11-06 | Add a changes file for 4410 | Sebastian Hahn | |
2011-11-06 | Fix remotely triggerable assert during ip decryption | Dan Rosenberg | |
Fixes bug 4410. | |||
2011-10-27 | minor cleanup on already published changelog text | Roger Dingledine | |
2011-10-27 | Merge branch 'maint-0.2.1' into release-0.2.1 | Roger Dingledine | |
2011-10-27 | bump maint to 0.2.1.31 | Roger Dingledine | |
2011-10-26 | slight tweak to texttor-0.2.1.31 | Roger Dingledine | |
2011-10-26 | opt for a short and sweet release blurb for 0.2.1.31. | Roger Dingledine | |
anybody who's reading it to decide whether to use it should not be using it. | |||
2011-10-26 | bump to 0.2.1.31 | Roger Dingledine | |
2011-10-26 | fold in changes files | Roger Dingledine | |
2011-10-26 | Merge branch 'maint-0.2.1' into release-0.2.1 | Roger Dingledine | |
2011-10-26 | Reject create cells on outgoing OR connections from bridges | Robert Ransom | |
2011-10-26 | Mark which OR connections are outgoing | Robert Ransom | |
2011-10-26 | merge in more changes entries | Roger Dingledine | |
2011-10-26 | Don't use any OR connection which sent us a CREATE_FAST cell for an EXTEND | Robert Ransom | |
Fix suggested by Nick Mathewson. | |||
2011-10-26 | Don't send a certificate chain on outgoing TLS connections from non-relays | Nick Mathewson | |
2011-10-26 | Merge branch 'maint-0.2.1' into release-0.2.1 | Roger Dingledine | |
2011-10-26 | Remove the -F option from tor-resolve. | Nick Mathewson | |
It used to mean "Force": it would tell tor-resolve to ask tor to resolve an address even if it ended with .onion. But when AutomapHostsOnResolve was added, automatically refusing to resolve .onion hosts stopped making sense. So in 0.2.1.16-rc (commit 298dc95dfd8), we made tor-resolve happy to resolve anything. The -F option stayed in, though, even though it didn't do anything. Oddly, it never got documented. Found while fixing GCC 4.6 "set, unused variable" warnings. | |||
2011-10-26 | manually backport a5232e0c4c | Roger Dingledine | |
2011-10-26 | Merge branch 'maint-0.2.1' into release-0.2.1 | Roger Dingledine | |
2011-10-26 | stop asserting at boot | Roger Dingledine | |
The patch for 3228 made us try to run init_keys() before we had loaded our state file, resulting in an assert inside init_keys. We had moved it too early in the function. Now it's later in the function, but still above the accounting calls. | |||
2011-10-26 | Reinit keys at the start of options_act(). | Nick Mathewson | |
Previously we did this nearer to the end (in the old_options && transition_affects_workers() block). But other stuff cares about keys being consistent with options... particularly anything which tries to access a key, which can die in assert_identity_keys_ok(). Fixes bug 3228; bugfix on 0.2.2.18-alpha. Conflicts: src/or/config.c | |||
2011-10-26 | Don't crash a bridge authority on SIGHUP if it's not in the consensus | Robert Ransom | |
Fixes bug 2572. | |||
2011-10-26 | Fix assert for relay/bridge state change | Sebastian Hahn | |
When we added support for separate client tls certs on bridges in a2bb0bfdd5 we forgot to correctly initialize this when changing from relay to bridge or vice versa while Tor is running. Fix that by always initializing keys when the state changes. Fixes bug 2433. Conflicts: src/or/config.c | |||
2011-10-26 | Don't crash when accountingmax is set in non-server Tors | Nick Mathewson | |
We use a hash of the identity key to seed a prng to tell when an accounting period should end. But thanks to the bug998 changes, clients no longer have server-identity keys to use as a long-term seed in accounting calculations. In any case, their identity keys (as used in TLS) were never never fixed. So we can just set the wakeup time from a random seed instead there. Still open is whether everybody should be random. This patch fixes bug 2235, which was introduced in 0.2.2.18-alpha. Diagnosed with help from boboper on irc. | |||
2011-10-26 | Properly refcount client_identity_key | Sebastian Hahn | |
In a2bb0bf we started using a separate client identity key. When we are in "public server mode" (that means not a bridge) we will use the same key. Reusing the key without doing the proper refcounting leads to a segfault on cleanup during shutdown. Fix that. Also introduce an assert that triggers if our refcount falls below 0. That should never happen. | |||
2011-10-26 | Add some asserts to get_{tlsclient|server}_identity_key | Nick Mathewson | |
We now require that: - Only actual servers should ever call get_server_identity_key - If you're being a client or bridge, the client and server keys should differ. - If you're being a public relay, the client and server keys should be the same. | |||
2011-10-26 | Rename get_client_identity_key to get_tlsclient_identity_key | Nick Mathewson | |
2011-10-26 | Maintain separate server and client identity keys when appropriate. | Robert Ransom | |
Fixes a bug described in ticket #988. Conflicts: src/or/main.c src/or/router.c | |||
2011-10-26 | Make crypto_free_pk_env tolerate NULL arg in 0.2.1. Error-proofing against ↵ | Nick Mathewson | |
bug 988 backport | |||
2011-10-26 | Maintain separate server and client TLS contexts. | Robert Ransom | |
Fixes bug #988. Conflicts: src/or/main.c src/or/router.c | |||
2011-10-26 | Refactor tor_tls_context_new: | Robert Ransom | |
* Make tor_tls_context_new internal to tortls.c, and return the new tor_tls_context_t from it. * Add a public tor_tls_context_init wrapper function to replace it. Conflicts: src/or/main.c src/or/router.c | |||
2011-10-26 | Add public_server_mode function. | Robert Ransom | |
2011-10-26 | Merge branch 'maint-0.2.1' into release-0.2.1 | Roger Dingledine | |
2011-10-26 | Fix zlib macro brokenness on osx with zlib 1.2.4 and higher. | Nick Mathewson | |
From the code: zlib 1.2.4 and 1.2.5 do some "clever" things with macros. Instead of saying "(defined(FOO) ? FOO : 0)" they like to say "FOO-0", on the theory that nobody will care if the compile outputs a no-such-identifier warning. Sorry, but we like -Werror over here, so I guess we need to define these. I hope that zlib 1.2.6 doesn't break these too. Possible fix for bug 1526. |