Archives
/
obfs4
mirror of https://gitlab.com/yawning/obfs4
2
0
Fork 0
Code Issues Projects Releases Wiki Activity
You cannot select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
master
obfs4proxy-0.0.14
obfs4proxy-0.0.13
obfs4proxy-0.0.12
obfs4proxy-0.0.11
obfs4proxy-0.0.10
obfs4proxy-0.0.9
obfs4proxy-0.0.8
obfs4proxy-0.0.7
obfs4proxy-0.0.6
obfs4proxy-0.0.5
obfs4proxy-0.0.4
obfs4proxy-0.0.3
obfs4proxy-0.0.2
obfs4proxy-0.0.1
Branches Tags
${ item.name }
Create tag ${ searchTerm }
Create branch ${ searchTerm }
from '09633500b3'
${ noResults }
obfs4/obfs4proxy
History
Yawning Angel ce86fa4348 Change the default logLevel to ERROR, upgrade some client warnings. 
Client side logs are less spammy than server side in general, so more
messages should be visible at the default logLevel when running as a
client.

Server side logging will be spammy basically no matter what unless
obfs4proxy gets into the (arguably dangerous) business of figuring out
which errors are people being evil vs which ones are transient network
issues, so most logging is suppressed by default, unless the admin
choses to open the floodgates.
 		10 years ago
..
log.go Add a prolog/epilog to the logging that always gets logged. 10 years ago
obfs4proxy.go Change the default logLevel to ERROR, upgrade some client warnings. 10 years ago
proxy_http.go Massive cleanup/code reorg. 10 years ago
proxy_socks4.go Massive cleanup/code reorg. 10 years ago
pt_extras.go Massive cleanup/code reorg. 10 years ago