When setting up an obfs4 bridge, the user has to perform extra steps to fill in the missing values to construct the full bridge line from /var/lib/tor/pt_state/obfs4_bridgeline.txt.
Specifically in:
Bridge obfs4 <IP ADDRESS>:<PORT> <FINGERPRINT> cert=<CERTIFICATE> iat-mode=0
only cert is populated automatically
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Child items ...
Show closed items
Linked items 0
Link issues together to show that they're related.
Learn more.
I'm tempted to call this a Tor ticket then, and Tor should write the whole bridge line to a log entry, or to a state file, or some other smart place?
(I imagine some people will be nervous about the idea of putting it in the log file, "because what if the operator accidentally reveals it to somebody", but I think usability trumps risk here.)
That's what I would propose. Instead of passing extra information (that's not needed for anything other than this ticket) to each PT provider, it makes more sense to me to do it at a place where all of the information already exists.
and Tor should write the whole bridge line to a log entry, or to a state file, or some other smart place?
Maybe follow the obfs4 model and write all of the bridge lines to $DATADIR/pt_state/bridgelines.txt perhaps.