Validate ECH public names
Categories
(NSS :: Libraries, enhancement, P3)
Tracking
(Not tracked)
People
(Reporter: mt, Assigned: mt)
Details
Attachments
(2 files)
The spec has been updated to require that public_name is a series of LDH labels (according to RFC 1023 and RFC 1134 definitions) but the value cannot be an IPv4 address. This is annoying, but necessary. Otherwise, we could end up with different parts of the system not agreeing on whether a name represents a DNS name or an IP address.
The text is not in the version of the draft we support, but the additional validation is worth including ahead of the next draft.
In implementing this, I discovered that we leak on the server if multiple configurations are provided for the same socket, so that's getting fixed too.
Assignee | ||
Updated•3 years ago
|
Comment 2•3 years ago
|
||
There's a r+ patch which didn't land and no activity in this bug for 2 weeks.
:mt, could you have a look please?
For more information, please visit auto_nag documentation.
Assignee | ||
Comment 3•3 years ago
•
|
||
Just waiting on review, that's all. (Low priority.)
Assignee | ||
Comment 4•3 years ago
|
||
OK, that was silly, I was just waiting for the release to pass before landing this.
Assignee | ||
Comment 5•3 years ago
|
||
Assignee | ||
Comment 6•3 years ago
|
||
Description
•