Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

KeePassXC 2.3.0 released

keepassxc.org

Post reply on HN
Print view View original

81–90 of 105 posts

Re: KeePassXC 2.3.0 released

#81

Post by vetinari »

scrollaway wrote: post #78
vetinari wrote: post #32

Earlier quoted context omitted.

I just switched from MacPass to KeePassXC for the reason mentioned in release notes: it obsoletes the HTTP Connector and uses another mechanism. MacPass keeps using HTTP, and it is uknown, when it will do the same switch. Given that I use multiple computers, and the extensions are synced, I want to use the same mechanism on all of them.

Do you know the details of the differences between the old and the new mechanisms? All I see is a migration is required, but I used neither.

The new mechanism uses Native Messaging[0], with the native application being keepassxc-proxy. The old one used HTTP, with the server (the password manager) listening on localhost.

[0] https://developer.mozilla.org/en-US/Add-ons/WebExtensions/Na...

Re: KeePassXC 2.3.0 released

#82

Post by teilo »

The thing that keeps me in 1Password is its Team Vault support. Nothing works quite so well for maintaining a shared password vault. If I didn't need that, I'd drop 1Password for KeePass in a heartbeat.

Re: KeePassXC 2.3.0 released

#83

Post by purerandomness »

therealmarv wrote: post #80
piracykills wrote: post #14

Earlier quoted context omitted.

Well, in my amateurish opinion - there was nothing wrong with the existing AES encryption implementation. But they also had a key derivation function based on running many iterations of AES, which was weird and non-standard, I mean it seemed like it would work, but it's not proven in the cryptographic community. Now they've switched to Argon2 which is a very well reviewed KDF and I have a lot more faith in that. Code…

How can I switch to the new system and new format easily?

Just save the database file in the new format.

Re: KeePassXC 2.3.0 released

#84

Post by agildehaus »

guessmyname wrote: post #17
piracykills wrote: post #7

> Add support for KDBX 4.0, Argon2 and ChaCha20 [#148, #1179, #1230, #1494] I can finally give this a shot without having to use the weird custom AES-based KDF Keepass used to use. Awesome. Congrats on the release.

Last week I started reverse engineering the KDBX 3.1 file format (for fun) . Does anyone knows where is the specification for KDBX 4.0? EDIT: Found it — https://github.com/keepassxreboot/keepassxc-specs

I don't believe the XML format has changed at all. Just the key derivation, stream cipher, and some changes to the binary header.

Re: KeePassXC 2.3.0 released

#85

Post by kayman »

076ae80a-3c97-4 wrote: post #18

I highly recommend https://keeweb.info/ if you're looking for an attractive, easy to use, cross-platform and Open Source solution. I've been using it on Windows and MacOS for years without any major issues. It's by far the best looking front-end for keepass databases I've seen.

+1 for keeweb. It's central to my password management strategy now. Can't recommend it enough.

I've tried the offline versions, but I find myself often on the go - without my laptop.

The tools for mobile don't seem to support updates - read only. Keeweb does both.

Re: KeePassXC 2.3.0 released

#87

Post by adrianmonk »

paulryanrogers wrote: post #15
nathan_long wrote: post #2

Anybody use this along with a non-tech significant other? How does it compare to commercial password managers in terms of usability?

Usability is too low, unapproachable for non techies. Even my somewhat technical spouse found it unusable after a few months. It could be better with good browser plugins, but then you have the same security tradeoffs as more polished services like Bitwarden or LastPass.

> with good browser plugins

This latest version KeePassXC has a whole new browser plugin:

https://github.com/keepassxreboot/keepassxc-browser

So maybe it has reached that point now? Not that I've tried it, but it's at least promising that they've been working on it.

Re: KeePassXC 2.3.0 released

#88

Post by varjolintu »

zie wrote: post #55
drdaeman wrote: post #50

Earlier quoted context omitted.

The linked article is very light on details to be called a comparison. Let me try to make it a little bit more detailed. ==================== Bitwarden: - Is essentially a service (with FLOSS client software and FLOSS server code). - Quite polished browser integration (to the extent browsers allow it). - Third party server holding the encrypted data. Proprietary (in a "completely unique, not compatible with anything…

I don't see anything wrong, but will add: Bitwarden has a desktop app(electron .. sigh but is cross-platform) and has integrations with all the major browsers (Safari, Firefox, Chrome, IE) Bitwarden also has Mobile support (iOS, Android & UWP). KeepassXC only does Chrome(and family) and Firefox I believe. Running your own bitwarden server is not difficult, and there are 3 implementations that I know about: The origin…

FYI: the new browser extension KeePassXC-Browser relies on native messaging which is not supported by Safari. IE/Edge support could be done in the future.

Re: KeePassXC 2.3.0 released

#89

Post by zaarn »

TacticalMalice wrote: post #76
ff_ wrote: post #64

The best UX improvement in this release (IMHO) is pretty buried in the changelog, and I don't see it mentioned here: no more lock files! If you use Keepass on something like Dropbox it's a blessing.

The mentioned issue has the following statement which makes me wonder whether concurrent use on sync services is supported atm: > I was going to add tests for "concurrent" access of the same file in phase 2 of these changes. Phase 2 is refactoring the saving process entirely to make it asynchronous and robust to file sync services.

From my experience, it already works somewhat. Atleast, whenever I overwrote the file in Nextcloud and my desktop pulled the update, it would merge the changes automatically.

Re: KeePassXC 2.3.0 released

#90

Post by zaarn »

therealmarv wrote: post #80
piracykills wrote: post #14

Earlier quoted context omitted.

Well, in my amateurish opinion - there was nothing wrong with the existing AES encryption implementation. But they also had a key derivation function based on running many iterations of AES, which was weird and non-standard, I mean it seemed like it would work, but it's not proven in the cryptographic community. Now they've switched to Argon2 which is a very well reviewed KDF and I have a lot more faith in that. Code…

How can I switch to the new system and new format easily?

In KPXC, simply open the database settings, switch into the security window and select Encryption method and KDF. Then save your database. Done.
Post reply on HN