Just a disclaimer - I do not understand Tor very well.

I was trying to set up a bridge, but it failed after getting 2% bootstrapped. Something to do with general SOCK handshake failure.

I also tried setting up relay, but my browser (LibreWolf) won’t work after setting up a SOCK proxy. The bootstrap would however complete by 100%. It says something about waiting for 20 minutes, but still won’t work?

I would appreciate it if someone could share their config. And about Arti, is it worth using over Tor?

  • 0v0@sopuli.xyz
    3·
    1 year ago

    I’m not on NixOS, but I have a decent working knowledge of Tor.

    Not quite clear on what you’re trying to do, are you trying to run a relay, or just connecting to the Tor network and pointing your browser to the socks proxy?

    Arti (the official Tor implementation in Rust) is not a complete replacement for the Tor C implementation yet. Hidden service support is disabled by default (due to the lack of a security feature that could allow guard discovery attacks), and bridges don’t work either. If you don’t understand Tor very well stick with the old router.

    • AureumTempus@lemmy.worldOP
      3·
      1 year ago

      Hey, I wanted to run my own bridge - I think it’s also called a bridge relay? In this particular case, I’m trying to setup obfs4, but I’m also okay with Snowflake. Correct me if I’m wrong, but I also want to use my browser to connect to the localhost proxy. But the connection keeps getting rejected.

      • 0v0@sopuli.xyz
        1·
        1 year ago

        Here is a config template to run an obfs4 bridge, make changes as required:

        BridgeRelay 1

# Replace "TODO1" with a Tor port of your choice.
# This port must be externally reachable.
# Avoid port 9001 because it's commonly associated with Tor and censors may be scanning the Internet for this port.
ORPort TODO1

ServerTransportPlugin obfs4 exec /usr/bin/obfs4proxy

# Replace "TODO2" with an obfs4 port of your choice.
# This port must be externally reachable and must be different from the one specified for ORPort.
# Avoid port 9001 because it's commonly associated with Tor and censors may be scanning the Internet for this port.
ServerTransportListenAddr obfs4 0.0.0.0:TODO2

# Local communication port between Tor and obfs4.  Always set this to "auto".
# "Ext" means "extended", not "external".  Don't try to set a specific port number, nor listen on 0.0.0.0.
ExtORPort auto

# Replace "" with your email address so we can contact you if there are problems with your bridge.
# This is optional but encouraged.
ContactInfo 

# Pick a nickname that you like for your bridge.  This is optional.
Nickname PickANickname

        You can also use the reachability test to check if everything is configured correctly. If it is reachable and bootstrapping reaches 100% you should be set.

        Set SocksPort if you want to connect your browser (don’t confuse this with ORPort). Default is localhost:9050.

        • AureumTempus@lemmy.worldOP
          1·
          1 year ago

          I’ve tried this again, yet it’s still not working. I keep getting some error about ORPort being set as null in the auto-generated torc file, despite setting the port. At least now I know that this is either due to a mistake in Nix derivation or the outdated documentation.