Re: Default Exit Policy

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 What about creating a white list/black list for domains in Tor. That way Tor could allow certain domains (such as google.com) to bypass the default blocks. This way you would be maintaining security while adding functionality. -BEGIN PGP SIGNA

Router Flags

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Can someone explain what these router flags mean? Some of them I have a good guess what they mean but I decided to list them all. Authority Bad Directory Bad Exit Exit Fast Guard Hibernating Named Stable Running Valid V2Dir -BEGIN PGP SIGNATURE-

Default Exit Policy

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I was looking at my server's stats at https://torstatus.kgprog.com and noticed that it has an exit policy that I didn't put in my config file. For example... reject 0.0.0.0/8:* reject 169.254.0.0/16:* reject 127.0.0.0/8:* reject 192.168.0.0/16:* re

Re: unsubscribe

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Thursday 22 May 2008 05:16:15 am [EMAIL PROTECTED] wrote: > unsubscribe Email [EMAIL PROTECTED] with the body [unsubscribe or-talk] -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.4-svn0 (GNU/Linux) iD8DBQFINhKrvsn/sQCIOqQRAkNMAJ9lb+W2tMsnEhRSSmM

Re: GPG Public Keys

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Thursday 22 May 2008 04:35:55 am Sebastian Hahn wrote: > I'm still looking for a solution, and might switch to mutt when I have > the time to set up my mail system properly. One solution I might recommend is figuring out what you're doing different

Re: GPG Public Keys

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Wednesday 21 May 2008 06:57:41 pm Sebastian Hahn wrote: > are you sure this is not just because subkeys.pgp.net ist not > functional currently and it's the only keyserver you use? This has > caused some problems for some people... > > I've also uplo

GPG Public Keys

I noticed some of you have GPG keys. I tried searching key servers so I can add your public keys to my list. It would seem either I'm not searching the right servers or none of you have uploaded them. So I'm asking that all of you respond with your public keys and I'll do the same. 0xC109AB

Re: Ports 443 & 80

On Sunday 18 May 2008 12:50:27 pm morphium wrote: > why don't you set ORListenAddress to 0.0.0.0:443 and don't do anything > with your firewall? I'm running Linux. You can only open certain lower ports (such as 80 & 443) in root. And it's bad to run tor as root.

Re: Ports 443 & 80

I just tried something else and I managed to get it working. :-) The problem was I was over thinking the solution. I set the ports in torrc back to their defaults ORPort 9001 & DirPort 9030. Instead, what I did was have the port forwaring on the router level... 443 --> 9001 & 80 --> 9030. T