You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When I start up cpm, it says
"error: encryption key KEY NAME EMAIL could not be be validated; not using it."
Then when I go to add keys with Ctrl-k, it allows me to enter the key, when I hit enter on the key it says: "edit encryption key", and when I hit enter again, it says: "The key you entered could not be validated." Then when I go to save with Ctrl-w, it says: "GpgMe encrypt error
Invalid value".
"Error encrypting the data.
could not encrypt database file."
I am on Debian GNU/Linux 10 (buster). cpm package 0.32-1.2+b1. I have had this problem for many years and on previous versions and cannot figure out how to get around it. cpm does not have this problem on Debian 8.11 (Jessie), cpm package 0.32-1.1.
Best,
Andrew
The text was updated successfully, but these errors were encountered:
Hi,
When I start up cpm, it says
"error: encryption key KEY NAME EMAIL could not be be validated; not using it."
Then when I go to add keys with Ctrl-k, it allows me to enter the key, when I hit enter on the key it says: "edit encryption key", and when I hit enter again, it says: "The key you entered could not be validated." Then when I go to save with Ctrl-w, it says: "GpgMe encrypt error
Invalid value".
"Error encrypting the data.
could not encrypt database file."
I built this github source code, and had the same problems. I also saw the related bug ( #58 ) but no amount of adding encryption keys with different names, or specifying the key in the .cpmrc as mentioned here: http://blog.larsstrand.no/2009/02/secure-password-management-using-cpm.html seems to resolve it.
I am on Debian GNU/Linux 10 (buster). cpm package 0.32-1.2+b1. I have had this problem for many years and on previous versions and cannot figure out how to get around it. cpm does not have this problem on Debian 8.11 (Jessie), cpm package 0.32-1.1.
Best,
Andrew
The text was updated successfully, but these errors were encountered: