obfsproxy(1) [debian man page]

OBFSPROXY(1)							   User Manuals 						      OBFSPROXY(1)

NAME

       obfsproxy - a pluggable transports proxy

SYNOPSIS

       obfsproxy [obfsproxy_args] protocol_name [protocol_args] protocol_options protocol_name

DESCRIPTION

       obfsproxy  is  a  tool that attempts to circumvent censorship, by transforming the Tor traffic between the client and the bridge. This way,
       censors, who usually monitor traffic between the client and the bridge, will see innocent-looking transformed traffic instead of the actual
       Tor traffic.

       obfsproxy  supports multiple protocols, called pluggable transports, which specify how the traffic is transformed. For example, there might
       be a HTTP transport which transforms Tor traffic to look like regular HTTP traffic.

OPTIONS

       --log-file=<file>
	      Set logfile

       --log-min-severity=warn|info|debug|notice
	      Set minimum logging severity

       --no-log
	      Disable logging

SEE ALSO

       tor(1)

       https://www.torproject.org/

BUGS

       Plenty, probably.  obfsproxy is still in development.  Please report them.

AUTHOR

       George Kadianakis <asn at torproject.org>.

Linux								    02/12/2012							      OBFSPROXY(1)

LWP::Debug(3)						User Contributed Perl Documentation					     LWP::Debug(3)

NAME

       LWP::Debug - deprecated

DESCRIPTION

       LWP::Debug used to provide tracing facilities, but these are not used by LWP any more.  The code in this module is kept around
       (undocumented) so that 3rd party code that happen to use the old interfaces continue to run.

       One useful feature that LWP::Debug provided (in an imprecise and troublesome way) was network traffic monitoring.  The following section
       provide some hints about recommened replacements.

   Network traffic monitoring
       The best way to monitor the network traffic that LWP generates is to use an external TCP monitoring program.  The Wireshark program
       (<http://www.wireshark.org/>) is higly recommended for this.

       Another approach it to use a debugging HTTP proxy server and make LWP direct all its traffic via this one.  Call "$ua->proxy" to set it up
       and then just use LWP as before.

       For less precise monitoring needs just setting up a few simple handlers might do.  The following example sets up handlers to dump the
       request and response objects that pass through LWP:

	 use LWP::UserAgent;
	 $ua = LWP::UserAgent->new;
	 $ua->default_header('Accept-Encoding' => scalar HTTP::Message::decodable());

	 $ua->add_handler("request_send",  sub { shift->dump; return });
	 $ua->add_handler("response_done", sub { shift->dump; return });

	 $ua->get("http://www.example.com");

SEE ALSO

       LWP::UserAgent

perl v5.18.2							    2012-01-13							     LWP::Debug(3)