The less it does, the fewer ways it can break or be broken. The attack surface is tiny compared to, say, LastPass.
You choose your own sync solution, unlike LastPass/the like.
What's the new standard for AES passes? Patch notes mention it but not the number.
This person should sell this...
HN discussion about it: https://news.ycombinator.com/item?id=13468261
Has any of that changed recently?
Debian is trying to get reproducible builds for their packages.
I don't know enough about iOS to say anything about that.
Perhaps there's some false assumption there that the "app store" will serve everyone a backdoored binary, instead of performing almost undetectable targeted attacks.
- Printable Emergency Sheet
- a function to search for similar passwords
The same parameters input into two online SSSS generators: 3 parts( 2 reqd), secret=hackernews yield different parts.
I want to make it easy to recover. Using the same tool to store the passwords and recover the keys simplifies the process.
"Having no source code repository (version control system) doesn't mean that KeePass isn't open source."
It's way below similarly aged articles with ~5x fewer points.
So .NET Core doesn't benefit from UWP UI library, but UWP typically benefits from .NET Core upgrades.
If keepass were a .net standard library, you could have different front-ends for various platforms. Making the front-end crossplatform is a good goal too. I'm sure you could use bindings to Qt or gtk. There's various native crossplatform front-ends in the works too. See my comments below.
Looks like Xamarin is building full cross-platform support via XAML
Avalonia seems like a straightforward reimplementation of WPF that is already usable.
DotVVM is working on electron support, and I work with it already. I like it.