Hacker News Reader

The first thing I looked at is the security model page. It doesn't give much detail, other than saying "we use libsodium defaults". Ok...which defaults, and how are they used?

The mention of RSA is also a bit of a red flag. RSA is extremely out dated, what excuse is there for using it in new apps?

(Also: I try to avoid being overly critical of people's projects, but password managers are critical pieces of software.)

View on HN

RSA is less of a footgun than many elliptic curve alternatives (e.g. it usually doesn't suffer from catastrophic compromise in case of reusing entropy in the way that DSA and ECDSA do), though.

Curve25519 is safe in that regard, but isn't yet as ubiquitous, and even though it's quite well-researched at this point, you can't beat RSA in terms of public scrutiny.

If performance doesn't matter as much to you, I'd say RSA is still a valid choice.

Looks like the mention of RSA is outdated. Seems from the codebase like it's all libsodium (x25519 + XSalsa20Poly1305) now.

> We formerly used AES and RSA encryption, we prefer to use generic terms now that do not imply any one implementation. We defer to libsodium recommendations on algorithms

https://gitlab.com/passit/passit/-/wikis/security

Reply on news.ycombinator.com