-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Clean up some things. Notes are now on my notebook.
- Loading branch information
1 parent
c405e66
commit e616667
Showing
4 changed files
with
10 additions
and
103 deletions.
There are no files selected for viewing
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
This file was deleted.
Oops, something went wrong.
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
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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,7 +1,8 @@ | ||
# Security Policy | ||
## Supported Version | ||
* Only the rewritten Rust Version is supported! Earlier Go Versions of Cyrkensia are deprecated and there won't be any support. | ||
* Custom modified builds or nightly builds are not supported! Only issues related to untouched code on a stable build are dealt with. | ||
- Only the rewritten Rust Version is supported! Earlier Go Versions of Cyrkensia are deprecated and there won't be any support. | ||
- Custom modified builds or nightly builds are not supported! Only issues related to untouched code on a stable build are dealt with. | ||
- Note that also only the latest stable release is supported. I think this is very obvious. | ||
|
||
## Reporting a Vulnerability | ||
Vulnerabilities can be reported as usual via the Security Advisory, but also as a GitHub Issue. I don't expect any major CVEs. | ||
Vulnerabilities can be reported as usual via the Security Advisory, but also as a GitHub Issue. I don't expect any major CVEs. Though this policy might change in the future. |