[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
[tor-relays] Re: Self hosting bridge at home - de-anonymization risk?
I would worry about my IP address at home ending up on a blacklist, even
with a bridge. Google and Microsoft have hidden blacklists with secret
criteria to be listed there, and to get off them once listed is a
long-winded pain. You only know there is an issue when emails won't
arrive at gmail or Microsoft managed accounts and some web pages won't load.
WebTunnel https bridges seems safe and so far and my three had not ended up
on blacklists on my VPS servers. I think because they are still a minority
sport and have not been found by the blacklisting pedants.
Gerry
-----Original Message-----
From: Marco Predicatori via tor-relays <tor-relays@xxxxxxxxxxxxxxxxxxxx>
Sent: 28 March 2025 08:02
To: tor-relays@xxxxxxxxxxxxxxxxxxxx
Subject: [tor-relays] Re: Self hosting bridge at home - de-anonymization
risk?
bjewrn2a--- via tor-relays wrote on 3/26/25 22:48:
>> I have a non-exit node at home, and (...) I use Torbrowser that connects
with the usual 3 hops.
>
> Thanks Marco, yes, that's what I'm hoping to setup now, as well,
> however I haven't seen this setup recommended on the official
> torproject websites. If you are aware of any published studies or
> anything mentioned at conferences, please let me know. Tor network is
> a complex subject and although it makes sense to me it doesn't mean that a
professional would take the same approach.
Sorry bjewrn2a,
I'm not aware of any paper about my approach. It just makes sense to me, and
apparently to other people in this thread. Hopefully somebody from the Tor
Olympus will tackle the subject one day.
Bye, Marco
_______________________________________________
tor-relays mailing list -- tor-relays@xxxxxxxxxxxxxxxxxxxx To unsubscribe
send an email to tor-relays-leave@xxxxxxxxxxxxxxxxxxxx
_______________________________________________
tor-relays mailing list -- tor-relays@xxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to tor-relays-leave@xxxxxxxxxxxxxxxxxxxx