You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: CONTRIBUTING.md
+4-2Lines changed: 4 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -7,12 +7,14 @@ All contributions to this project must adhere to the requirements of the [Develo
7
7
We require that all contributors sign-off on their commits. This certifies that the contribution is your original work, or you have rights to submit it under the same license, or a compatible license. Any contribution which contains commits that do not have the Signed-off-by trailer will not be accepted.
8
8
9
9
To sign off on a commit you must use the `--signoff` (or `-s`) option when committing your change:
10
-
```shell
10
+
11
+
```shell
11
12
git commit -s -m "feat: Add some feature."
12
13
```
13
14
14
15
This will append the following trailer to your commit message:
- We encourage you to use the following PGP key for secure email communication: [NVIDIA public PGP Key for communication](https://www.nvidia.com/en-us/security/pgp-key)
13
-
- Please include the following information:
14
-
- Product/Driver name and version/branch that contains the vulnerability
15
-
- Type of vulnerability (code execution, denial of service, buffer overflow, etc.)
16
-
- Instructions to reproduce the vulnerability
17
-
- Proof-of-concept or exploit code
18
-
- Potential impact of the vulnerability, including how an attacker could exploit the vulnerability
13
+
- We encourage you to use the following PGP key for secure email communication: [NVIDIA public PGP Key for communication](https://www.nvidia.com/en-us/security/pgp-key)
14
+
- Please include the following information:
15
+
- Product/Driver name and version/branch that contains the vulnerability
16
+
- Type of vulnerability (code execution, denial of service, buffer overflow, etc.)
17
+
- Instructions to reproduce the vulnerability
18
+
- Proof-of-concept or exploit code
19
+
- Potential impact of the vulnerability, including how an attacker could exploit the vulnerability
19
20
20
21
While NVIDIA currently does not have a bug bounty program, we do offer acknowledgement when an externally reported security issue is addressed under our coordinated vulnerability disclosure policy. Please visit our [Product Security Incident Response Team (PSIRT)](https://www.nvidia.com/en-us/security/psirt-policies/) policies page for more information.
0 commit comments