Opened 5 years ago

Last modified 7 months ago

#11134 new defect

obfsproxy's SOCKS server should send success response post handshake

Reported by: yawning Owned by:
Priority: Medium Milestone:
Component: Archived/Obfsproxy Version:
Severity: Normal Keywords: SOCKS response, handshakeing
Cc: Actual Points:
Parent ID: Points:
Reviewer: Sponsor:

Description

Currently the obfsproxy SOCKS server sends the response back to tor immediately after the TCP/IP connection has been established, instead of after the underlying transport has been fully initialized.

This behavior is incorrect, and should be changed to each of the underlying transports signalling that they are ready to relay data after they manage to handshake.

With the current SOCKSv4Protocol based listener this would require further monkey patching which may be a good argument for defering this till after #9221 or similar gets merged.

Child Tickets

Change History (3)

comment:1 Changed 21 months ago by teor

Severity: Normal

Set all open tickets without a severity to "Normal"

comment:2 Changed 7 months ago by teor

Owner: asn deleted
Status: newassigned

asn does not need to own any obfuscation tickets any more. Default owners are trouble.

comment:3 Changed 7 months ago by cohosh

Status: assignednew

tickets are unassigned, reverting to 'new'

Note: See TracTickets for help on using tickets.