Skip to content

Security Contribution

Ron Lauren Hombre edited this page Jan 19, 2024 · 1 revision

Security Contribution

Security is a major requirement for the KyberKotlin repository. As we are humans, it's inevitable that we will make mistakes that will result in unintended security risks. Thus, I implore everyone to review the code in the repository and contribute to making it safe and secure to use.

Supported Branches

KyberKotlin has two development and active branches. These are the "master" and "standard" branches. They work similarly but does it differently. Due to this differences, a security risk in one branch might not be applicable for the other. Please review which branches are impacted by the security risk.

Submitting a Security Report

When you find a security risk(vulnerability), you need to follow our standard procedure in order for it to be processed as quickly as possible.

Template

## TITLE
SHORT DESCRIPTION
### Branches:
* master
* standard
### Proof of Concept:
INSERT LINK TO IT OR INSERT A CODE SNIPPET. IF NOT APPLICABLE, EXPLAIN WHY OR PROVIDE RESOURCES.
### Affected Code:
* KyberMath.kt line 5

AT THE VERY BOTTOM, YOU CAN ADD ANYTHING YOU WANT.

Submit it here

We take Security Reports seriously. If you are not submitting actual security risks and spamming, then you may be banned from the KyberKotlin repository.

Submitting a Security Fix through a Pull Request

Fork the repository and submit your Security Fix through a Pull Request. Please keep your code concise and explain what it does. Otherwise, it will delay the merging of the Security Fix.

Add the security-fix label in order to alert us. More info.

Update Speed for Security Reports/Security Fixes

Critical

As soon as possible.

High

Next day.

Medium

Next Release.

Low

Next Release.