| Age | Commit message (Collapse) | Author | Files | Lines |
|
|
|
Somewhat refactors how some obfuscation related types display themselves
|
|
|
|
|
|
|
|
|
|
This has the following benefits:
* It's a somewhat standard way of representing such a thing
* It's shorter
* It ties the protocol closer to the SocketAddr data it's associated to
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
We recently changed the cipher from chacha20 -> aes-256-gcm
and the password from 23#dfsbbb to mullvad
on port 443 on all our shadowsocks bridges
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
a specific protocol
|
|
|
|
|
|
|
|
|
|
only some options in the CLI
|
|
|
|
|
|
|
|
|
|
|