[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
Re: [tor-bugs] #15515 [Tor]: Don't allow multiple INTRODUCE1s on the same circuit
#15515: Don't allow multiple INTRODUCE1s on the same circuit
-------------------------+-------------------------------------------------
Reporter: asn | Owner:
Type: defect | Status: needs_review
Priority: normal | Milestone: Tor: 0.2.6.x-final
Component: Tor | Version:
Resolution: | Keywords: 026-backport 025-backport
Actual Points: | 024-backport
Points: | Parent ID: #15463
-------------------------+-------------------------------------------------
Comment (by yawning):
Replying to [comment:8 arma]:
> I asked weasel about the efficacy of an 0.2.4 backport here: "jessie
will release in april, and that might move a lot of people to 0.2.5.x
within a relatively short period of time. so maybe wait for that?" "also,
which versions of 0.2.4 are they running? 0.2.4.26? if not, they aren't
using squeeze or wheezy anyway."
>
> I'm just trying to sort out if, for relays not running the latest
0.2.4.x, a new 0.2.4.x is going to help them or us any.
Based off the current consensus:
{{{
1 v Tor 0.2.4.18-rc
4 v Tor 0.2.4.19
190 v Tor 0.2.4.20
69 v Tor 0.2.4.21
132 v Tor 0.2.4.22
902 v Tor 0.2.4.23
1 v Tor 0.2.4.23-dev
750 v Tor 0.2.4.24
26 v Tor 0.2.4.25
688 v Tor 0.2.4.26
}}}
~24.9% are on latest 0.2.4.x. I'm unsure of how many of the remainder
will upgrade if we make a lot of noise about upgrading. Given some of the
other changes pending that I also believe should go into maint-0.2.4, I'm
still in favor of a backport here.
--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/15515#comment:11>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online
_______________________________________________
tor-bugs mailing list
tor-bugs@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs