On 2023-03-12 09:53 AM, Stuart Henderson wrote: > I don't think the problem you're seeing is related to login.conf but a > few comments on that, > > ... > > I suggest removing login.conf.db (it is not created by default) and not > using cap_mkdb, to avoid any problems with the db file getting out of > sync after other changes. You probably want to override openfiles-cur as > well, not just -max.
Done. Thanks for the insight, Stuart. > Note any daemon-specific config here will only be used automatically if > you're running it via rcctl or the rc.d script. (If you run it "by hand" > you can set the login class with su -c or sudo -c). I’m aware of that, but thank you for clarification nonetheless. > It doesn't help your problem with obfs4proxy but snowflake_proxy is for > providing access to others; you want snowflake_client (it's in -current > but was not built in the package until after 7.2-release). Thank you for the heads up! That was quite a revelation to me that this particular package gets shipped with three binaries for different purposes—should’ve taken advantage of pkg_info’s -L option, my bad. I’ve just upgraded to 7.3-beta and updated the snowflake_proxy package to version 2.5.1; here’s the updated contents of my torrc file: $ grep '^[A-Z]' /etc/tor/torrc Log notice syslog RunAsDaemon 1 DataDirectory /var/tor User _tor UseBridges 1 ClientTransportPlugin snowflake exec /usr/local/bin/snowflake_client Bridge snowflake 192.0.2.3:1 url=https://snowflake-broker.torproject.net.global.prod.fastly.net/ front=cdn.sstatic.net ice=stun:stun.l.google.com:19302,stun:stun.antisip.com:3478,stun:stun.bluesip.net:3478,stun:stun.dus.net:3478,stun:stun.epygi.com:3478,stun:stun.sonetel.com:3478,stun:stun.uls.co.za:3478,stun:stun.voipgate.com:3478,stun:stun.voys.nl:3478 Tor keeps spewing logs of the same kind, however. Nothing has changed. I have no idea as to what else can be done to make Tor start building circuits. I would’ve posted on Tor mailing lists if I had experienced the same issues on my GNU/Linux machine as well as on my Android device, but things appear to be working there just fine. Can you or anybody else reading this message give me some insight into ways of finding the root of the problem? I’m at a loss here. Many thanks in advance.
