-
-
Notifications
You must be signed in to change notification settings - Fork 32k
bpo-33433 Fix private address checking for IPv4 mapped IPv6. #26172
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I made some wording updates to the docstring and news entry.
@JamoBox: Status check is done, and it's a failure ❌ . |
@JamoBox: Status check is done, and it's a success ✅ . |
Thanks @JamoBox for the PR 🌮🎉.. I'm working now to backport this PR to: 3.10. |
GH-26189 is a backport of this pull request to the 3.10 branch. |
…H-26172) For IPv4 mapped IPv6 addresses, defer privacy check to the mapped IPv4 address. Solves bug where public mapped IPv4 addresses are considered private by the IPv6 check. Automerge-Triggered-By: GH:gpshead (cherry picked from commit 83f0f8d) Co-authored-by: Pete Wicken <[email protected]>
For IPv4 mapped IPv6 addresses, defer privacy check to the mapped IPv4 address. Solves bug where public mapped IPv4 addresses are considered private by the IPv6 check. Automerge-Triggered-By: GH:gpshead (cherry picked from commit 83f0f8d) Co-authored-by: Pete Wicken <[email protected]>
Thanks Gregory! |
For IPv4 mapped IPv6 addresses, defer privacy check to the mapped IPv4 address. Solves bug where public mapped IPv4 addresses are considered private by the IPv6 check.
https://bugs.python.org/issue33433
Automerge-Triggered-By: GH:gpshead