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.

Sign up for GitHub

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

Jump to bottom

Require Encrypted SNI in locations where it isn't blocked #49

Open
gnarea opened this issue Feb 18, 2020 · 0 comments
Open

Require Encrypted SNI in locations where it isn't blocked #49

gnarea opened this issue Feb 18, 2020 · 0 comments
Labels
attribute-privacy enhancement New feature or request

Comments

@gnarea
Copy link
Member

gnarea commented Feb 18, 2020 •
edited
Loading

48f9bf5 introduced a recommendation to use ESNI, but I think we should take this further and require it in places where it isn't blocked (it's blocked in China and India, for example).

This should be straightforward, but we need to check support across all supported platforms and I'm also debating whether to hold off doing this until the ESNI spec is finalised/stable.
gnarea added a commit that referenced this issue Jun 28, 2020
@gnarea
Core: Require TLS 1.3 or newer
362b69f 
This is needed to support ESNI eventually (per #49). Also, I was worried about the following not supporting TLS 1.3 but they do (now):

- Netty on Android (for the Android Courier).
- GCP.
@gnarea gnarea changed the title Require TLS 1.3+ and Encrypted SNI Require Encrypted SNI Jun 28, 2020
@gnarea gnarea mentioned this issue Jul 25, 2020
Open
@gnarea gnarea changed the title Require Encrypted SNI Require Encrypted SNI in locations where it isn't blocked Feb 17, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
attribute-privacy enhancement New feature or request
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@gnarea