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 #122

Closed
JamieSlome opened this issue Jan 7, 2022 · 4 comments
Closed

Who to contact for security issues #122

JamieSlome opened this issue Jan 7, 2022 · 4 comments

Comments

@JamieSlome
Copy link

Hey there!

I belong to an open source security research community, and a member (@ranjit-git) 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)

@lquixada
Copy link
Owner

@JamieSlome thanks for taking the time to open this issue! A SECURITY.md file has been created.

@JamieSlome
Copy link
Author

@lquixada - thanks for creating the SECURITY.md 👍

We will get further details sent over to the elected e-mail address shortly. In the meantime, the report can be accessed directly here:
https://huntr.dev/bounties/ab55dfdd-2a60-437a-a832-e3efe3d264ac

It is private and only accessible to you @lquixada 👍

@lquixada
Copy link
Owner

thanks @JamieSlome ! will take a look!

@JamieSlome
Copy link
Author

@lquixada - great, on call if you need me for any support, plus @ranjit-git for any questions regarding the report 😃

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