Re: [tor-relays] obfs4 bridge current setup is not entirely clear

On Mittwoch, 8. November 2023 20:35:56 CET s7r wrote: > boldsuck wrote: > > > > > Not recommended, but rather a request to try it out. > > > > > So I tried, and besides the log messages that I have a descriptor > mismatch I also get the status of my bridge as not running when ORPort > is not

Re: [tor-relays] obfs4 bridge current setup is not entirely clear

boldsuck wrote: Not recommended, but rather a request to try it out. So I tried, and besides the log messages that I have a descriptor mismatch I also get the status of my bridge as not running when ORPort is not exposed. The minute I switched ORPort to `localhost` the BridgeDB reported th

Re: [tor-relays] obfs4 bridge current setup is not entirely clear

On Mittwoch, 8. November 2023 17:42:46 CET s7r wrote: > 2. It was recommended on the mail list that obfs4 bridges should not > open their ORPorts publicly to prevent scanning the entire 1-65536 port > range and determine it's a Tor bridge. OK. Not recommended, but rather a request to try it out

[tor-relays] obfs4 bridge current setup is not entirely clear

Hi, I ran into some new IP space and I decided to change a cluster of obfs4 bridges that are more than 4 year old. When I set them up I don't remember spending so much time. So, Debian latest and Tor latest from deb.torproject.org nightly. GoLang from the official website (as it's the latest