Re: [tor-relays] Multiple ServerTransportListenAddr OBFS2|3|4 Configuration

2022-12-14 Thread Gary C. New via tor-relays
On Wednesday, December 14, 2022, 02:55:05 AM MST, trinity pointard wrote: Hi trinity! >> As an added bonus, obfs4proxy also supports acting as an obfs2/3 client and >> bridge to ease the transition to the new protocol. >> My question is whether the respective obfs2|3|4 transport names force

Re: [tor-relays] Multiple ServerTransportListenAddr OBFS2|3|4 Configuration

2022-12-14 Thread trinity pointard
Hi, > I noticed that the obfs2, obfs3, and obfs4 transport names seem to be > hardcoded into tor. obfs2/3/4 has no special meaning to tor. In fact if you grep the codebase, you'll find obfs2 and obfs4 appears only in comments and tests, and obfs3 doesn't show up. The ability of obfs4proxy to wo

[tor-relays] Multiple ServerTransportListenAddr OBFS2|3|4 Configuration

2022-12-14 Thread Gary C. New via tor-relays
All: I noticed that the obfs2, obfs3, and obfs4 transport names seem to be hardcoded into tor. I have been able to configure the torrc to register each of the transports for multiple ServerTransportListenAddr: # cat torrc ORPort xxx.xxx.xxx.xxx:443 NoListen ORPort 192.168.0.31:9001 NoAdvertise