We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Originally posted by @cryptomilk in #1018 (comment)
For fuzzing and also security related fixes it is important to have the process documented. You can use: https://www.libssh.org/development/security-process/
Write down which versions you support and communicate that. Example: https://wiki.samba.org/index.php/Samba_Release_Planning
This way you can always point people to your processes. The smaller the team the less versions you should have in maintenance mode.
I hope that helps.
The text was updated successfully, but these errors were encountered:
Also get CVEs through the Red Hat Security team, they also assist if something is considered a security issue or not.
Sorry, something went wrong.
Done: #1122.
clanmills
No branches or pull requests
Originally posted by @cryptomilk in #1018 (comment)
For fuzzing and also security related fixes it is important to have the process documented. You can use: https://www.libssh.org/development/security-process/
Write down which versions you support and communicate that. Example: https://wiki.samba.org/index.php/Samba_Release_Planning
This way you can always point people to your processes. The smaller the team the less versions you should have in maintenance mode.
I hope that helps.
The text was updated successfully, but these errors were encountered: