[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]

Re: another tor issue...? (irc...)

I rather suspect that you are not going to be able to resolve the issue so 
long as you run an exit.  It doesn't matter what sort of traffic you block, 
all that matters is that your ip will appear in the list of published exit 
nodes shortly after you start it up and that list will lead to you being 
blocked by other sites.

You will either need to operate an exit node from a separate IP than the 
computer (physically or via a separate proxy) you wish to connect to freenode 
with (or use their hidden service) and Slashdot or you will need to forego 
running an exit, no matter how configured (I suppose if you personally knew 
someone at Slashdot or one of the admins of freenode you might finangle a 
personal exception...).

Most of these sites have this policy because of actual past abuses rather than 
a general philosophical dislike of anonymity or tor.

On Monday 05 January 2009 12:03:55 Udo van den Heuvel wrote:
> Praedor Atrebates wrote:
> > To regain normal access, you have to ensure you are not running a tor
> > exit AND you need to contact the freenode operators and request you be
> > unblocked, explaining that you are not running (or are no longer running)
> > a tor exit node.
> I did so, thanks. (worked OK)
> So how can I open exit ports without fearing (too much) abuse or bad
> response from otherwise OK services?
> (even slashdot has tor issues!)

"Moral indignation is jealousy with a halo."
--H.G. Wells

Attachment: signature.asc
Description: This is a digitally signed message part.