remove expired GPG key from README
Encourage initial bug reports to security@ to be unencrypted for faster triage
Will Scott committed
Feb 25, 2020 at 12:30 UTC
ca0ee36b8dde20d53a2892660689e7ab9a6f051d
1 file changed
+1
-1
README.md
+1
-1
@@ -52,7 +52,7 @@ Before opening an issue, consider using one of the following locations to ensure
52
53
The IPFS protocol and its implementations are still in heavy development. This means that there may be problems in our protocols, or there may be mistakes in our implementations. And -- though IPFS is not production-ready yet -- many people are already running nodes in their machines. So we take security vulnerabilities very seriously. If you discover a security issue, please bring it to our attention right away!
54
55
-If you find a vulnerability that may affect live deployments -- for example, by exposing a remote execution exploit -- please send your report privately to security@ipfs.io. Please DO NOT file a public issue. The GPG key for security@ipfs.io is [4B9665FB 92636D17 7C7A86D3 50AAE8A9 59B13AF3](https://pgp.mit.edu/pks/lookup?op=get&search=0x50AAE8A959B13AF3).
55
+If you find a vulnerability that may affect live deployments -- for example, by exposing a remote execution exploit -- please send your report privately to security@ipfs.io. Please DO NOT file a public issue.
56
57
If the issue is a protocol weakness that cannot be immediately exploited or something not yet deployed, just discuss it openly.
58