Opened 7 years ago

Closed 7 years ago

Last modified 18 months ago

#5063 closed task (fixed)

Create obfsproxy images for AWS

Reported by: runa Owned by: runa
Priority: Immediate Milestone:
Component: Archived/Tor Cloud Version:
Severity: Normal Keywords:
Cc: Actual Points:
Parent ID: Points:
Reviewer: Sponsor:

Description

We need more obfs2 servers. It would be nice if we could have images for various AWS regions ready to go.

Child Tickets

Change History (10)

comment:1 Changed 7 years ago by arma

Would it be bad to just add obfsproxy to our current bridge images for amazon? Then everybody running a bridge image would be accessible as a normal bridge or as an obfsproxy bridge.

Also, then we don't create a new image we have to maintain.

comment:2 in reply to:  1 ; Changed 7 years ago by rransom

Replying to arma:

Would it be bad to just add obfsproxy to our current bridge images for amazon? Then everybody running a bridge image would be accessible as a normal bridge or as an obfsproxy bridge.

I don't think it works that way. My understanding is that when someone launches an ‘instance’ of one of our images, Amazon makes a copy of its hard disk image in their account.

comment:3 in reply to:  2 Changed 7 years ago by arma

Replying to rransom:

Replying to arma:

Would it be bad to just add obfsproxy to our current bridge images for amazon? Then everybody running a bridge image would be accessible as a normal bridge or as an obfsproxy bridge.

I don't think it works that way. My understanding is that when someone launches an ‘instance’ of one of our images, Amazon makes a copy of its hard disk image in their account.

Sure. Fine. So that hard disk image should include obfsproxy, and the part of the hard disk image that configures what their Tor does should include launching the obfsproxy.

(We will want to change Tor so it advertises its obfsproxy address in, say, its extrainfo desc, if we want bridgedb to be able to learn about the obfsproxy address. That's probably on somebody's roadmap already.)

comment:4 Changed 7 years ago by runa

Sure, happy to just update the current bridge images instead of creating additional ones. The AWS bridges already running will not change, though.

Is there anything I should know that is not described on https://www.torproject.org/projects/obfsproxy-instructions.html.en ?

comment:5 in reply to:  4 Changed 7 years ago by runa

Replying to runa:

Sure, happy to just update the current bridge images instead of creating additional ones. The AWS bridges already running will not change, though.

... Assuming the required packages are available in Lucid Lynx.

comment:6 Changed 7 years ago by runa

Resolution: wontfix
Status: newclosed

Building obfsproxy bridge images with Ubuntu isn't as easy as I thought it would be. We currently have more than enough obfsproxy bridge addresses, so I'm going to close with as wontfix and reopen when we do need these images.

comment:7 Changed 7 years ago by runa

Priority: normalblocker
Resolution: wontfix
Status: closedreopened

Looks like we need to include Tor version 0.2.4x-alpha to have the bridges report directly to BridgeDB. Any chance we can have 0.2.4.x-alpha Debian packages?

comment:8 Changed 7 years ago by arma

Tor 0.2.4.1-alpha will be out in the next day or so, with debs following shortly after.

comment:9 Changed 7 years ago by runa

Resolution: fixed
Status: reopenedclosed

comment:10 Changed 18 months ago by teor

Severity: Normal

Set all tickets without a severity to "Normal"

Note: See TracTickets for help on using tickets.