101–110 of 131 posts
What's a good, trustworthy KeepassXC iOS client w/ FaceID unlock?
Now using KeePassium Pro. Very happy. Does everything I need, uses the file API for opening files and integrates well.
I hate KeePass so much at work. But we still have to use it because our security leadership insist on it. It's not a bad tool for a home user with one PC but it's totally inadequate for an enterprise scenario. But they keep insisting it's safe because it's been audited and the encryption is strong. Sure but what's the point of encryption if you store the password in a text file in the same folder or in some cases in…
I hate KeePass so much at work. But we still have to use it because our security leadership insist on it. It's not a bad tool for a home user with one PC but it's totally inadequate for an enterprise scenario. But they keep insisting it's safe because it's been audited and the encryption is strong. Sure but what's the point of encryption if you store the password in a text file in the same folder or in some cases in…
How is KeepassDX? It's on F-Droid.
Since you're also using a keyfile to encrypt it, it doesn't matter if another party gets the db file and even your passphrase, since only a device that also has the physical keyfile can decrypt it.
I hate KeePass so much at work. But we still have to use it because our security leadership insist on it. It's not a bad tool for a home user with one PC but it's totally inadequate for an enterprise scenario. But they keep insisting it's safe because it's been audited and the encryption is strong. Sure but what's the point of encryption if you store the password in a text file in the same folder or in some cases in…
The kdbx format used by KeePass is an open standard, and can be used by a variety of password management applications. Perhaps another app using that format might be a better fit for you and your organisation?
But most of my concerns are centered around the fact that it's just files not centrally managed.
Earlier quoted context omitted.
I guess mono never happened...
"natively" was the key word
Earlier quoted context omitted.
Doesn't mean the companies the work for did so. Doesn't mean they agreed with their employers decision. Doesn't mean they don't complain about it when their company does it. Doesn't mean they don't raise complains internally with their employer. But what do you expect? They quitting their job about this, many can't afford it. They mentioning how bad their employer is too every time they complain about a different com…
At the end of the day, engineers/programmers are the ones who implement these changes. I find it unacceptable that lots of HNers get so high minded about these issues but then go on to contribute to the problem by working at for-profit companies. Nothing wrong with either one, just choose one.
Earlier quoted context omitted.
The kdbx format used by KeePass is an open standard, and can be used by a variety of password management applications. Perhaps another app using that format might be a better fit for you and your organisation?
No, our company doesn't allow any of the other apps because they have not been audited. Which also means we don't have a solution for Mac. But most of my concerns are centered around the fact that it's just files not centrally managed.
My stack is KeePassXC on computers, Keepass2android on mobile and Dropbox for syncing. A few months ago I realized that both of my clients showed a TOTP option. Went digging a little and realized that there was enough support that I felt completely comfortable jumping ship away from Google Authenticator.
Google Authenticator had been worryingly opaque to me until then - you scan a QR code and then somehow you get TOTP codes? - and having gone through a phone number change recently, I felt especially aware and uncomfortable about having 2FA for many important accounts tied to one fairly fragile, fairly mis-placeable electronic device (not to mention in an app controlled by Google).
Figuring out how to use TOTP on KeePass was the nudge I needed to read up on how TOTP works, and of course it was quite simple. And keeping TOTP secrets in a password manager seems like a not-terrible idea (with the one caveat - and it's not a small one, I know - of busting the "second factor"ness of 2FA by making it possible to generate a TOTP code from the same device that you're using to log in with).
I was especially impressed that KeePass knows about Steam's non-standard TOTP implementation and is able to generate Steam Authenticator codes. I will say that doing this requires some hairy steps! This was what put me on the right path: https://old.reddit.com/r/Bitwarden/comments/a67c1n/steam_aut... And I put a good ~200 words of notes stored in that particular KeePass entry to remind me how I did it in the future.