Bon. On va faire un truc dingue : passer de keepassxc à protonpass. L'avantage? C'est online, plus de problème de conflit de base de donnée comme avec KeePass et syncthing. Et c'est inclu dans mon abo. Et y a les scan de vulnérabilité. Et y a les adresses mail temporaires intégrées. Et la complétion auto dans les navigateurs web.
Le seul problème : je DOIS garder KeePass dans un coin pour stocker les mots de passe @protonprivacy . Mais ça représente 2 entrées, sur les plus de 300 que j'ai.
@protonprivacy sure! I've already used it a little, with an old dump of my KeePass db. Browser integration is great. Just... surprised it never asks for any auth, though, even after a full browser restart. Might be a setting somewhere.
@protonprivacy during the import, my main keepass has about 10 or 15 directories. Those don't map in Pass (known, no directory support), but I'd expect to not have to select what vault to target for every single directory... ^^'
@protonprivacy so all set successfully. Just the mentioned "not that user-friendly" things, but otherwise, move was smooth. Enabling apps, completion and al on devices was simple enough, and it's just working.
Having more control via the android app would make the whole experience fare more enjoyable and easy. My wife is waiting, since she'll face the same issues with export vs import devices/os
@Daemon Thanks for sharing your thoughts Cédric! We'll make sure to forward the feedback to the team so we can have this in mind for future improvement.
@protonprivacy Sure :). So far, so good, I've used my keepass only once to unlock proton account on my work env - and since then, I rely on ProtonPass only (and work SSO backed by kerberos, but that's another story)
ONE thing though:
at work, we have 2FA in a "weird" way:
TOTP is appended to the password.
Meaning only 2 fields: username, password, and password would require actual password + TOTP.
Wondering if we could get something like a rule for entries to append TOTP during completion?
Add comment