3 ms·

I can never get keybase to address this article about them: "Keybase, we have a problem." https://freehuman.fr/posts/20238f40da8b01357816236af097d2ae https://f

• chupasaurus 8y ago
  A happy KB user, let's bring that article down: 1. A server runs KBFS which syncs data with the server. No one could stop you from disabling it on startup and running wherever you need it. 2. Any app running without AppArmour/SELinux or outside of network namespace could get your real address. Latter is relatively easy to set up, I'm running VPN by default and all the apps inside are running only in the namespace with VPN tunnel device. 3. Last time I checked I could make my own package. 4. I don't have time to check it atm. 5. Link for audit results is somewhere in the comments on this post. 6. Works with uBlock on. 7. Some paranoia rant without looking how KB works: it's push/pull mode, all messages are stored as files you could sync. 8. Based on previous points. 9. Each connection is under TLS. Plaintext messages could be read via RAM, and if someone could read it, KB would be the last problem. 10. You could make your own. 11. Fixed. #ls -l /keybase would show you the symlink KBFS_NOT_RUNNING to /dev/null, but shows correct directories under user running the app. 12. Hello GDPR. 13. Like everyone in the world does. 14. Bad outro.