Skip to content

Commit 1951e20

Browse files
suriyaafjl
andauthored
SECURITY.md: link to release page (#22067)
Add links to go-ethereum's GitHub release page. Co-authored-by: Felix Lange <[email protected]>
1 parent 5c2a7ce commit 1951e20

File tree

1 file changed

+4
-6
lines changed

1 file changed

+4
-6
lines changed

SECURITY.md

Lines changed: 4 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -2,31 +2,29 @@
22

33
## Supported Versions
44

5-
Please see Releases. We recommend to use the most recent released version.
5+
Please see [Releases](https://github.com/ethereum/go-ethereum/releases). We recommend using the [most recently released version](https://github.com/ethereum/go-ethereum/releases/latest).
66

77
## Audit reports
88

99
Audit reports are published in the `docs` folder: https://github.com/ethereum/go-ethereum/tree/master/docs/audits
1010

11-
1211
| Scope | Date | Report Link |
1312
| ------- | ------- | ----------- |
1413
| `geth` | 20170425 | [pdf](https://github.com/ethereum/go-ethereum/blob/master/docs/audits/2017-04-25_Geth-audit_Truesec.pdf) |
1514
| `clef` | 20180914 | [pdf](https://github.com/ethereum/go-ethereum/blob/master/docs/audits/2018-09-14_Clef-audit_NCC.pdf) |
1615

17-
18-
1916
## Reporting a Vulnerability
2017

2118
**Please do not file a public ticket** mentioning the vulnerability.
2219

23-
To find out how to disclose a vulnerability in Ethereum visit [https://bounty.ethereum.org](https://bounty.ethereum.org) or email [email protected].
20+
To find out how to disclose a vulnerability in Ethereum visit [https://bounty.ethereum.org](https://bounty.ethereum.org) or email [email protected]. Please read the [disclosure page](https://github.com/ethereum/go-ethereum/security/advisories?state=published) for more information about publically disclosed security vulnerabilities.
21+
22+
Use the built-in `geth version-check` feature to check whether the software is affected by any known vulnerability. This command will fetch the latest [`vulnerabilities.json`](https://geth.ethereum.org/docs/vulnerabilities/vulnerabilities.json) file which contains known security vulnerabilities concerning `geth`, and cross-check the data against its own version number.
2423

2524
The following key may be used to communicate sensitive information to developers.
2625

2726
Fingerprint: `AE96 ED96 9E47 9B00 84F3 E17F E88D 3334 FA5F 6A0A`
2827

29-
3028
```
3129
-----BEGIN PGP PUBLIC KEY BLOCK-----
3230
Version: GnuPG v1

0 commit comments

Comments
 (0)