Skip to content

Commit

Permalink
Update Security Policy (#196)
Browse files Browse the repository at this point in the history
Created SECURITY.md file because GitHub automatically uses it.

The text is mostly copied from "Security Policy" section of README.md with an exception added for vulnerabilities already known to the public (to encourage easier or anonymous reporting).

Update "Security Policy" section.  Link to SECURITY.md instead of providing details in the README.
  • Loading branch information
x448 authored Mar 20, 2020
1 parent 5dc3bbd commit bd88e42
Show file tree
Hide file tree
Showing 2 changed files with 9 additions and 2 deletions.
4 changes: 2 additions & 2 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -954,9 +954,9 @@ This project has adopted the [Contributor Covenant Code of Conduct](CODE_OF_COND
Please refer to [How to Contribute](CONTRIBUTING.md).

## Security Policy
Security fixes are provided for the latest released version.
Security fixes are provided for the latest released version of fxamacker/cbor.

To report security vulnerabilities, please email [[email protected]](mailto:[email protected]) and allow time for the problem to be resolved before reporting it to the public.
For the full text of the Security Policy, see [SECURITY.md](SECURITY.md).

## Disclaimers
Phrases like "no crashes", "doesn't crash", and "is secure" mean there are no known crash bugs in the latest version based on results of unit tests and coverage-guided fuzzing. They don't imply the software is 100% bug-free or 100% invulnerable to all known and unknown attacks.
Expand Down
7 changes: 7 additions & 0 deletions SECURITY.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,7 @@
# Security Policy

Security fixes are provided for the latest released version of fxamacker/cbor.

If the security vulnerability is already known to the public, then you can open an issue as a bug report.

To report security vulnerabilities not yet known to the public, please email [email protected] and allow time for the problem to be resolved before reporting it to the public.

0 comments on commit bd88e42

Please sign in to comment.