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 ncoghlan
Recipients acucci, benjamin.peterson, brett.cannon, georg.brandl, ncoghlan, python-dev, serhiy.storchaka, sirkonst, yselivanov, ztane
Date 2016-03-05.17:21:33
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
And as some additional background as to why segmentation faults provoked by Python code aren't currently considered a security bug: since CPython doesn't include a security sandbox, we're already relying entirely on the OS to provide process isolation.

That OS level security boundary isn't affected by whether the code is running "normally", or in a modified state following a deliberately triggered segmentation fault.
Date User Action Args
2016-03-05 17:21:34ncoghlansetrecipients: + ncoghlan, brett.cannon, georg.brandl, benjamin.peterson, python-dev, serhiy.storchaka, yselivanov, ztane, acucci, sirkonst
2016-03-05 17:21:34ncoghlansetmessageid: <>
2016-03-05 17:21:34ncoghlanlinkissue25973 messages
2016-03-05 17:21:33ncoghlancreate