-
Notifications
You must be signed in to change notification settings - Fork 10.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Create Security Policy #6354
Create Security Policy #6354
Conversation
Signed-off-by: Joyce <joycebrum@google.com>
SECURITY.md
Outdated
|
||
## Reporting a Vulnerability | ||
|
||
Beware that none of the topics under [Using LLaMA C++ Securely](#using-LLaMA-C++-securely) are considered vulnerabilities of LLaMA C++. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The link should probably be to #using-llama-c-securely
instead, as it is it doesn't work in the preview.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yeah, just tested it and #using-llama-c-securely works. Fixed, thanks.
SECURITY.md
Outdated
@@ -0,0 +1,67 @@ | |||
# Security Policy | |||
|
|||
- [**Using LLaMA C++ Securely**](#using-LLaMA-C++-securely) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Same here.
Signed-off-by: Joyce <joycebrum@google.com>
Signed-off-by: Joyce <joycebrum@google.com>
* Create SECURITY.md Signed-off-by: Joyce <joycebrum@google.com> * Fix: link on SECURITY.md Signed-off-by: Joyce <joycebrum@google.com> * Fix: link on SECURITY.md Signed-off-by: Joyce <joycebrum@google.com> * minor * fix * fix --------- Signed-off-by: Joyce <joycebrum@google.com> Co-authored-by: Georgi Gerganov <ggerganov@gmail.com>
Closes #6353
I've created the following SECURITY.md file (preview) considering the report vulnerability through security advisory, which is a new GitHub feature.
If you're interested in GitHub's feature, it must be activated for the repository:
If you rather not enable it, there is also the possibility to receive the vulnerability report through an email. In this case just let me know what would be the email and I'll submit the change.
Besides that, feel free to edit or suggest any changes to this document.
Thanks!