summaryrefslogtreecommitdiff
path: root/ChangeLog
diff options
context:
space:
mode:
authorNick Mathewson <nickm@torproject.org>2006-10-20 17:54:48 +0000
committerNick Mathewson <nickm@torproject.org>2006-10-20 17:54:48 +0000
commitb27cb38dee3aa024e191a974bcf2801d4e87c0a5 (patch)
treea08aa6d0cd08cea79e981975cb9b75ed803cce87 /ChangeLog
parent8e94097edb05b204cff7772588a3376507b3fd0b (diff)
downloadtor-b27cb38dee3aa024e191a974bcf2801d4e87c0a5.tar.gz
tor-b27cb38dee3aa024e191a974bcf2801d4e87c0a5.zip
r9307@Kushana: nickm | 2006-10-20 13:53:54 -0400
Have connection_about_to_close use an end_reason field in edge_connection_t to tell what reason to tell the controller for closing the stream. Set end_reason in connection_edge_end, connection_mark_unattached_ap, and everwhere we set edge_has_sent_end. Add a changelog entry. svn:r8779
Diffstat (limited to 'ChangeLog')
-rw-r--r--ChangeLog2
1 files changed, 2 insertions, 0 deletions
diff --git a/ChangeLog b/ChangeLog
index c7a853a054..fd92bb6f31 100644
--- a/ChangeLog
+++ b/ChangeLog
@@ -22,6 +22,8 @@ Changes in version 0.1.2.3-alpha - 2006-10-??
why a remote OR told us to close a circuit.
- There's now a GETINFO ns/... field so that controllers can ask Tor
about the current state of a router.
+ - Stream events also have REASON and REMOTE_REASON fields, working much
+ like those for circuit events.
o Security bugfixes:
- When the user sends a NEWNYM signal, clear the client-side DNS