![]() Let’s start by saying that this password manager supports YubiKey to secure your database. Making this seamless would require autotyping the current TOTP token, which I'm not sure is possible either. KeePassXC is for people with extremely high demands of secure personal data management. KeePassXC’s two-factor authentication (2FA) is a little complicated. Currently, I can have KeepassXC autotype my personal authentication for the first layer, and then have my static pin prefix autotyped, but then I have to get the output of stoken and paste it, and then do another autotype for the final authentication layer. The KeePassXC website contains some basic documentation, a general (largely non-technical) FAQ, and a blog. We use RSA SecurID for external VPN and internal 2FA for accessing secure networks. This is a feature not natively supported in the original KeePass, although it can be achieved via a plugin. Select Show TOTP from the context menu, and see that the tokens it generates do not match the ones produced by the RSA app or stoken.Seconds per tokencode (as the Time step) With 2FA i can bear a simpler password since the one time token provide good additional security.I ran stoken show -seed and set up TOTP using:.It is a lightweight app that respects your privacy: offline-first, no ads, no analytics. sdtid file I got from our security manager into stoken and verified that it provides the same tokens as the RSA Windows app. KeePassium features a clean well-polished interface and makes KeePass easy to use. The only GUI change necessary would be adding a radio button for RSA SecurID like the Steam one, and a text input for an optional PIN. ![]() Integrate the stoken code into KeePassXC. doesn't cause an error) but it produces invalid tokens. Current BehaviorĬonfiguring TOTP with the settings of my RSA SecurID "works" (i.e. The modern RSA SecurID algorithm is not very different from TOTP. Setup TOTP allows using Steam and Default RFC 6238 token settings, and I would like to be able to use my RSA SecurID as well. ![]()
0 Comments
Leave a Reply. |