Add SECURITY.md - #22
Merged
Merged
Conversation
This repo had no security policy, so a finder had no documented private channel and would reasonably have opened a public issue. yojimbo has had one; netcode, reliable and serialize had none. Follows yojimbo's reporting section, with the scope written for what this library actually does rather than copied. States plainly that it performs no encryption or authentication and normally sits under a layer that does -- and that this does NOT put memory safety out of scope, since a stream is only trustworthy if the layer above really verified it. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
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
1 participant
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 repo had no security policy, so a finder had no documented private channel and would reasonably have opened a public issue. yojimbo has had one; netcode, reliable and serialize had none — PRs for all three today.
Follows yojimbo's reporting section, with the scope written for what this library actually does rather than copied across.
States plainly that it performs no encryption or authentication and normally sits under a layer that does — and that this does not put memory safety out of scope, since a stream is only trustworthy if the layer above really verified it.