Without ls, show does not shows keys
kpcli has always had this behavior. It is an intentional design decision based upon the fact that the entry numbers are only associated with an ls. The show command also supports titles, and so there is no need (and it's somewhat nonsensical) to try to show via a number when no ls was ever performed. Moreover, the show command will show entries from the prior ls that was performed with no regard for where the user's cwd currently is. Again, this was an intentional design decision.
Without ls, show does not shows keys
That worked. Thanks.
Release 4.1.3
Very minor cleanups
Show protected tags (strings) and allow protecting tags
This feature was added in SVN commit r67 on the head of the trunk and will be in the next release. https://sourceforge.net/p/kpcli/code/67/
Adds string protection toggling, requested in SF FR #31
Splendid ! Thanks. Awaiting the protect tag feature
I fixed the KDBXv3 protected strings display bug reported here. It is part of this commit: https://sourceforge.net/p/kpcli/code/66/tree//trunk/kpcli-DEVELOPMENT.pl?diff=6570cda74363ae34c51814f1:65 Note that the bug.kdbx file that you sent did not have the otp string protected in the entry, but the attached file does, in one of the two entries, as shown in the screenshot.
Couple of bug fixes.
I managed to install File::KDBX and opened a KDBX 4.1 file that was created by KeePassVault, and the otp entry was redacted indeed. I opened my KDBX 3.0 file again, it still wasn't redacted. The stats says that File::KeePass was used for that file.
Database password: test Entry: Internet/Groogle I don't know if this matters: I don't have File::KDBX on my system
Database password: test
Because I am unable to replicate this problem, would you please create a small kdbx file that has one or more entries within it that exhibits the concerning behavior and upload it to a reply here? Thanks.
I just tried to protect the otp field of an entry using KeepassDroid, and open the file using kpcli 4.1.2, it still displayed the otp string without red on red
For a couple of entries, I added the otp string using an old version of kpcli (3.1 to 3.7, I don't recall). One entry was created by kpcli 4.1.2, I opened the database using KeepassDroid, and it showed that the otp string wasn't protected for all those entries, even the one created by kpcli 4.1.2
The screenshot from my prior reply was from a 3.x KDBX file and an entry that had its OTP added by KeePassXC. If that behaves the way that you expect, then I am not sure what issue you are running into. What version of kpcli are you using (run the vers command)? What software added the OTP strings to the kdbx file's entries? I understand the other request that you described (you've made two requests in one ticket). I am presently focused on understanding the OTP issue, which seems to not behave for...
That's not what happens with me. I am using a 3.x KDBX file, and I use the otp string (instead of 2FA-TOTP field in Notes) to put the otpauth:// url, and it is displayed without being redacted as in your screenshot. Also, I need to add some sensitive info in string fields, such as recovery codes, yet there is no way to protect such info using kpcli
That's not what happens with me. I am using a 3.x KDBX file, and I use the otp string (instead of 2FA-TOTP foeld in Notes) to put the otpauth:// url, and it is displayed without being redacted as in your screenshot. Also, I need to add some sensitive info in string fields, such as recovery codes, yet there is no way to protect such info using kpcli
Show protected tags (strings) and allow protecting tags
It seems that I am not understanding something in this. Unless -f is given to the show command, the otp string is hidden as red on red text, just like the password is, as seen in the attached image.
I was astonished that kpcli shows the otp strings (which contains secret info.) even though I didn't use -f flag for show command. When I opened the keepass database using another app (KeePassDroid), it showed that the otp string was indeed protected.
I was astonished that kpcli shows the otp strings even though I didn't use -f flag for show command
Show protected tags (strings) and allow protecting tags
wrong sha256sum for kpcli-4.1.1-README
Hi - What you found is an Arch Linux AUR packaging bug. The AUR packager has been made aware. https://aur.archlinux.org/packages/kpcli -- Lester
wrong sha256sum for kpcli-4.1.1-README
Hello Lester. Thank you very much! I appreciate your quick reaction (as always). One of multiple reasons why I'm a happy kpcli long term user... :)
How to preserve notes during edit
Fixed in version 4.1.2.
Thank you for reporting this, Vladimir. You discovered a legitimate bug in versions 4.1 and 4.1.1 that impacts the Notes field exactly as you described. I have found and fixed the problem and plan to release 4.1.2 soon with the fix. For now, you can use version 4.0 and hopefully brew will give you a smooth path to upgrade to release 4.1.2 when I release it. If you would like to fix your version of 4.1 yourself, this is the section of code to change, starting at line 4684 (remove the one - line and...
Release 4.1.2 to fix SF bug #56
How to preserve notes during edit
Thank you for reporting this, Vladimir. You discovered a legitimate bug in versions 4.1 and 4.1.1 that impacts the Notes field exactly as you described. I have found and fixed the problem and plan to release 4.1.2 soon with the fix. For now, you can use version 4.0 and hopefully brew will give you a smooth path to upgrade to release 4.1.2 when I release it. If you would like to fix your version of 4.1 yourself, this is the section of code to change, starting at line 4684 (remove the one - line and...
How to preserve notes during edit
Warning: Attempt to call undefined import method with arguments (":all") via package "File::KDBX::Key"
Fixed in version 4.1.1.
Commits related to version 4.1.1
Warning: Attempt to call undefined import method with arguments (":all") via package "File::KDBX::Key"
new action - non-interactive attach one file to entry
If you actually code this, please send a patch (unified diff) and/or a copy of your kpcli that you added it to and I will review and consider it.
Would you mind sharing and educating me on how you used "dependency walker" to determine that LIBXML2-2__.DLL was missing. Thanks.
Missing Windows DLL
Thank you for reporting this bug. You found a problem with my build process on windows that impacted both v4.0 and v4.1. I corrected that problem, recompiled both EXEs, and put the new files into the project's Files area. Those EXEs should work properly now.
new action - non-interactive attach one file to entry
Missing Windows DLL
Accented characters not being displayed
Proper utf8 support was added with version 4.1.
Version 4.1 release
Don't warn on commented out debugging lines
Minor fixes (most typos/spellings) in a few comments
Better handle invalid OTP Base32 secret strings
Fixed a utf8-related problem with the autosave command
Fixed a UTF-8 bug in cli_find that Tom reported
A few bug fixes and a little code cleanup
UTF-8 bug fixes from extensive interoperability testing
Small utf8 fix in get_recycle_group_uuid() for KDBX
Small fix for group listing in --no-utf8 and KDBX
Further UTF-8 improvements, mostly around KDBv1
UTF8 fixes after tests on Arch Linux and Ubuntu 20.04
Looks pretty good :) Thanks a lot Lester and let me know if there's anything you'd like me to test! patrick@thinkpad-l580:~/kpcli-test$ kpcli-DEVELOPMENT.pl --kdb Patrick\ KeePassXC\ -\ fr_CA.UTF-8.kdbx Provide the master password: ************************* KeePass CLI (kpcli-DEVELOPMENT) vDEVELOPMENT is ready for operation. Type 'help' for a description of available commands. Type 'help <command>' for details on individual commands. kpcli-DEVELOPMENT:/Racine> ls === Groups === Balançoire/ Français/...
Looks pretty good :) Thanks a lot Lester* and let me know if there's anything you'd like me to test! patrick@thinkpad-l580:~/kpcli-test$ kpcli-DEVELOPMENT.pl --kdb Patrick\ KeePassXC\ -\ fr_CA.UTF-8.kdbx Provide the master password: ************************* KeePass CLI (kpcli-DEVELOPMENT) vDEVELOPMENT is ready for operation. Type 'help' for a description of available commands. Type 'help <command>' for details on individual commands. kpcli-DEVELOPMENT:/Racine> ls === Groups === Balançoire/ Français/...
Looks pretty good :) patrick@thinkpad-l580:~/kpcli-test$ kpcli-DEVELOPMENT.pl --kdb Patrick\ KeePassXC\ -\ fr_CA.UTF-8.kdbx Provide the master password: ************************* KeePass CLI (kpcli-DEVELOPMENT) vDEVELOPMENT is ready for operation. Type 'help' for a description of available commands. Type 'help <command>' for details on individual commands. kpcli-DEVELOPMENT:/Racine> ls === Groups === Balançoire/ Français/ Koala/ Corbeille/ kpcli-DEVELOPMENT:/Racine> cd Koala/ kpcli-DEVELOPMENT:/Racine/Koala>...
Looks pretty good :) patrick@thinkpad-l580:~/kpcli-test$ kpcli-DEVELOPMENT.pl --kdb Patrick\ KeePassXC\ -\ fr_CA.UTF-8.kdbx Provide the master password: ************************* KeePass CLI (kpcli-DEVELOPMENT) vDEVELOPMENT is ready for operation. Type 'help' for a description of available commands. Type 'help <command>' for details on individual commands. kpcli-DEVELOPMENT:/Racine> ls === Groups === Balançoire/ Français/ Koala/ Corbeille/ kpcli-DEVELOPMENT:/Racine> cd Koala/ kpcli-DEVELOPMENT:/Racine/Koala>...
Looks pretty good :) patrick@thinkpad-l580:~/kpcli-test$ kpcli-DEVELOPMENT.pl --kdb Patrick\ KeePassXC\ -\ fr_CA.UTF-8.kdbx Provide the master password: ************************* KeePass CLI (kpcli-DEVELOPMENT) vDEVELOPMENT is ready for operation. Type 'help' for a description of available commands. Type 'help <command>' for details on individual commands. kpcli-DEVELOPMENT:/Racine> ls === Groups === Balançoire/ Français/ Koala/ Corbeille/ kpcli-DEVELOPMENT:/Racine> cd Koala/ kpcli-DEVELOPMENT:/Racine/Koala>...
Patrick - I just committed an update that I believe is getting very close to have fully working utf8 support. If you're using kpcli, please install this version locally and use it. Thanks. https://sourceforge.net/p/kpcli/code/HEAD/tree/trunk/kpcli-DEVELOPMENT.pl
More utf8 work. Well tested with KDB1, KBDX3, and KDBX4
More utf8 progress. KDBv1 and KDBXv4 seem pretty solid
Fixed utf8-related problems with KDBX3 files
Sound-trip a RAM-based DB save/load for mktestdb
Significantly more utf8 work completed
Apologies for not getting those directory paths just right, and thanks for that testing, Patrick. Your results seem to imply that I probably should stop treating the password field differently... I need to give that some thought, but it is obvious that what I am currently doing is probably not correct.
Hey no problem Lester! Take your time to think about it and let me know if you need anything.
Apologies for not getting those directory paths just right, and thanks for that testing, Patrick. Your results seem to imply that I probably should stop treating the password field differently... I need to give that some thought, but it is obvious that what I am currently doing it probably not correct.
I was able to test you Clipboard wl-clipboard support. I think there may have been a small mistake in your lib/Clipboard/lib/ reference but fortunately the error messages I got mentioned where the files were supposed to be. So they ended up at ~/perl5/lib/perl5/Clipboard/WaylandClipboard.pm and ~/perl5/lib/perl5/Clipboard.pm in order to make everything work. See the results in the attached screenshot.