[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
Re: [tor-bugs] #2681 [Tor]: brainstorm ways to let Tor clients use yesterday's consensus more safely
#2681: brainstorm ways to let Tor clients use yesterday's consensus more safely
--------------------------------------------------------------------------------+
Reporter: arma | Owner:
Type: enhancement | Status: new
Priority: normal | Milestone: Tor: 0.2.4.x-final
Component: Tor | Version:
Keywords: dirauth-dos-resistance proposal-needed MikePerry201210d tor-client | Parent: #2664
Points: | Actualpoints:
--------------------------------------------------------------------------------+
Comment(by nickm):
Replying to [comment:9 mikeperry]:
> Hrmm. I tried to ponder these imponderables, but I failed to both do
that and get my other proposals done on time. Can we just set the limit at
3 days and call this 'small-feature' (or make a different ticket for that
and call that one 'small-feature')?
I'm pretty leery of calling stuff "small" when our reason for doing so is
that if we called it "big" we couldn't merge it on the timeframe we want.
That's as many as four tens^W^W^W^W^W motivated reasoning, and that's
terrible.
That said, this _does_ feel simple to me. If we get the proposal done
soon and the code merged before the big feature deadline, we can try it
out. (I don't want to push it to the end of the feature merge schedule,
since this kind of thing is prone to having unexpected consequences that
could mean more fixing would be needed .)
--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/2681#comment:10>
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