Skip to content

Create a Security Policy #529

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

Closed
diogoteles08 opened this issue Jul 17, 2023 · 0 comments · Fixed by #530
Closed

Create a Security Policy #529

diogoteles08 opened this issue Jul 17, 2023 · 0 comments · Fixed by #530

Comments

@diogoteles08
Copy link
Contributor

Hi! I'm Diogo and I'm back (see #523) hoping to offer a bit more help with security enhancements.

This time I'm here to suggest that you expose a way that users can report eventual vulnerabilities in a safe and efficient way. This is usually done through a Security Policy, which is a GitHub standard document (SECURITY.md) added on the root of the repo and that will be visible to the users in the "Security Tab", as you can see bellow:

image

I see that this was already briefly mentioned on the issue #424, which has spotted a vulnerability. Having this Security Policy would have made it easier and safer to repor that vulnerability. It is also a recommendation from Github itself, and from Scorecard (being a security measure of medium priority).

Aiming to make this change easier, I'll take the liberty and submit a suggestion of a Security Policy as a PR. Please feel free to edit it directly or ask me for editions until it is in compliance with how python-ldap would best handle vulnerability reports.

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

Successfully merging a pull request may close this issue.

1 participant