How do I build the obfs4_bridgeline.txt

My 2 debian bookworm bridges I just installed were missing the pt_state directory with the 2 files in it: obfs4_bridgeline.txt, obfs4_state.json.
I can find the ip, port and fingerprint to put in it, but don’t know where to find the cert. It seems to have been supplied automatically in earlier bridges. I think I could find it somewhere, but can’t think how to supply the obfs4_state.json file.

I have no idea how this affects the distribution type or not at all or how to re-populate the pt_state directory. Is this important enough to worry about?

1 Like

Only the json file in the pt_state directory is needed. Set the owner ship to tor. As soon as tor starts and launches obfs4, the bridge txt file is generated.
The json file is the id of the obfs4 bridge and holds private and public keys.

1 Like

I have no json file at all, as the pt_state directory was never created on install. Now I have created the pt_state directory, would removing and reinstalling obfs4 create the json file? I don’t know how this works.

···

On Tuesday, April 16th, 2024 at 7:54 PM, Felix via Tor Project Forum noreply@forum.torproject.org wrote:

Felix
April 16

Only the json file in the pt_state directory is needed. Set the owner ship to tor. As soon as tor starts and launches obfs4, the bridge txt file is generated.
The json file is the id of the obfs4 bridge and holds private and public keys.


Visit Topic or reply to this email to respond.

To unsubscribe from these emails, click here.

1 Like

Could you share your torrc?

2 Likes

Sure:

Log notice file /var/log/tor/notices.log
DisableDebuggerAttachment 0
ControlPort 9051
CookieAuthentication 1
DataDirectoryGroupReadable 1
CookieAuthFileGroupReadable 1
ExtORPortCookieAuthFileGroupReadable 1
CacheDirectoryGroupReadable 1
CookieAuthFile /var/lib/tor/control_auth_cookie
ORPort 7612
##TOR WON'T START WHEN IPV6 ORPORT IS NOT REMMMED OUT
#ORPort [2001:678:6d4:5030::a121:103]:7612
#ORPort [2001:678:6d4:5000::a13b:12d]:7612
ServerTransportPlugin obfs4 exec /usr/local/bin/obfs4proxy
ServerTransportListenAddr obfs4 0.0.0.0:8847
ServerTransportOptions obfs4 iat-mode=2
# Enable Extended ORPort
ExtORPort auto
Nickname Aramis57
ContactInfo email:torix@protonmail.com url:https://torix-relays.org proof:uri-rsa hoster:alexhost.com ciissversion:2

MetricsPort 127.0.0.1:9035
MetricsPortPolicy accept 127.0.0.1
#BridgeDistribution moat
RunAsDaemon 1
BridgeRelay 1
···

On Tuesday, April 16th, 2024 at 8:54 PM, Gus via Tor Project Forum noreply@forum.torproject.org wrote:

gus Community Team lead
April 16

Could you share your torrc?


Visit Topic or reply to this email to respond.

To unsubscribe from these emails, click here.

1 Like

How you installed obfs4proxy?
Did you compile from the source or installed via apt?

If you installed via apt, the correct line is:

ServerTransportPlugin obfs4 exec /usr/bin/obfs4proxy
1 Like

Thank you, Gus! I had missed that line - the torrc came over from when it was running on freeBSD. I changed the path, restarted tor, and the pt_state and files were created.

–Torix

···

On Wednesday, April 17th, 2024 at 9:51 PM, Gus via Tor Project Forum noreply@forum.torproject.org wrote:

gus Community Team lead
April 17

torix:

ServerTransportPlugin obfs4 exec /usr/local/bin/obfs4proxy

How you installed obfs4proxy?
Did you compile from the source or installed via apt?

If you installed via apt, the correct line is:

ServerTransportPlugin obfs4 exec /usr/bin/obfs4proxy


Visit Topic or reply to this email to respond.

To unsubscribe from these emails, click here.

2 Likes

This topic was automatically closed 24 hours after the last reply. New replies are no longer allowed.