Opened 5 years ago

Closed 5 years ago

#14217 closed defect (user disappeared)

Address translation is not working

Reported by: masterkorp Owned by: asn
Priority: Medium Milestone:
Component: Archived/Obfsproxy Version:
Severity: Keywords:
Cc: phw Actual Points:
Parent ID: Points:
Reviewer: Sponsor:

Description

Address translation is not working on obfsproxy.

When running obfsproxy with OpenVPN both obfsproxy server and client need to be on the same machine was the OpenVPN server and client, so the the address used to communicate is 127.0.0.1

References:
https://forums.openvpn.net/topic17960.html

Child Tickets

Change History (3)

comment:1 Changed 5 years ago by masterkorp

Priority: criticalmajor

comment:2 Changed 5 years ago by yawning

Cc: phw added
Priority: majornormal
Status: newneeds_information

So, a few things:

  • I have no idea what you mean by "When running obfsproxy with OpenVPN both obfsproxy server and client need to be on the same machine was the OpenVPN server and client, so the the address used to communicate is 127.0.0.1".
  • I don't use OpenVPN, and do not have the time to replicate your setup, so I will need the obfsproxy logs.
  • As far as I am aware, external mode for ScrambleSuit works fine with obfsproxy.

Since this doesn't affect the tor PT use case, it's not a security issue, and this sort of setup should work, I'm going to lower the priority to normal for now as well.

comment:3 Changed 5 years ago by yawning

Resolution: user disappeared
Status: needs_informationclosed

From the associated tor-dev@ thread, I'm more inclined to "not a bug" this, but since there's been no movement on this in a while, this will suffice.

https://lists.torproject.org/pipermail/tor-dev/2015-January/008161.html

Note: See TracTickets for help on using tickets.