ping
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1846153
Title:
gpg generate-key fails
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnupg2/+bug/1846153/
[Expired for gnupg2 (Ubuntu) because there has been no activity for 60
days.]
** Changed in: gnupg2 (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1846153
Upon closer inspection of the ~/.gnupg folder it appears that at some
point a directory is created with the label private-keys-v1.d, the
generation process does not recreate the directory if its missing and
running the batch command returns a very un-useful "file not found"
error if the directory d
I've verified that adding %no-protection to the batch file does allow
the key generation to proceed past the error to completion but there are
other issues.
GPG generates the public key and exports to a file successfully. The
public keyfile contains data, but its untestable.
The private key is no
Does it work if you either set a passphrase in the batch file or use
%no-protection to indicate no passphrase?
https://www.gnupg.org/documentation/manuals/gnupg-devel/Unattended-GPG-
key-generation.html
Thanks
** Changed in: gnupg2 (Ubuntu)
Status: New => Incomplete
--
You received this
Additionally, the workaround that many people suggest for similar errors
(via google) as described at https://d.sb/2016/11/gpg-inappropriate-
ioctl-for-device-errors does not work.
The output with proposed changes from the above link:
#> gpg --generate-key --batch < temp.batch
gpg: Generating a s
