peergos-arch-5min-v03.pdf

Transcript

1. ▪ ▪ ▪ ▪
2. ▪ ▪  Safelogin  Strong crypto, ideallypost- quantum  Hide filemetadata  Free of SSLCas  Free ofDNS
3. ▪ ▪  Safelogin  Strong crypto, ideallypost- quantum  Hide filemetadata  Free of SSLCas  Free ofDNS • Selfhostable • Selectively sharefiles • Hidecontacts • Pseudonymous
4. ▪ ▪  Safelogin  Strong crypto, ideallypost- quantum  Hide filemetadata  Free of SSLCas  Free ofDNS • Selfhostable • Selectively sharefiles • Hidecontacts • Pseudonymous • Webinterface • Log in from anydevice • Filesyncing • Publishfiles • Resilient • As convenient as Dropbox,Facebook
5. ▪ ▪
6. ▪ ▪
7. ▪ ▪ • Global file system • /username/yourfiles • Tree of symmetric keys (TweetNaCl) with cryptographic links between (Cryptree) • Location + Key = cryptographic access token or capability (CAP) • Explicitly don't use convergent encryption!
8. ▪ ▪
9. ▪ ▪ Chunk raw file
10. ▪ ▪ Chunk raw file Encrypt chunk
11. ▪ ▪ Chunk raw file Encrypt chunk Split
12. ▪ ▪ Chunk raw file Encrypt chunk Split Upload
13. ▪ ▪
14. ▪ ▪ ~1 second Only ever stored in RAM, never written to disk or transmitted
15. ▪ ▪
16. ▪ ▪ • Brute force is practically impossible with a good password • Random 14 character alpha-numeric password has ~ 2^84 ~ 10^25 possibilities • A GPU can calculate ~ 1M scrypt hashes/s (measured by litecoin users) • One GPU cracking a single user’s login would take 10^19 seconds or ~ 300 billion years • 300 million GPUs would take 1000 years • GPU purchase cost = 300 billion USD
17. ▪ ▪
18. ▪ ▪ • Web-interface – done • Use actual IPNS – to do • Tor integration – to do • Fuse client – done • Security audit – to do • Granting write access – not in UI yet • Private keystore of friends (TOFU) – done
19. ▪ ▪ • Sign up to hear when our alpha is ready (soon): https://peergos.org • Read our book: https://peergos.github.io/book • Try our demo at https://demo.peergos.net • Contribute https://github.com/peergos/peergos • Currently we are a team of 4 contributors
20. ▪ ▪