Problem with AES and Salsa is that salting is required for smaller-sized password and are not considered a "hashing" algorithm; those two are block ciphers, as I recall.
No, MATSO is not open source but with an enterprise license, you can negotiate for the source code.
AES and Twofish are both block ciphers. Neither are hasing algorithms, and you'll need a PBKDF or some other construction to derive a key for either, no?
Salsa is a stream cipher.
Right. thanks for the update. My note should have been consulted as you being correct. Hate my memory nowadays. Need to consult some more notes before speaking.
"AES-KDF in KeePass is only CPU hard, while Argon2 is both CPU and RAM hard. This means that AES-KDF is victim to GPUs and ASICs for fast password cracking. The memory requirements in Argon2 make GPUs and ASICs considerably more expensive to reach similar password cracking speeds."
https://www.reddit.com/r/KeePass/comments/k511o6/comment/ged...
I know that it's been one dumpster fire after the other in the past few years, but did they actually go as far? The most severe one I remember hearing of was a leak of (possibly insufficiently salted, depending on the age of the account) encrypted password vaults. Still, I'll never again consider or recommend them going forward.
> In pwsafe, unbroken TwoFish algorithm is still being used instead of currently safer Argon2i
This is actually a negative point for it, in my view. AES is just as unbroken, yet has received considerably more scrutiny over the years.
The only place were non-AES symmetric algorithms still make sense these days is platforms where hardware acceleration is not available (e.g. djb's Salsa/Chacha), and even there only for high-throughput applications, which a password safe decidedly isn't.
> The recommended client-wise of PasswordSafe is still Netwrix (formerly MATESO of Germany)
I've never heard of them. Is it open source or at least properly audited?