Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

doc: show how to use the experimental tls factory #20

Merged
merged 3 commits into from
Jan 4, 2022

Conversation

bassosimone
Copy link
Contributor

@bassosimone bassosimone commented Jan 4, 2022

This commit adds a new example showing how one can use the
experimental TLSClientFactory function to create an uTLS
connection when using a SOCKS5 (or other) proxy.

Users have requested this functionality.

The new example seems to work for me.

Compare:

sbs@localhost:~$ go run . -utls | jq -r .ja3_hash
0ffee3ba8e615ad22535e7f771690a28

to:

sbs@localhost:~$ go run . | jq -r .ja3_hash
3fed133de60c35724739b913924b6c24

Once users have confirmed this code works as intended, I'll
update the README to advert this functionality.

This commit adds a new example showing how one can use the
experimental TLSClientFactory function to create an uTLS
connection when using a SOCKS5 (or other) proxy.

Users have requested this functionality.

The example seems to work for me.

Compare:

```
sbs@localhost:~$ go run . -utls | jq -r .ja3_hash
0ffee3ba8e615ad22535e7f771690a28
```

to:

```
sbs@localhost:~$ go run . | jq -r .ja3_hash
3fed133de60c35724739b913924b6c24
```

Once users have confirmed this code works as intended, I'll
update the README to advert this functionality.
Interestingly, I didn't see this on macOS but now I see it on
my Linux system (where I just tested with `-race`).
@bassosimone bassosimone merged commit ce1c6b5 into main Jan 4, 2022
@bassosimone bassosimone deleted the tls-factory-example branch January 4, 2022 15:48
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant