@dotancohen - The question is not "what version *forward* are Keepass v2
files (*.kdbx) supported" but instead "at which version did support
cease." The simple answer is that Keepass v2 files up to and through
version 3.1 are supported. Version 4 and beyond are not supported and
may never be.
You
Lester, I see that the kpcli homepage [1] now (March 2022) states:
> A command line interface (interactive shell) to work with KeePass 1.x
or 2.x database files.
From what version forward are Keepass v2 files (*.kdbx) supported?
I tried what I believe to be the latest kpcli version (3.6),
I see! Thank you very much!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1874161
Title:
kpcli is unable to open a kdbx file if the file is locked by both a
password and a key file
To manage
KeepassX version 0.4.4 and earlier use *.kdb (V1).
KeepassX version 2.0.0 and higher use *.kdbx (V2).
I do now know what your problem is, but you might want to try keepass2,
keepassxc, and/or read about "Version 4 of the KDBX file format is
unsupported" here:
I have a correction to my previous comment: Instead of asking, "Is this
behavior of Keepass new?" I want to convey, "Is this behavior of
KeePassX new?"
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
The file command shows that my file is a 2.x KDBX file.
I tried creating a new database file with KeePassX with the KDBX
extension. The file command shows the new database file is also a 2.x
KDBX file.
I also tried creating a database file with KeePassX with the KDB
extension. The file command
The file command can tell you if the file format is v1 or v2:
$ file test.kdb
test.kdb: Keepass password database 1.x KDB, 11 groups, 12 entries, AES, 6000
key transformation rounds
$ file test.kdbx
test.kdbx: Keepass password database 2.x KDBX
--
You received this bug notification because
Hello Lester,
Thank you for your guidance. I tried renaming the kdbx file to end with
a kdb extension instead. I then used kpcli to try opening the kdb file
with the same key file, but I still encountered the same error: Couldn't
load the file kpstuff2.kdb: The database key appears invalid or
I am the author of kpci.
KeePassX does not support Keepass v2 files (*.kdbx), only v1 files
(*.kdb).
I suspect that you created a v1 file named foo.kdbx, which kpcli will
assume (wrongly) is a v2 file due to the kdbx file extension, and fail
to open it. An easy test would be to copy your file to
