[tor-bugs] #16235 [Tor]: Proposal 228 needs spec documentation

[Tor Bug Tracker & Wiki]

#16235: Proposal 228 needs spec documentation
------------------------+-----------------
     Reporter:  atagar  |      Owner:
         Type:  defect  |     Status:  new
     Priority:  normal  |  Milestone:
    Component:  Tor     |    Version:
   Resolution:          |   Keywords:
Actual Points:          |  Parent ID:
       Points:          |
------------------------+-----------------

Comment (by atagar):

 Should the priority of this be bumped? Proposal 228 was incomplete, and if
 this wasn't an important security improvement I'd argue we should be
 rolling it back until that's fixed.

 Karsten is moving forward with descriptor sanitation. The following was my
 reply to his request for comment...

 {{{
 Hi Karsten. My thought is that the existing ED stuff doesn't have a
 specification, I don't know what it does, and think that should be
 fixed before we worry about how it's sanitized. The spec was
 incomplete and personally think we should either prioritize that or
 roll back the feature. But maybe that's impractical. I already voiced
 this earlier so feel free to proceed as you'd like. You have my
 complete confidence. :P
 }}}

 Documenting (or rolling back) this feature should be easy so I'm surprised
 this is still an issue.

 Apologies if this ruffles feathers, but personally I think the proposal
 process for this was mishandled. We shouldn't be merging major features
 that lack a spec, then leave them undocumented for a full month afterward.
 :(

--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/16235#comment:1>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online