v0.2.25

What's Changed

• Chore: Upgrade dependencies and use new async func in trait syntax by @ihciah

Full Changelog: v0.2.23...v0.2.25

v0.2.23

What's Changed

• Feat: Add config file support by @er888kh in #90
• Feat: resolve domain with spawn_blocking by @ihciah

New Contributors

• @er888kh made their first contribution in #90

Full Changelog: v0.2.22...v0.2.23

v0.2.22

What's Changed

• Feat: feat: use monoio 0.1.3 and support TCP_FASTOPEN @ihciah

About TCP_FASTOPEN

TFO is disabled by default. You can enable it by passing --fastopen or adding env FASTOPEN=1 if you are using docker. Also, make sure you have correct sysctl settings(net.ipv4.tcp_fastopen=3).
If you find any related problem, please disable it and submit an issue.

Full Changelog: v0.2.21...v0.2.22

v0.2.21

What's Changed

• Chore: build docker from release binary for faster and armv7l support @Kosette @ihciah

Full Changelog: v0.2.20...v0.2.21

v0.2.20

What's Changed

• Chore: adjust to new nightly toolchain @ihciah

Full Changelog: v0.2.19...v0.2.20

v0.2.19

What's Changed

• Feat: support wildcard SNI @ihciah

Related wiki: Use-shadow-tls-to-Bypass-Traffic-Billing-Systems

Full Changelog: v0.2.18...v0.2.19

v0.2.18

What's Changed

• Fix: not send tls alert on tls1.3 @ihciah

Full Changelog: v0.2.17...v0.2.18

v0.2.17

What's Changed

• Workflow related: add more container registries. @ihciah
• Better error output when bind failed. @ihciah

Full Changelog: v0.2.16...v0.2.17

v0.2.16

What's Changed

• Support TLS1.2 for V3 protocol non-strict mode. @ihciah

Full Changelog: v0.2.15...v0.2.16

About V3 Protocol

V3 protocol is a new version of shadow-tls, which solves all known security issues.

How to Use V3 Protocol

For compatibility reasons, the V3 protocol is not enabled by default. If you want to use it, add --v3(for command line users) or V3=1 environ(for docker users). V3 should be enabled or disabled on both side(V2 cannot communicate with V3).

If you use a third-party client, do not enable V3 before it support our V3 protocol on server side.

V3 protocol will be enabled by default on next major version.

More About V3 Protocol

Please refer to wiki for more details: https://github.com/ihciah/shadow-tls/wiki/V3-Protocol

v0.2.15

What's Changed

• Only Support TLS1.3 for V3 protocol. @ihciah
• Fix data bug for V3 protocol. @ihciah

Full Changelog: v0.2.14...v0.2.15

About V3 Protocol

V3 protocol is a new version of shadow-tls, which solves all known security issues.

How to Use V3 Protocol

For compatibility reasons, the V3 protocol is not enabled by default. If you want to use it, add --v3(for command line users) or V3=1 environ(for docker users). V3 should be enabled or disabled on both side(V2 cannot communicate with V3).

If you use a third-party client, do not enable V3 before it support our V3 protocol on server side.

V3 protocol will be enabled by default on next major version.

More About V3 Protocol

Please refer to wiki for more details: https://github.com/ihciah/shadow-tls/wiki/V3-Protocol