[tor-bugs] #2800 [Tor Client]: Resolve or postpone all XXX022/XXX021 items
Tor Bug Tracker & Wiki
torproject-admin at torproject.org
Mon Mar 28 17:29:32 UTC 2011
#2800: Resolve or postpone all XXX022/XXX021 items
------------------------+---------------------------------------------------
Reporter: nickm | Owner:
Type: defect | Status: needs_review
Priority: normal | Milestone: Tor: 0.2.2.x-final
Component: Tor Client | Version:
Keywords: | Parent:
Points: | Actualpoints:
------------------------+---------------------------------------------------
Comment(by Sebastian):
Added a branch xxx_fixups to my repo
Fixed the comment a little for 41380fa3. Looks good otherwise.
c4bd06735: I'd probably just remove the lines. But keeping them seems fine
too
05887f10ff: for the reasons.c change, we might want to do this still?
0.2.1.30 is out, and nobody should be running a versoin earlier than
0.2.1.27 anymore due to security concerns. The change in rephist.c seems
important, but I think we don't need to block 0.2.2.x for that:
Authorities are easy to upgrade and they all run alpha or more recent
currently, so they could also run the 0.2.3 release containing the fix
dddd333a: I have a fixup commit in my branch
f3b89c114 and 43273427: about the stream_id exhaustion, maybe this XXX can
also be turned into an attack where you manage to open a few 10k streams
and see that a particular circuit dies/doesn't get new streams. Not sure
how realistic that is, tho.
--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/2800#comment:2>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online
More information about the tor-bugs
mailing list