Closed
Bug 1783791
Opened 2 years ago
Closed 2 years ago
[Suggestion] Optionally send no SNI for HTTPS alike connections (when using encrypted DNS)
Categories
(Core :: Networking, enhancement)
Core
Networking
Tracking
()
RESOLVED
INVALID
People
(Reporter: masterquestionable, Unassigned)
References
Details
See [ https://github.com/curl/curl/issues/9160#issuecomment-1189604667 ].
Similar to the "HTTPS-Only Mode"'s implementation.
Note: "-k" in `curl` means skip certificate verification.
Reporter | ||
Updated•2 years ago
|
Summary: [Suggestion] Optionally send no SNI for HTTPS connections → [Suggestion] Optionally send no SNI for HTTPS connections (when using encrypted DNS)
Reporter | ||
Updated•2 years ago
|
Summary: [Suggestion] Optionally send no SNI for HTTPS connections (when using encrypted DNS) → [Suggestion] Optionally send no SNI for HTTPS alike connections (when using encrypted DNS)
Reporter | ||
Updated•2 years ago
|
Component: Preferences → Networking
Product: Firefox → Core
Comment 1•2 years ago
|
||
I don't think disabling SNI in certain situations would make things any better.
We are actively working on ECH support, which should improve the privacy situation there.
Status: UNCONFIRMED → RESOLVED
Closed: 2 years ago
Resolution: --- → INVALID
Reporter | ||
Comment 2•2 years ago
|
||
The reasoning has been given in the linked post (in particular [ https://github.com/curl/curl/issues/9160#issuecomment-1188602124 ]).
It appears helpful whatsoever.
You need to log in
before you can comment on or make changes to this bug.
Description
•