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

Please create a SECURITY.md #269

Open
stevebeattie opened this issue Jul 29, 2022 · 5 comments · May be fixed by cifsd-team/ksmbd#588 or #298
Open

Please create a SECURITY.md #269

stevebeattie opened this issue Jul 29, 2022 · 5 comments · May be fixed by cifsd-team/ksmbd#588 or #298

Comments

@stevebeattie
Copy link

Hi!

Please create a SECURITY.md document or some other mechanism for describing how to submit security vulnerabilities for the project.

Both github and the Open Source Security Foundation have guidelines, templates, and best practice recommendations for vulnerability disclosure handling.

Thanks!

@namjaejeon
Copy link
Member

Hi:)

Could you please contribute it to ksmbd project ?

Thanks!

junland added a commit to junland/ksmbd that referenced this issue Mar 2, 2023
@junland junland linked a pull request Mar 2, 2023 that will close this issue
@stevebeattie
Copy link
Author

Hey, @namjaejeon, is the submission from @junland acceptable? If the information is correct, it seems reasonable to me.

@namjaejeon
Copy link
Member

Question : This is for ksmbd kernel module? or ksmbd-tools ?

@stevebeattie
Copy link
Author

For the userspace ksmbd-tools. For issues with the kernel module, I'd assume the correct approach would be to go through the linux kernel's security process (contacting [email protected]). That said, you may wish to clarify that in your SECURITY.md policy document, just so others are clear.

@namjaejeon
Copy link
Member

OK!

@junland junland linked a pull request Mar 22, 2023 that will close this issue
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.

2 participants