Security policy: exceptions are not crashes#1849
Open
encukou wants to merge 1 commit into
Open
Conversation
Documentation build overview
|
sethmlarson
approved these changes
Jun 30, 2026
StanFromIreland
approved these changes
Jun 30, 2026
StanFromIreland
left a comment
StanFromIreland
left a comment
Member
There was a problem hiding this comment.
LGTM, however, can we keep it under availability vulnerabilities?
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This is mostly word nitpicking, but: by "crash" we generally mean a segfault or similar; see
Lib/test/crashersfor example.Unhandled exceptions are not crashes, and are not a security concern.
However, since segfaults usually can be weaponized, a “crash resulting from unhandled exception” would be a PSRT issue.