Opened 7 weeks ago

Last modified 7 weeks ago

#29286 new task

Maintain obfs4 proxy

Reported by: cohosh Owned by:
Priority: Medium Milestone:
Component: Obfuscation/Obfsproxy Version:
Severity: Normal Keywords: obfs4, maintainance
Cc: cohosh, yawning Actual Points:
Parent ID: Points:
Reviewer: Sponsor: Sponsor19

Description

This depends first on ticket #29279 and seeing what is possibly going wrong with obfs4 now.

Child Tickets

Change History (5)

comment:1 Changed 7 weeks ago by teor

Owner: asn deleted
Status: newassigned

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

comment:2 Changed 7 weeks ago by yawning

Is this a out of season April fool's joke?

comment:3 Changed 7 weeks ago by yawning

Cc: yawning added

comment:4 Changed 7 weeks ago by ahf

While it may seem plausible that this is an off season April 1st joke since we are off exactly by two months from the 1st of April when this ticket was created, but no, that is not the case :-)

This ticket was created as part of a larger roadmap session we did in Brussels for Tor's new anti-censorship team that we have recently been hiring for. The ticket is by no means a "let's take over maintainership from Yawning" ticket or anything like that. It should be seen more as a tracker bug for us to remember to look into obfs4 and if there is anything we can help with around obfs4. For example: we have recently added the LOG and STATUS handlers in little-t-tor and adding support for that in obfs4 might be something we should do.

Our main focus is going to be on getting the Snowflake PT into a state where we can ship it with Tor browser, but we are also interested in helping out with anything around obfs4 wherever we can :-)

comment:5 Changed 7 weeks ago by cohosh

Status: assignednew

tickets are unassigned, reverting to 'new'

Note: See TracTickets for help on using tickets.