[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]

Re: [tor-bugs] #6297 [Tor Client]: SOCKS issues with bitcoin in .2.3.18-rc vs .2.2.37

#6297: SOCKS issues with bitcoin in .2.3.18-rc vs .2.2.37
-------------------------+--------------------------------------------------
 Reporter:  jrmithdobbs  |          Owner:                   
     Type:  defect       |         Status:  needs_information
 Priority:  normal       |      Milestone:                   
Component:  Tor Client   |        Version:  Tor: 0.2.3.18-rc 
 Keywords:               |         Parent:                   
   Points:               |   Actualpoints:                   
-------------------------+--------------------------------------------------
Changes (by nickm):

  * status:  needs_revision => needs_information


Comment:

 I wouldn't mind a more accurate "Hey, there's some extra data there"
 warning to help programmers track down bugs in their socks
 implementations.

 I'm not sure what the security argument is, though: if an adversary can
 modify data send on your connection to your socks port, they can do worse
 than inject extra bytes, and they can do bad stuff without injecting extra
 bytes.

 Does the RFC require the server to do any particular behavior in this
 case?

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