I am getting the general error creating the first/new pair.
See Attached image.
Thank you for your help!
Hi,
you are saying that both Kleopatra and GPA do not allow you to create a key-pair?
Could you try on the command line?
gpg -v --quick-generate-keys SOME@EMAIL.ADDRESS
Yes that is what I am saying.
I will try the command and advise.
Thank you
The command seemed to have an extra hypen in it, as with the double hyphen it
gave an error, invalid option.
In removing the extra hyphen, it states it’s NOT able to open the email address
I provided.
Was there any additional formatting needed around the email address?
The double hyphen is correct but the option name was mistyped its: --quick-generate-key and not --quick-generate-keys
so the command you should try is:
gpg -v --quick-generate-key SOME@EMAIL.ADDRESS
Thank you for your last response!
Seems that helped in seeing what the issue was.
Appears as if the TurstDB was Corrupted? (not sure how on a new/clean install)
Please see the initial output after issuing the updated command:
(modified for privacy)
gpg: pinentry launched (10600 qt 1.1.0 - - -)
gpg: writing self signature
gpg: RSA/SHA256 signature from: “SSSSSSSSSSSSSSSSSSS [?]”
We need to generate a lot of random bytes. It is a good idea to perform
some other action (type on the keyboard, move the mouse, utilize the
disks) during the prime generation; this gives the random number
generator a better chance to gain enough entropy.
gpg: writing key binding signature
gpg: RSA/SHA256 signature from: “SSSSSSSSSSSSSSSSS [?]”
gpg: writing public key to ‘/user path/AppData/Roaming/gnupg/pubring.gpg’
gpg: using pgp trust model
gpg: lookup_hashtable failed: Unknown system error
gpg: trustdb: searching trust record failed: Unknown system error
gpg: Error: The trustdb is corrupted.
gpg: You may try to re-create the trustdb using the commands:
gpg: cd \userpath\AppData\Roaming\gnupg
gpg: gpg --export-ownertrust > otrust.tmp
gpg: del trustdb.gpg
gpg: gpg --import-ownertrust < otrust.tmp
gpg: If that does not work, please consult the manual
I did carry out those instructions, and it did work!
Modified output below (for privacy):
We need to generate a lot of random bytes. It is a good idea to perform
some other action (type on the keyboard, move the mouse, utilize the
disks) during the prime generation; this gives the random number
generator a better chance to gain enough entropy.
gpg: pinentry launched (572 qt 1.1.0 - - -)
gpg: writing self signature
gpg: RSA/SHA256 signature from: “TTTTTTTTTTTTTTTTTTTT [?]”
We need to generate a lot of random bytes. It is a good idea to perform
some other action (type on the keyboard, move the mouse, utilize the
disks) during the prime generation; this gives the random number
generator a better chance to gain enough entropy.
gpg: writing key binding signature
gpg: RSA/SHA256 signature from: “VVVVVVVVVVVVVVVVV [?]”
gpg: writing public key to ‘/userpath/AppData/Roaming/gnupg/pubring.gpg’
gpg: using pgp trust model
gpg: key SSSSSSSSSSSSSSSS marked as ultimately trusted
gpg: directory ‘userpath/AppData/Roaming/gnupg/openpgp-revocs.d’ created
gpg: writing to ‘userpath//AppData/Roaming/gnupg/openpgp-revocs.ZZZZZZZZZZZZZZZZZZZZZZZZZZZZ.rev’
gpg: RSA/SHA256 signature from: “XXXXXXXXXXXXXXX email-address-here”
gpg: revocation certificate stored as ‘User Path/AppData/Roaming/gnupg/open
pgp-revocs.d\YYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYY.rev’
public and secret key created and signed.
pub rsa2048 2018-01-12 [SC] [expires: 2020-01-12]
wwwwwwwwwwwwwwwwwwwwwwwwwwwww
uid email-address-here
sub rsa2048 2018-01-12 [E]
Of course the question now is, can this be fixed in the GUI?
If I can get WinPgp Working, i’d like to deploy it on other systems as well, and
I’d like to donate in that case!
I will continue testing WinPgp now that the key is established, and advise!
Additionally, after running the DB Repair commands and generating the key,
upon opening Kleopatra, there are NOW a number of keys listed and their
status is ‘not certified’ and they seem to be ALl of the failed attempts over
numerous days.
None of these keys were listed previously, so there had to be some sort of
bug involved, after the initial install, and attempting to generate the first key pair
until the repair was performed.
Hope that helps.
And one more thing, all of the previous attempts did not have a ‘valid until’ date,
except for the first time I ran the manual command today, when it responded with
the corrupted DB message, however that was still listed as ‘not certified’
The 2nd attempt is what lead to a successful key being generated with a ‘valid until’ date
and being ‘certified’.
Hope that also helps.
Hi,
a corrupted trustdb file for a fresh installation is strange.
So we need to find the difference to the many working installations.
Could there be some permission, space, or otherwise a problem with the drive?
What kind of windows version are we talking about?
Was there ever a different version of Gpg4win or GnuPG or a similiar tool, which might have brought gnupg with itself installed on the machine?
Best Regards,
Bernhard
This is Win 7 Pro 64.
Yes, it is very likely there was another Wingpg and/or other pgp software/tech on the computer previously, unfortunately, it was from too far back to remember, but it was ‘removed’ prior to attempting the latest verion(s).
Of course, I can’t tell you what was left behind from the previous uninstalls, so it likely some sort or prior version interference was to blame, and we wouldn’t have even known that w/o the manual commands being issued, and seeing the results for that.
So possibly a good suggestion is to see what can be done with the GUI to offer to execute such commands, in the event of a failed key generation and display the output?
Thank you again for ALL your attention and work, I am still needing to do some testing, and then deploying!