3 ms·
I still use KeePassX and have no issues with it so no reason to move to XC. I do value an actively maintained project, but I also value stability - and particul
by jl6 5y ago
I still use KeePassX and have no issues with it so no reason to move to XC. I do value an actively maintained project, but I also value stability - and particularly for a security-sensitive application, I quite like the fact that it hasn’t been updated in years (I’m not saying I assume all the bugs have been fixed, just that there is less churn in which bugs could hide). How should I evaluate the respective projects from the perspective of security, and the level of trust I should be placing in the developers?
- k8sToGo 5y ago>and particularly for a security-sensitive application, I quite like the fact that it hasn’t been updated in years I feel like this is an oxymoron. At least security updates should be something to look forward to, no?
- jl6 5y agoI welcome updates that fix security vulnerabilities, but I view feature updates as a potential vector for introducing security vulnerabilities. The difficulty is telling the difference between projects that rarely update because there aren’t any vulns, and projects that rarely update because they don’t care.
- phoerious 5y agoKeePassX has literally been abandoned, so you will not get updates of any kind: https://www.keepassx.org/index.html%3Fp=636.html https://www.keepassx.org/index.html%3Fp=636.html