Skip to content

Commit 387d723

Browse files
committed
Merge dashpay#679: Add SECURITY.md
78c3836 Add SECURITY.md (Jonas Nick) Pull request description: Fixes dashpay#646 WIP because the [email protected] email address doesn't exist yet. But it seems like the right place for vulnerability reports. [email protected] would have the downside that it perhaps reaches more people than necessary. Ideally secp256k1-security would just forward to the three maintainers listed in SECURITY.md. @sipa @apoelstra is it okay to put you there? Fwiw I'm opting out for now because three people should be enough. @sipa do you know who to talk to about adding [email protected] and the specifics about how it would work? ACKs for top commit: real-or-random: ACK 78c3836 I looked at the diff and verified my fingerprint Tree-SHA512: 53a989615665cf8cf0c6a70d3bc2c4b71b68178cae40b2a7881aa9eba24732d126ba1e258a9fc127c69b47bb3025943097300cfcbbe18736cbf92ff4f3a901e0
2 parents 0db61d2 + 78c3836 commit 387d723

File tree

2 files changed

+20
-0
lines changed

2 files changed

+20
-0
lines changed

README.md

+5
Original file line numberDiff line numberDiff line change
@@ -71,3 +71,8 @@ Exhaustive tests
7171
With valgrind, you might need to increase the max stack size:
7272

7373
$ valgrind --max-stackframe=2500000 ./exhaustive_tests
74+
75+
Reporting a vulnerability
76+
------------
77+
78+
See [SECURITY.md](SECURITY.md)

SECURITY.md

+15
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,15 @@
1+
# Security Policy
2+
3+
## Reporting a Vulnerability
4+
5+
To report security issues send an email to [email protected] (not for support).
6+
7+
The following keys may be used to communicate sensitive information to developers:
8+
9+
| Name | Fingerprint |
10+
|------|-------------|
11+
| Pieter Wuille | 133E AC17 9436 F14A 5CF1 B794 860F EB80 4E66 9320 |
12+
| Andrew Poelstra | 699A 63EF C17A D3A9 A34C FFC0 7AD0 A91C 40BD 0091 |
13+
| Tim Ruffing | 09E0 3F87 1092 E40E 106E 902B 33BC 86AB 80FF 5516 |
14+
15+
You can import a key by running the following command with that individual’s fingerprint: `gpg --recv-keys "<fingerprint>"` Ensure that you put quotes around fingerprints containing spaces.

0 commit comments

Comments
 (0)