Skip to content
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

Who to contact for security issues #275

Open
JamieSlome opened this issue Apr 19, 2022 · 2 comments
Open

Who to contact for security issues #275

JamieSlome opened this issue Apr 19, 2022 · 2 comments

Comments

@JamieSlome
Copy link

Hey there!

I belong to an open source security research community, and a member (@ycdxsb) has found an issue, but doesn’t know the best way to disclose it.

If not a hassle, might you kindly add a SECURITY.md file with an email, or another contact method? GitHub recommends this best practice to ensure security issues are responsibly disclosed, and it would serve as a simple instruction for security researchers in the future.

Thank you for your consideration, and I look forward to hearing from you!

(cc @huntr-helper)

@larskanis
Copy link
Member

I'll add a SECURITY.md file and keep this issue open until then. For the time being please contact me by email lars@greiz-reinsdorf.de and if you want encryption, use this PGP key: https://keyserver.ubuntu.com/pks/lookup?op=get&search=0xb5ff9149f95a59bfbcfdaf0543b526b8aae32ba7

@JamieSlome
Copy link
Author

@larskanis - thanks 👍

I will get an e-mail sent over to you now. Just for reference, the report can be found directly here:
https://huntr.dev/bounties/5a21711d-6dcf-4bb3-8ce0-002c07dd1da7/

It is private and only accessible to maintainers with repository write permissions.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants