assets: add [email protected] GPG key

License: MIT
Signed-off-by: Lars Gierth <[email protected]>

README.md

@@ -47,7 +47,7 @@ Please put all issues regarding the Go IPFS _implementation_ in [this repo](http
 
 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!
 
-If you find a vulnerability that may affect live deployments -- for example, by exposing a remote execution exploit -- please send your report privately to [email protected]. Please DO NOT file a public issue.
+If you find a vulnerability that may affect live deployments -- for example, by exposing a remote execution exploit -- please send your report privately to [email protected]. Please DO NOT file a public issue. The GPG key for [email protected] is [4B9665FB 92636D17 7C7A86D3 50AAE8A9 59B13AF3](https://pgp.mit.edu/pks/lookup?op=get&search=0x50AAE8A959B13AF3).
 
 If the issue is a protocol weakness that cannot be immediately exploited or something not yet deployed, just discuss it openly.
 

assets/init-doc/security-notes

@@ -14,6 +14,10 @@ Please note the following:
   user provided data. But please point any problems out to us in a
   github issue, or email [email protected] privately.
 
+- [email protected] GPG key:
+  - 4B9665FB 92636D17 7C7A86D3 50AAE8A9 59B13AF3
+  - https://pgp.mit.edu/pks/lookup?op=get&search=0x50AAE8A959B13AF3
+
 - ipfs uses encryption for all communication, but it's NOT PROVEN SECURE
   YET!  It may be totally broken. For now, the code is included to make
   sure we benchmark our operations with encryption in mind. In the future,