mirror of
https://gitlab.torproject.org/tpo/core/tor.git
synced 2024-11-10 05:03:43 +01:00
clean up the changelog for a release today
svn:r12487
This commit is contained in:
parent
c23a22785d
commit
b7024f0f30
17
ChangeLog
17
ChangeLog
@ -1,4 +1,4 @@
|
||||
Changes in version 0.2.0.11-alpha - 2007-11-??
|
||||
Changes in version 0.2.0.11-alpha - 2007-11-12
|
||||
o Security fixes:
|
||||
- Exit policies now reject connections that are addressed to a
|
||||
relay's public (external) IP address too, unless
|
||||
@ -8,14 +8,15 @@ Changes in version 0.2.0.11-alpha - 2007-11-??
|
||||
|
||||
o Major bugfixes:
|
||||
- Fix a memory leak on exit relays; we were leaking a cached_resolve_t
|
||||
on every successful resolve. Reported by Mike Perry.
|
||||
on every successful resolve. Reported by Mike Perry; bugfix
|
||||
on 0.1.2.x.
|
||||
- On authorities, never downgrade to old router descriptors simply
|
||||
because they're listed in the consensus. This created a catch-22 where
|
||||
we wouldn't list a new descriptor because there was an old one in the
|
||||
consensus, and we couldn't get the new one in the consensus because we
|
||||
wouldn't list it. Possible fix for bug 548. (Also, this might cause
|
||||
bug 543 to appear on authorities. If so, we'll need a band-aid for
|
||||
that.)
|
||||
because they're listed in the consensus. This created a catch-22
|
||||
where we wouldn't list a new descriptor because there was an
|
||||
old one in the consensus, and we couldn't get the new one in the
|
||||
consensus because we wouldn't list it. Possible fix for bug 548.
|
||||
Also, this might cause bug 543 to appear on authorities; if so,
|
||||
we'll need a band-aid for that. Bugfix on 0.2.0.9-alpha.
|
||||
|
||||
o Packaging fixes on 0.2.0.10-alpha:
|
||||
- We were including instructions about what to do with the
|
||||
|
Loading…
Reference in New Issue
Block a user