This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author vstinner
Recipients Joel Croteau, Julian, christian.heimes, docs@python, eric.smith, gc2, lukasz.langa, mgorny, miss-islington, ncoghlan, ned.deily, pablogsal, pmoody, serhiy.storchaka, steve.dower, vstinner
Date 2021-05-25.16:44:50
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1621961090.05.0.445946943812.issue36384@roundup.psfhosted.org>
In-reply-to
Content
George-Cristian Bîrzan: "The timeline there is wrong."

Fixed: https://python-security.readthedocs.io/vuln/ipaddress-ipv4-leading-zeros.html#timeline

The strange part is "2019-03-20 (-741 days): Python issue bpo-36384 reported by Joel Croteau".

The problem is that this issue was "reused" for two different things: the initial change and the vulnerability.

Maybe I can removed the reference to the bpo to remove it from the timeline (and put it in links).
History
Date User Action Args
2021-05-25 16:44:50vstinnersetrecipients: + vstinner, ncoghlan, eric.smith, christian.heimes, ned.deily, pmoody, docs@python, lukasz.langa, mgorny, Julian, serhiy.storchaka, steve.dower, pablogsal, miss-islington, Joel Croteau, gc2
2021-05-25 16:44:50vstinnersetmessageid: <1621961090.05.0.445946943812.issue36384@roundup.psfhosted.org>
2021-05-25 16:44:50vstinnerlinkissue36384 messages
2021-05-25 16:44:50vstinnercreate