Opened 4 years ago

Closed 4 years ago

#8944 closed defect (fixed)

pyobfsproxy rename necessitates different bundle App directory structure

Reported by: dcf Owned by: asn
Priority: Medium Milestone:
Component: Obfuscation/Obfsproxy Version:
Severity: Keywords: flashproxy
Cc: Actual Points:
Parent ID: Points:
Reviewer: Sponsor:

Description

Since the program name is now "obfsproxy", it conflicts with the Python module of the same name. Before 3b80ce41 we had this structure in bundle App directories:

pyobfsproxy*
obfsproxy/

But now we can't do that because the names are the same:

obfsproxy*
obfsproxy/

Some options:

  1. Call the executable obfsproxy.bin only in the bundles.
  2. Put the obfsproxy executable in bin/obfsproxy in the bundles.

Child Tickets

Change History (4)

comment:1 Changed 4 years ago by dcf

Keywords: flashproxy added

comment:2 Changed 4 years ago by dcf

My plan for this is to call the executable obfsproxy.bin in the directory tree and in torrc.

comment:3 in reply to:  2 Changed 4 years ago by asn

Replying to dcf:

My plan for this is to call the executable obfsproxy.bin in the directory tree and in torrc.

Sounds good. Thanks for taking the initiative.

comment:4 Changed 4 years ago by dcf

Resolution: fixed
Status: newclosed
Note: See TracTickets for help on using tickets.