3 ms·
A while back I asked HN if there was any way I could trust an iOS keepass client. The answer was no, on the basis that you have no way of auditing whether the o
by jl6 9y ago
A while back I asked HN if there was any way I could trust an iOS keepass client. The answer was no, on the basis that you have no way of auditing whether the open source code built what’s in the App Store. Nor is there a way of preventing a rogue keepass client app from accessing the internet and exfiltrating your database and password.
Has any of that changed recently?
- lost_name 9y agoWouldn't this be true for any open source application you don't compile from the source?
- starquake 9y agoThere's something called deterministic compilation: https://en.wikipedia.org/wiki/Deterministic_compilation https://en.wikipedia.org/wiki/Deterministic_compilation Debian is trying to get reproducible builds for their packages. I don't know enough about iOS to say anything about that.
- ryanlol 9y agoHow does that help if you aren't compiling?
- jjnoakes 9y agoBecause someone you trust can compile and verify that the source they audited matches the binary you got from the app store.
- ryanlol 9y agoSo how do you do this in practice? Do you just send some guy (that you trust!) hashes of all the files on your system and hope that he spots the backdoored binary soon enough? Perhaps there's some false assumption there that the "app store" will serve everyone a backdoored binary, instead of performing almost undetectable targeted attacks.
- Tharkun 9y agoWhat's stopping you from compiling the source on mac?