Opened 6 years ago

Last modified 7 months ago

#9825 new defect

-v returns 'unknown' for Obfsproxy.exe from '2.4.17-beta-2-pt3'

Reported by: bastik Owned by:
Priority: Low Milestone:
Component: Archived/Obfsproxy Version:
Severity: Normal Keywords:
Cc: Actual Points:
Parent ID: Points:
Reviewer: Sponsor:

Description

obfsproxy.exe -v

prints out

unknown

It was included in 'tor-pluggable-transports-browser-2.4.17-beta-2-pt3_en-US.exe' and its (obfsproxy.exe) checksums are:

SHA-1: 8690778C86542ABC3596C65EF42903E943C843A9
SHA-256: F75A997308B689335AEA9705BF7DF57EEA0636CB7C2EB7D75BCAC41389F0F84F
SHA-512: 89459D5189C2490C22FA63AC8509AEF8B7902B38174C73BB2902C57F73DFAFC4EC42B1C361ADDBEB019D7709882589594D94FD264FD20A2712592326596B1107

Child Tickets

Change History (7)

comment:1 Changed 6 years ago by asn

Ugh, thanks for reporting this.

I have no idea what's going on there. It's probably related to the versioneer script (https://github.com/warner/python-versioneer) and the way obfsproxy is built in Windows...

Need to find some time to debug this.

comment:2 Changed 6 years ago by arma

Summary: -v returns 'unkown' for Obfsproxy.exe from '2.4.17-beta-2-pt3'-v returns 'unknown' for Obfsproxy.exe from '2.4.17-beta-2-pt3'

comment:3 Changed 6 years ago by asn

this was verified by another windows user. Seems like the versioneer script or the way we use it is to blame.

comment:4 Changed 6 years ago by asn

I talked with Brian and he told me that versioneer is very likely to misbehave in Windows. Mainly because the git executable might not be locatable.

He said that if someone with Windows knowledge is interested in debugging this, he could help fix the issue. Anyone interested?

comment:5 Changed 21 months ago by teor

Severity: Normal

Set all open tickets without a severity to "Normal"

comment:6 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:7 Changed 7 months ago by cohosh

Status: assignednew

tickets are unassigned, reverting to 'new'

Note: See TracTickets for help on using tickets.