3 ms·
In addition to not being (fully) open source, something that also should be mentioned is, that if u use the mobile apps it unfortunately still isn't "zero knowl
by tinodotim 10y ago
In addition to not being (fully) open source, something that also should be mentioned is, that if u use the mobile apps it unfortunately still isn't "zero knowledge" [0].
[0] https://spideroak.com/manual/spideroak-on-mobile https://spideroak.com/manual/spideroak-on-mobile
- danbruc 10y agoUntil recently, mobile platforms were not capable of doing the on-device encryption necessary for SpiderOak's Zero Knowledge implementation. Anyone any idea what the issue is or was? What would prevents you from doing PBKDF2, RSA and AES [1] on a mobile device? [1] https://spideroak.com/manual/zero-knowledge-explained https://spideroak.com/manual/zero-knowledge-explained
- rarrrrrr 10y agoIt's mostly that the desktop app is Python and C, and there wasn't a clear path to make that same code base run on mobile, so the mobile app is just a reader. However for Semaphor, our encrypted group chat and file sharing tool (akin to IRC, to Slack or HipChat) the internals are written in Go and it's the same code base on all platforms, including mobile. That source code is also published for security review. We plan to migrate SpiderOakONE to use that same stack so the mobile experience is the same as desktop.