Closed
Bug 1649801
Opened 5 years ago
Closed 4 years ago
Properly handle no-fallback TRR providers
Categories
(Firefox :: Security, task, P2)
Firefox
Security
Tracking
()
RESOLVED
WORKSFORME
People
(Reporter: valentin, Unassigned)
References
(Blocks 2 open bugs)
Details
We may want to add TRR providers that provide filtering services (DNSSEC validation, parental controls, etc).
In order to do this we have to:
- See if the provider implements https://datatracker.ietf.org/doc/draft-ietf-dnsop-extended-error/
- if so implement bug 1525854
- If extended-errors can't be used, we will probably have to use mode3 in which case we have to:
- Figure out how to show this option in the UI
- Figure out how to handle resolver failures
Peter, does this sound reasonable?
|
Reporter | |
Updated•5 years ago
|
Flags: needinfo?(stpeter)
|
||
Comment 1•5 years ago
|
||
Valentin, can you set an appropriate priority & severity on this bug? Thanks.
Flags: needinfo?(valentin.gosu)
|
|
Reporter | |
Updated•5 years ago
|
Severity: -- → S3
Flags: needinfo?(valentin.gosu)
Priority: -- → P2
|
||
Updated•4 years ago
|
Flags: needinfo?(stpeter)
|
|
Reporter | |
Comment 2•4 years ago
|
||
Since bug 1525854 and bug 1667975 landed, we now have extended DNS error support.
In absence of known requirements from TRR providers regarding running in mode3, I think we can close this for now.
Status: NEW → RESOLVED
Closed: 4 years ago
Resolution: --- → WORKSFORME
You need to log in
before you can comment on or make changes to this bug.
Description
•