121–130 of 131 posts
Preferably use KeePassXC. Why? -> https://keepassxc.org/docs/#faq-keepassx
Short answer: written in C++ instead of C# I also have used keepassxc for years now on mac/windows/linux/iphones
The real reason to use KeepassXC over Keepass is because it's much better! The UI is better in almost every way.
Earlier quoted context omitted.
Exactly. If you can self-host a password manager then surely you can self-host a Git repository as well and use that instead and avoid this: [0] [0] https://news.ycombinator.com/item?id=32735734
and get into merge hell when you forget to push and have passwords added on two different binary blobs? no thanks. I prefer using something that was meant to be a password server
If you can self-host a password manager, then in the case of GitHub [0] going down every month you can self-host your Git repositories yourself, especially if you have projects like wireguard [1] for example.
Earlier quoted context omitted.
I just use keepassxc and have a cron job that zips and encrypts the password vault and then uploads it to Amazon S3 once a day, simple and pretty much foolproof, probably costs me $0.12 a year for storage.
not foolproof for a non technical user you can improve fool proving by watching the db file for change and then uploading it you can further improve it by checking if the uploaded file is the one which was there when you did download it last and only then upload your changed version but yes, for many people that simple approach would be good enough by far I mean how often do you add new passwords?
Earlier quoted context omitted.
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.
At the end of the day engineers and programmers receive dollars for hours worked and can often be ambivalent about whether that is good or bad for customers because they no longer are valued by management as input to features and the future direction of the company.
I don't agree with that. At best, they should resist bad ideas, and at the very least, they shouldn't b!tch about them on HN when someone else does it.
Does anyone has a good self hosting sync scheme? Keepass is awesome... But hadn't managed the sync to work smoothly yet
Earlier quoted context omitted.
I imagine it might be obvious for most users and potential users of pass, and being in line with the unix philosophy, it might be by design, but still, since I didn't see it mentioned in the documentation, it's worth mentioning: By itself, Passwordstore will not encrypt file names or directory names (which by convention represent the names of the service/site you have an account with). That might not pose a problem i…
You may not need to encrypt file names. Those are website address and perhaps with usernames, and public information. It’s like suggesting to encrypt public keys.
Wouldn't that same argument suggest that that encrypted DNS queries should not be something one would want to use?
My point is - it's nothing like that, I'm sure that most people could think of at least one website at some point in their life where they'd want to keep the knowledge of them having an account with that website private.
Earlier quoted context omitted.
Plus I feel that once one has experienced the browser integration of 1Pass, BW, LastPass, etc it's hard to go back to manually filling credentials again. That and the seamless sync across devices. It's just too much to handle for non techie folk.
I'm willing to tolerate a little friction to setup syncing, but keepass has friction at almost every level. Their importer is powerful... but I had to manually configure it to import from lastpass. Just bake that in ffs. There is no "generate password" button on the main application screen despite that being the #2 use for a password manager behind autofilling. Instead the main screen has "find", "find entries" and "…
Would you explain what kind of a problem you see here (I mean: KeePass related)? AFAIK syncing two KeePass database instances is based on timestamps, so losing changes made on any two copies kept/used on different devices is simply impossible if you properly use KeePass (ie. do merge them with KeePass). Of course, if you want to have a real cloud-based password manager then KeePass (without any extension) isn't appropriate at all. But what's the purpose of comparing apples to oranges?
Earlier quoted context omitted.
I replied in a different comment that I landed on the community page. But I have to say, arguing that the downloads buttons on keepass are more friction than "get started" (I don't see a app store link) which takes me to the business offer and then the family offer where I have to register an account and provide payment details, is a bit of a stretch. And bitwarden is very similar. Sure I can search on the playstore,…
I think that's just the downside of 1Password/Bitwarden's business model. The best they can do is explain the core features on the splash page, as you'd need a valid account to actually use the app in the first place. KeePassXC is probably the closest to ideal. It could just use more info about what it does on the homepage, and change its name for better marketing. But the project states itself that their audience is…
Well, "the closest", but not ideal, unfortunately, what I realized when they decided to abandon support for windows7 forcing me to maintain the KeePass database in VMs by hand... :-(
I see nobody's mentioned TOTP support yet. 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…
Thank you very much for your remark! I always am in trouble when I have to dig through terrible KeePass "documentation" and never found a remark about it.