Please run a bridge relay! (was Re: Tor 0.2.0.13-alpha is out)

[Andrew Del Vecchio]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Sudo route and iptables -L don't show the below in the routing table as
being applied. Any debugging suggestions?

~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.


Drake Wilson wrote:
> Quoth Andrew Del Vecchio <firefox-gen at walala.org>, on 2007-12-23 13:36:45 -0800:
>> 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.
> 
> The obvious way to handle this, if you have iptables available, is
> probably to run the Tor server on some other port (say, 1443) and then
> use iptables to redirect incoming connections on port 443 to port 1443
> instead.  Something like (untested):
> 
>   iptables -t nat -A PREROUTING -d <tor-address> \
>     -p tcp --dport 443 -j DNAT --to-destination :1443
> 
>> Thanks,
>> Andrew
> 
>    ---> Drake Wilson
> 
> 
> 
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFHcV3wgwZR2XMkZmQRAmkqAJ9vquaFcjUhLhQ6RkSNFlOAb8Wh7wCePBP8
TE1tLGHWUNBMHxL7rru//0s=
=QdV0
-----END PGP SIGNATURE-----