| 1 | IPFS Alpha Security Notes |
| 2 | |
| 3 | We try hard to ensure our system is safe and robust, but all software |
| 4 | has bugs, especially new software. This distribution is meant to be an |
| 5 | alpha preview, don't use it for anything mission critical. |
| 6 | |
| 7 | Please note the following: |
| 8 | |
| 9 | - This is alpha software and has not been audited. It is our goal |
| 10 | to conduct a proper security audit once we close in on a 1.0 release. |
| 11 | |
| 12 | - ipfs is a networked program, and may have serious undiscovered |
| 13 | vulnerabilities. It is written in Go, and we do not execute any |
| 14 | user provided data. But please point any problems out to us in a |
| 15 | github issue, or email security@ipfs.io privately. |
| 16 | |
| 17 | - security@ipfs.io GPG key: |
| 18 | - 4B9665FB 92636D17 7C7A86D3 50AAE8A9 59B13AF3 |
| 19 | - https://pgp.mit.edu/pks/lookup?op=get&search=0x50AAE8A959B13AF3 |
| 20 | |
| 21 | - ipfs uses encryption for all communication, but it's NOT PROVEN SECURE |
| 22 | YET! It may be totally broken. For now, the code is included to make |
| 23 | sure we benchmark our operations with encryption in mind. In the future, |
| 24 | there will be an "unsafe" mode for high performance intranet apps. |
| 25 | If this is a blocking feature for you, please contact us. |