Re: [tor-bugs] #6274 [Tor Client]: config parsing does not abort if ServerTransportPlugin but no ORPort

["Tor Bug Tracker & Wiki" <torproject-admin@xxxxxxxxxxxxxx>]

#6274: config parsing does not abort if ServerTransportPlugin but no ORPort
------------------------+---------------------------------------------------
 Reporter:  asn         |          Owner:                    
     Type:  defect      |         Status:  needs_review      
 Priority:  normal      |      Milestone:  Tor: 0.2.3.x-final
Component:  Tor Client  |        Version:                    
 Keywords:  pt          |         Parent:                    
   Points:              |   Actualpoints:                    
------------------------+---------------------------------------------------
Changes (by asn):

  * status:  needs_revision => needs_review


Comment:

 Replying to [comment:2 nickm]:
 > Not sure I agree.  It's okay to specify lots of other server-only stuff
 when ORPort is disabled.  Rather than requiring that you turn off
 ServerTransportPlugin before we undefine ORPort, I think it would make
 more sense to just ignore ServerTransportPlugin when ORPort is disabled.
 >

 Makes sense.

 > Also, this ticket is for 0.2.3.x, but the branch is on master, it
 appears.

 Please see branch `bug6274_take2` in
 `https://git.gitorious.org/mytor/mytor.git`. I hope it's correctly rebased
 to maint-0.2.3.

-- 
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/6274#comment:3>
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