-
Notifications
You must be signed in to change notification settings - Fork 370
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
Add security guidelines #1329
Add security guidelines #1329
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Fine with me, once my inline comments are addressed.
Out of curiosity, what kind of security issues are we talking about here? |
add language corrections by @jougs Co-Authored-By: Jochen Martin Eppler <[email protected]>
I think many things can be considered security related bugs. Basically anything that raises concerns of the user or machine/network admins. Main point is to define a way of contacting the developers on a secure channel. If a user would find a way to do any mischief with the simulator, it wouldn't be a good idea to put that into normal issue tracking or onto the mailing list. This of course assumes (a) something like this is possible, however unlikely, and (b) that it is a person is not tying to be next years supervillain. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for accepting my suggestions. I think this is better than having nothing and we always address further changes in future PRs. I'm thus merging without waiting for more reviews.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@terhorstd Good work!
This file defines the NEST security infrastructure. As discussed in the NEST-Initative Board.
The information will be available also in the project's Security Advisories page on GitHib (see next to Wiki above)