![]() ![]() For KeePassium, every major release first goes through a week of beta-testing by about 200 volunteers.To prevent this, KeePassium makes a backup copy of your database before rewriting it.This one I already addressed above: the app stays offline and this can be checked by the end user. I have to trust that it'll not steal all the data and shunt it over the net for nefarious purposes. Thanks for the clarifications you gave, I've no doubt that the Apple vetting process is strong enough to identify you as an actual person with developer program memberships and subscriptions and whatnot. If I've locked my KDB with a composite key (password + key file) will it work, or am I forced/limited to password only?.how reliable is it? Is there things I can do to the DB in the desktop app that will prevent it working on iOS?.Also, more fool me for not having good backups of cloud files if this did happen. If this was happening, then I'm sure it'd be in the app reviews, or someone here would pipe up and mention it. ![]() how stable is it? will it trash my file then make it sync? Always a worry with sync'd files and 3rd party apps.No different to trusting the desktop app to be honest. I have to trust that it'll not steal all the data and shunt it over the net for nefarious purposes.Perhaps some clarification on 'safe' is in order. How else can I vouch for KeePassium and make it more transparent? If it tried to leak your data, you could detect this in the data consumption stats. KeePassium needs about 12KB to load the in-app purchase options. If you use KeePassium on mobile internet connection, you can check apps' data consumption measured by the system (device settings → Mobile data → KeePassium).However, transparency was more important. Reddit knows I was reluctant to do this, because this was risky for the commercial side of the project. Deanonymized: KeePassium's author is an actual person with a name, and a paper trail proving such person exists.Other developers could possibly confirm that the published source code has no backdoors - but there is no way to prove that the app in App Store is actually based on the published source code without any "suprises".Īs a developer, I did everything I know to ensure transparency: But any claim would not carry any weight due to the obvious conflict of interest. The only person who has the necessary information to vouch for an app is its developer (well, me).
0 Comments
Leave a Reply. |