-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Roger, I'm good to go except for one thing: The permissions issue with the port being 443 (less than 1024). Is there an easy way around this without having to create a chroot jail, etc? I'm using the latest Ubuntu 7.10. I can change file permissions but I don't want to create a security vulnerability.
Thanks, Andrew - -- People just like you lose untold millions in personal wealth due to frivolous lawsuits and unfair government seizures. Are you protected? Read the Asset Protection Crash Course at http://www.keepyourassets.net?andrew to find out how to protect your hard-earned assets. Roger Dingledine wrote: > On Sat, Dec 22, 2007 at 04:19:09AM -0500, Roger Dingledine wrote: >> Tor 0.2.0.13-alpha adds a fourth v3 directory authority run by Geoff >> Goodell, fixes many more bugs, and adds a lot of infrastructure for >> upcoming features. > > Hi folks, > > One of the new features we've been working on is called "bridges". We > need some volunteers to run more of them. > > Bridge relays (or "bridges" for short) are Tor relays that aren't listed > in the main directory. Since there is no complete public list of them, > even if an ISP is filtering connections to all the known Tor relays, > they probably won't be able to block all the bridges. From the operator's > perspective, unlike running an exit relay, running a bridge relay just > passes data to and from the Tor network, so it shouldn't expose the > operator to any abuse complaints. > > First, install the latest development bundle from > https://www.torproject.org/download#Dev > There are two ways to set up a bridge. The easy way is to go into > Vidalia's Settings -> Relay window, and click "Help censored users > reach the Tor network". You might want to click on 'Bandwidth Limits' > too and set that to something smaller. Then click save. > > The harder way is to edit your torrc file manually > https://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ#torrc > and add the following lines: > ORPort 443 > BridgeRelay 1 > PublishServerDescriptor bridge > ExitPolicy reject *:* > RelayBandwidthRate 50 KBytes > > In either case, your next step is to mess with your Linksys router or > whatever you're using, and set up port forwarding so connections will > make it to port 443 of the computer running the bridge relay. Then check > your 'Message Log' window to see whether "Self-testing indicates your > ORPort is reachable from the outside", or "Your server has not managed > to confirm that its ORPort is reachable." > > If you're interested, you can see a few bridges listed here: > https://bridges.torproject.org/ > You only learn a small number of bridges from any single location, to > make it a bit harder for attackers to learn them all. We've still got a > big pile of items on the bridge todo list, but having more bridges for > testing is really useful for the next steps. > > Plus there are people in the world who need them. :) > > Thanks! > --Roger > > > > -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFHbtTtgwZR2XMkZmQRAuuwAJ9Sgcp34KzaNjrBKjTldnAtdryurwCfQIBi LScWtlZzJHqpjjmZHRO2b40= =CErh -----END PGP SIGNATURE-----
