[tor-bugs] #2800 [Tor Client]: Resolve or postpone all XXX022/XXX021 items

[Tor Bug Tracker & Wiki]

#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 nickm):

 Replying to [comment:7 arma]:
 > This doesn't actually want to be an XXXX023 -- I already resolved it in
 master. (If you change it here you will find a conflict when you try to
 merge.)

 I'm going to leave it as XXX023, and resolve the conflict in favor of
 master when I merge.  The alternative is to leave it as XXX022, which
 would be wrong, since we *don't* intend to fix it in 0.2.2.

 Replying to [comment:8 arma]:
 > This replacement doesn't produce exactly the same functionality. I'm not
 sure if we care.

 I am pretty sure that we don't care.  To get the original behavior, we'd
 actually want to add in 60 seconds of allowable delay between certificate
 expiry and deciding that it's actually expired.  But I don't believe that
 really buys us anything.

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