| Summary: | Force EDNS0 requests on | ||||||
|---|---|---|---|---|---|---|---|
| Product: | Portable OpenSSH | Reporter: | Adam Tkac <vonsch> | ||||
| Component: | ssh | Assignee: | Assigned to nobody <unassigned-bugs> | ||||
| Status: | CLOSED WONTFIX | ||||||
| Severity: | normal | CC: | djm | ||||
| Priority: | P2 | ||||||
| Version: | 5.2p1 | ||||||
| Hardware: | Other | ||||||
| OS: | Linux | ||||||
| Attachments: |
|
||||||
|
Description
Adam Tkac
2009-07-28 02:14:51 AEST
I think it is a bit risky to enable EDNS0 when it has not been administratively configured as the resolver may not be trustworthy. I'm not sure about this - it may in fact be harmful. If traffic between a non--DNSSEC-verifying stub resolver and its recursive verifying resolver is subject to attack (e.g. it is on a shared network), then automatically enabling DNSSEC may make it possible for an attacker to force acceptance of certain host keys. Won't implement this for the reasons described. Set all RESOLVED bugs to CLOSED with release of OpenSSH 7.1 |