Create SECURITY.md #2513
Closed
Create SECURITY.md #2513
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Hi! You have not got a `SECURITY.md` file. A SECURITY file is used to give guidelines to developers who may find exploits which could be harmful to plugins, servers, or even local machines (Servers or Home Computers). This file gives a quick outline on what kinds of reports are allowed. Please feel free to edit this file until you are happy.
Vladislav-CS
requested changes
May 19, 2024
Co-authored-by: Vladislav Popovič <vladislavcs@proton.me>
Co-authored-by: Vladislav Popovič <vladislavcs@proton.me>
Vladislav-CS
approved these changes
May 19, 2024
|
Build CI errors are unrelated to PR and can be ignored. |
Misfiy
approved these changes
May 21, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hi!
You haven't got a
SECURITY.mdfile. A SECURITY file is used to give guidelines to developers who may find exploits which could be harmful to plugins, servers, or even local machines (Servers or Home Computers). This also applies to workflows, e.g. Logging unencrypted API keys which could provide an attacker unrestricted write access to the repository.While most issues can be made in the issues tab, security reports are made for exploits which shouldn't be shared while a fix is in production. Say: I could use an exploit reported to Issues to get server credentials and start a backdoor server. You can a bit more research before you make a decision, but this file is generally a good idea to have.
This file gives a quick outline on what kinds of reports are allowed.
Please feel free to edit this file until you are happy.