aboutsummaryrefslogtreecommitdiff
path: root/ChangeLog
Commit message (Collapse)AuthorAge
* give us a blurb; add stanza to the releasenotesRoger Dingledine2010-03-16
|
* bump to 0.2.1.25Roger Dingledine2010-03-15
| | | | it's perfect, let's ship it
* clean up the 0.2.1.25 changelogRoger Dingledine2010-03-06
|
* Apply Roger's bug 1269 fix.Nick Mathewson2010-03-04
| | | | | | | | | | | | | From http://archives.seul.org/tor/relays/Mar-2010/msg00006.html : As I understand it, the bug should show up on relays that don't set Address to an IP address (so they need to resolve their Address line or their hostname to guess their IP address), and their hostname or Address line fails to resolve -- at that point they'll pick a random 4 bytes out of memory and call that their address. At the same time, relays that *do* successfully resolve their address will ignore the result, and only come up with a useful address if their interface address happens to be a public IP address.
* Properly handle non-terminated stringsSebastian Hahn2010-02-27
| | | | | | | | Treat strings returned from signed_descriptor_get_body_impl() as not NUL-terminated. Since the length of the strings is available, this is not a big problem. Discovered by rieo.
* Proper NULL checking in circuit_list_path_impl()Sebastian Hahn2010-02-26
| | | | | | | Another dereference-then-NULL-check sequence. No reports of this bug triggered in the wild. Fixes bugreport 1256. Thanks to ekir for discovering and reporting this bug.
* Proper NULL checking for hsdesc publicationSebastian Hahn2010-02-26
| | | | | | | | | Fix a dereference-then-NULL-check sequence. This bug wasn't triggered in the wild, but we should fix it anyways in case it ever happens. Also make sure users get a note about this being a bug when they see it in their log. Thanks to ekir for discovering and reporting this bug.
* Zero a cipher completely before freeing itSebastian Hahn2010-02-26
| | | | | | We used to only zero the first ptrsize bytes of the cipher. Since cipher is large enough, we didn't zero too many bytes. Discovered and fixed by ekir. Fixes bug 1254.
* bump to 0.2.1.24Roger Dingledine2010-02-21
|
* Add changelog for latest openssl fixNick Mathewson2010-02-18
|
* give it a blurb, update the dateRoger Dingledine2010-02-13
|
* new dannenberg address; make moria2's demise official.Roger Dingledine2010-02-12
|
* prepare for 0.2.1.23Roger Dingledine2010-02-12
|
* Don't use gethostbyname() in resolve_my_address()Sebastian Hahn2010-02-08
| | | | | | | Tor has tor_lookup_hostname(), which prefers ipv4 addresses automatically. Bug 1244 occured because gethostbyname() returned an ipv6 address, which Tor cannot handle currently. Fixes bug 1244; bugfix on 0.0.2pre25. Reported by Mike Mestnik.
* lookup_last_hid_serv_request() could overflow and leak memorySebastian Hahn2010-02-07
| | | | | | The problem was that we didn't allocate enough memory on 32-bit platforms with 64-bit time_t. The memory leak occured every time we fetched a hidden service descriptor we've fetched before.
* Decide whether to use SSL flags based on runtime OpenSSL version.Nick Mathewson2010-01-29
| | | | | | | | | | | We need to do this because Apple doesn't update its dev-tools headers when it updates its libraries in a security patch. On the bright side, this might get us out of shipping a statically linked OpenSSL on OSX. May fix bug 1225. [backported]
* spread guard rotation out throughout the monthRoger Dingledine2010-01-19
|
* weight guard choice by bandwidth; discard old guardsRoger Dingledine2010-01-19
|
* bump to 0.2.1.22, and give it a changelogRoger Dingledine2010-01-19
|
* rotate keys for moria1 and gabelmooRoger Dingledine2010-01-19
|
* stop bridge authorities from leaking their bridge listRoger Dingledine2010-01-17
|
* bump to 0.2.1.21 so we can releaseRoger Dingledine2009-12-21
|
* Fix bug 1173: remove an assert(unsigned >= 0).Nick Mathewson2009-12-15
|
* fix race condition that can cause crashes at client or exit relayRoger Dingledine2009-11-23
| | | | | | Avoid crashing if the client is trying to upload many bytes and the circuit gets torn down at the same time, or if the flip side happens on the exit relay. Bugfix on 0.2.0.1-alpha; fixes bug 1150.
* add the 0.2.1.20 changelog blurb, plus update the releasenotesRoger Dingledine2009-11-17
|
* Make Tor work with OpenSSL 0.9.8lNick Mathewson2009-11-05
| | | | | | | | | | | | | | | | | | | To fix a major security problem related to incorrect use of SSL/TLS renegotiation, OpenSSL has turned off renegotiation by default. We are not affected by this security problem, however, since we do renegotiation right. (Specifically, we never treat a renegotiated credential as authenticating previous communication.) Nevertheless, OpenSSL's new behavior requires us to explicitly turn renegotiation back on in order to get our protocol working again. Amusingly, this is not so simple as "set the flag when you create the SSL object" , since calling connect or accept seems to clear the flags. For belt-and-suspenders purposes, we clear the flag once the Tor handshake is done. There's no way to exploit a second handshake either, but we might as well not allow it.
* Add changelog to describe coverity fixes for 0.2.1.21Nick Mathewson2009-10-26
|
* Only send the if_modified_since header for a v3 consensus.Nick Mathewson2009-10-26
| | | | | Spotted by xmux; bugfix on 0.2.0.10-alpha. (Bug introduced by 20b10859)
* bump to 0.2.1.20Roger Dingledine2009-10-15
|
* Move moria1 and Tonga to alternate IP addresses.Roger Dingledine2009-10-15
|
* read the "circwindow" parameter from the consensusRoger Dingledine2009-10-14
| | | | | backport of c43859c5c12361fad505 backport of 0d13e0ed145f4c1b5bd1
* Revert "Teach connection_ap_can_use_exit about Exclude*Nodes"Roger Dingledine2009-09-20
| | | | | | | This reverts commit dc3229313b6d2aaff437c6fc7fa55ead4409e93d. We're going to do this more thoroughly in 0.2.2.x, and not in maint-0.2.1.
* Work around a memory leak in openssl 0.9.8g (and maybe others)Nick Mathewson2009-09-17
|
* Merge commit 'karsten/fix-1073' into maint-0.2.1Nick Mathewson2009-09-16
|\
| * Avoid segfault when accessing hidden service.Karsten Loesing2009-08-29
| |
* | Teach connection_ap_can_use_exit about Exclude*NodesSebastian Hahn2009-09-16
| | | | | | | | | | | | To further attempt to fix bug 1090, make sure connection_ap_can_use_exit always returns 0 when the chosen exit router is excluded. This should fix bug1090.
* | Merge commit 'sebastian/memleak' into maint-0.2.1Nick Mathewson2009-09-15
|\ \
| * | Fix a memory leak when parsing a nsSebastian Hahn2009-09-14
| | | | | | | | | | | | | | | | | | | | | | | | Adding the same vote to a networkstatus consensus leads to a memory leak on the client side. Fix that by only using the first vote from any given voter, and ignoring the others. Problem found by Rotor, who also helped writing the patch. Thanks!
* | | make some bug 1090 warnings go awaySebastian Hahn2009-09-16
|/ / | | | | | | | | | | | | | | | | When we excluded some Exits, we were sometimes warning the user that we were going to use the node regardless. Many of those warnings were in fact bogus, because the relay in question was not used to connect to the outside world. Based on patch by Rotor, thanks!
* | Fix obscure 64-bit big-endian hidserv bugRoger Dingledine2009-09-02
| | | | | | | | | | | | | | Fix an obscure bug where hidden services on 64-bit big-endian systems might mis-read the timestamp in v3 introduce cells, and refuse to connect back to the client. Discovered by "rotor". Bugfix on 0.2.1.6-alpha.
* | turns out the packaging changes aren't in 0.2.1.20Roger Dingledine2009-09-01
| |
* | update changelog with bundle detailsAndrew Lewman2009-09-01
| |
* | Add getinfo accepted-server-descriptor. Clean spec.Roger Dingledine2009-08-31
| | | | | | | | | | | | | | | | Add a "getinfo status/accepted-server-descriptor" controller command, which is the recommended way for controllers to learn whether our server descriptor has been successfully received by at least on directory authority. Un-recommend good-server-descriptor getinfo and status events until we have a better design for them.
* | Only send reachability status events on overall success/failureRoger Dingledine2009-08-31
|/ | | | | | | | | We were telling the controller about CHECKING_REACHABILITY and REACHABILITY_FAILED status events whenever we launch a testing circuit or notice that one has failed. Instead, only tell the controller when we want to inform the user of overall success or overall failure. Bugfix on 0.1.2.6-alpha. Fixes bug 1075. Reported by SwissTorExit.
* Only send netinfo clock_skew to controller if an authority told us soRoger Dingledine2009-08-28
| | | | | | | | We were triggering a CLOCK_SKEW controller status event whenever we connect via the v2 connection protocol to any relay that has a wrong clock. Instead, we should only inform the controller when it's a trusted authority that claims our clock is wrong. Bugfix on 0.2.0.20-rc; starts to fix bug 1074. Reported by SwissTorExit.
* extremely infinite? who talks like that?Roger Dingledine2009-08-27
|
* nobody forward-ported the 0.2.0.35 changelogRoger Dingledine2009-08-26
|
* Fix a rare infinite-recursion bug when shutting down.Nick Mathewson2009-08-20
| | | | | | | | | | | | | | | | | | | Once we had called log_free_all(), anything that tried to log a message (like a failed tor_assert()) would fail like this: 1. The logging call eventually invokes the _log() function. 2. _log() calls tor_mutex_lock(log_mutex). 3. tor_mutex_lock(m) calls tor_assert(m). 4. Since we freed the log_mutex, tor_assert() fails, and tries to log its failure. 5. GOTO 1. Now we allocate the mutex statically, and never destroy it on shutdown. Bugfix on 0.2.0.16-alpha, which introduced the log mutex. This bug was found by Matt Edman.
* Fix possible segmentation fault on directory authorities.Karsten Loesing2009-08-11
| | | | | | The more verbose logs that were added in ee58153 also include a string that might not have been initialized. This can lead to segfaults, e.g., when setting up private Tor networks. Initialize this string with NULL.
* Send sendmes when we're down 100 cells, not 101.Roger Dingledine2009-08-10
| | | | | | | | | Send circuit or stream sendme cells when our window has decreased by 100 cells, not when it has decreased by 101 cells. Bug uncovered by Karsten when testing the "reduce circuit window" performance patch. Bugfix on the 54th commit on Tor -- from July 2002, before the release of Tor 0.0.0. This is the new winner of the oldest-bug prize.
generated by cgit v1.2.3 (git 2.25.4) at 2024-10-06 03:39:21 +0000