Message 350003 - Python tracker

➜

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	rschiron
Recipients	cstratak, gregory.p.smith, larry, martin.panter, miss-islington, orange, rschiron, serhiy.storchaka, vstinner, ware, xiang.zhang, xtreak
Date	2019-08-20.13:30:46
SpamBayes Score	-1.0
Marked as misclassified	Yes
Message-id	<1566307847.06.0.517487903449.issue30458@roundup.psfhosted.org>
In-reply-to

Content
Will the flaw outlined in https://bugs.python.org/issue30458#msg347282 be fixed in python itself? If so, I think a CVE for python should be requested to MITRE (I can request one, in that case). Moreover, does it make sense to create a new bug to track the new issue? This bug already references 3 CVEs and it would probably just create more confusion to reference a 4th. What do you think?

Will the flaw outlined in https://bugs.python.org/issue30458#msg347282 be fixed in python itself? If so, I think a CVE for python should be requested to MITRE (I can request one, in that case).

Moreover, does it make sense to create a new bug to track the new issue? This bug already references 3 CVEs and it would probably just create more confusion to reference a 4th. What do you think?

History
Date	User	Action	Args
2019-08-20 13:30:47	rschiron	set	recipients: + rschiron, gregory.p.smith, vstinner, larry, martin.panter, serhiy.storchaka, xiang.zhang, cstratak, orange, miss-islington, xtreak, ware
2019-08-20 13:30:47	rschiron	set	messageid: <1566307847.06.0.517487903449.issue30458@roundup.psfhosted.org>
2019-08-20 13:30:47	rschiron	link	issue30458 messages
2019-08-20 13:30:46	rschiron	create