On 5/20/15, s7r wrote:
> On 5/20/2015 12:07 PM, Tor User wrote:
>> If I'm wrong about this, that's great - I'd love to see some
>> documentation to explain it better if you have any links handy.
>> But if I'm right, how can I configure our TBB clients to actually
>> MAKE them use our TOR proxy as
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Thanks for the eloquent response. Many good points made and apologies if
my comments came across as being critical of the Tor development
community. I have no plans to take down the relays I'm running any time
soon -- bwauth hiccups or not. Regard
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hi
Glad you understood what you are doing wrong. In this case, you can
use your relay as a guard for the clients in your network. See in my
previous email suggestion #2, and all your clients will have the
desired guard. Install Tor browser on each c
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hello Julian
Thanks for your contribution to Tor!
Please keep them running, as much as you can. We already struggle to
(at least partially) solve the issue for the short term, by launching
more bandwidth authorities. On the long term, some research
Companies such as DirecTV blacklist all Tor relays. This is very
disconcerting when I go to their site to get help with my television
feed. In their defense (and this hurts), their Genie system uses
some of the ports that Tor uses for ORPorts such as 9001.
L Brandt
Hi s7r,
Thank you for your reply. There's a lot of good info in it and I'll be
reconfiguring the clients.
The fact that I've been doing Tor-through-Tor unawares explains a lot.
It did seem odd to have polipo in the mix, but it makes sense now, that
would only be if the LAN clients weren't
Nothing.
There are DNS blacklists for TOR nodes. For some wild reason they're called
blacklists, but they just indicate that a particular IP runs a
node/relay/bridge. Some idiots even ban IPs in these blacklists even if
it's not an exit.
Just explain this to your hoster and forget about it.
On Sat
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Hey guys,
Today I got a complaint from my vServer hoster that has received an abuse email
The company who accused the usage of my system is called sectoor
http://www.sectoor.de/tor
Here's the abuse message:
More Information About Sectoor
Listin