From 514c3c6053ee3a2d3a842fd59b623ef432d93b7d Mon Sep 17 00:00:00 2001 From: Yawning Angel Date: Wed, 24 Sep 2014 16:00:42 +0000 Subject: Write an example obfs4 bridge line to "obfs4_bridgeline.txt". Write an example client bridge line suitable for use with the running obfs4 server instance to "obfs4_bridgeline.txt" for the convenience of bridge operators. --- doc/obfs4proxy.1 | 9 ++++++++- 1 file changed, 8 insertions(+), 1 deletion(-) (limited to 'doc') diff --git a/doc/obfs4proxy.1 b/doc/obfs4proxy.1 index bda677a..e442946 100644 --- a/doc/obfs4proxy.1 +++ b/doc/obfs4proxy.1 @@ -1,4 +1,4 @@ -.TH OBFS4PROXY 1 "2014-09-06" +.TH OBFS4PROXY 1 "2014-09-24" .SH NAME obfs4proxy \- pluggable transport proxy for Tor, implementing obfs4 .SH SYNOPSIS @@ -53,6 +53,13 @@ The Bridge (server) auto-generated obfs4 bridge parameters file. This file will not be created if the administrator specifies them in the \fBtorrc\fR via a \fBServerTransportOptions\fR directive. .RE +.PP +\fIDataDirectory\fR\fB/pt_state/obfs4_bridgeline.txt\fR +.RS 4 +The Bridge (server) obfs4 bridge's client parameters. This file is created +and contains the \fBBridge\fR directive a client should add to their +\fBtorrc\fR to connect to the running server's obfs4 instance. +.RE .SH "CONFORMING TO" Tor Pluggable Transport Specification .SH NOTES -- cgit v1.2.3