Comment 343 for bug 417757
Revision history for this message
|
|
#343 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
0e1f616
(Get the code!)
But the question remains, WHY did the behavior change? Originally, glibc DID use unique ports for the AAAA and A queries. From a "predictability" perspective, that is a more secure approach, no? Similar to how ISNs are now randomized in TCP.
It seems many people's problems would be solved by going back to the (arguably more secure) method of using distinct ports for the A and AAAA queries.