Re: gpg 2.1.19 fails to generate key pair
On Fri, 22 Sep 2017 20:48, g...@unixarea.de said: > Ok. I will update to the most recent version. Btw: libcrypt is 1.7.0. Please update to 1.7.9 - Libgcrypt is the most likely cause for a bus error. > Linux ubuntu-phablet 3.4.67 #1 SMP PREEMPT Mon Jun 6 12:04:40 UTC 2016 > b75400e armv7l armv7l armv7l GNU/Linux 1.7.2 has this NEWS entry - Fix bus errors on ARM for Poly1305, ChaCha20, AES, and SHA-512. AES is used by gpg-agent to protect your key. Shalom-Salam, Werner -- Die Gedanken sind frei. Ausnahmen regelt ein Bundesgesetz. pgp8fOSBCFwiV.pgp Description: PGP signature ___ Gnupg-users mailing list Gnupg-users@gnupg.org http://lists.gnupg.org/mailman/listinfo/gnupg-users
Re: gpg 2.1.19 fails to generate key pair
it works with: phablet@ubuntu-phablet-bq:~$ ./gpg2.sh --version gpg-agent[28499]: enabled debug flags: mpi crypto memory cache memstat hashing ipc gpg-agent: a gpg-agent is already running - not starting a new one gpg-agent: random usage: poolsize=600 mixed=0 polls=0/0 added=0/0 outmix=0 getlvl1=0/0 getlvl2=0/0 gpg-agent: secmem usage: 0/32768 bytes in 0 blocks gpg (GnuPG) 2.2.1 libgcrypt 1.8.1 ... phablet@ubuntu-phablet-bq:~$ ~/gpg2.sh --full-generate-key ... ┌──┐ │ Please re-enter this passphrase │ │ │ │ Passphrase: ***_ │ │ │ │ │ └──┘ 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: /home/phablet/.gnupg/trustdb.gpg: trustdb created gpg: key 3FECB79DDDA409E4 marked as ultimately trusted gpg: directory '/home/phablet/.gnupg/openpgp-revocs.d' created gpg: revocation certificate stored as '/home/phablet/.gnupg/openpgp-revocs.d/41E0B3688FDD76C9337ECD873FECB79DDDA409E4.rev' public and secret key created and signed. pub rsa2048 2017-09-22 [SC] 41E0B3688FDD76C9337ECD873FECB79DDDA409E4 uid Matthias Apitz (test) sub rsa2048 2017-09-22 [E] -- Matthias Apitz, ✉ g...@unixarea.de, ⌂ http://www.unixarea.de/ ☎ +49-176-38902045 Public GnuPG key: http://www.unixarea.de/key.pub ___ Gnupg-users mailing list Gnupg-users@gnupg.org http://lists.gnupg.org/mailman/listinfo/gnupg-users
Re: gpg 2.1.19 fails to generate key pair
El día viernes, septiembre 22, 2017 a las 08:19:14p. m. +0200, Werner Koch escribió: > On Fri, 22 Sep 2017 17:24, g...@unixarea.de said: > > > I instructed via gpg-agent.conf the gpg-agent to do a debug log which > > follows. The proc gpg-agent crashes with SIG_BUS. > > That is why you see and EOF error from gpg. > I can imagine. That's why I attached the log of the gpg-agent. > We did a few more release after 2.1.19, which was released on March 1. > Not all fixed bugs are noted in the NEWS and it is also possible that > the SIGBUS comes from Libgcrypt. (run gpg-agent --version to see the > version of Libgcrypt). > > Please first try to build with a recent version (2.2.1 is current but > 2.1.23 should be okay) and the latest version of the respective > Libgcrypt branch. That would be easier for us than to try to figure out > a bug we might have already fixed. Ok. I will update to the most recent version. Btw: libcrypt is 1.7.0. > What OS and which platform are you using? I assume it is a BSD (or > Plan-9 ;-). No, wrong guess in this case. It is: phablet@ubuntu-phablet-bq:~$ uname -a Linux ubuntu-phablet 3.4.67 #1 SMP PREEMPT Mon Jun 6 12:04:40 UTC 2016 b75400e armv7l armv7l armv7l GNU/Linux an Ubuntu based smartphone. matthias -- Matthias Apitz, ✉ g...@unixarea.de, ⌂ http://www.unixarea.de/ ☎ +49-176-38902045 Public GnuPG key: http://www.unixarea.de/key.pub signature.asc Description: PGP signature ___ Gnupg-users mailing list Gnupg-users@gnupg.org http://lists.gnupg.org/mailman/listinfo/gnupg-users
Re: gpg 2.1.19 fails to generate key pair
On Fri, 22 Sep 2017 17:24, g...@unixarea.de said: > I instructed via gpg-agent.conf the gpg-agent to do a debug log which > follows. The proc gpg-agent crashes with SIG_BUS. That is why you see and EOF error from gpg. We did a few more release after 2.1.19, which was released on March 1. Not all fixed bugs are noted in the NEWS and it is also possible that the SIGBUS comes from Libgcrypt. (run gpg-agent --version to see the version of Libgcrypt). Please first try to build with a recent version (2.2.1 is current but 2.1.23 should be okay) and the latest version of the respective Libgcrypt branch. That would be easier for us than to try to figure out a bug we might have already fixed. What OS and which platform are you using? I assume it is a BSD (or Plan-9 ;-). Salam-Shalom, Werner -- Die Gedanken sind frei. Ausnahmen regelt ein Bundesgesetz. pgprV9Rbe2SS6.pgp Description: PGP signature ___ Gnupg-users mailing list Gnupg-users@gnupg.org http://lists.gnupg.org/mailman/listinfo/gnupg-users
gpg 2.1.19 fails to generate key pair
Hello, I've compile gpg 2.1.19 and all the required shared libs from source. The cmd sequence: LD_LIBRARY_PATH=/home/phablet/myRoot/usr/local/lib export LD_LIBRARY_PATH PATH=/home/phablet/myRoot/usr/local/bin:$PATH export PATH GNUPGHOME=/home/phablet/.gnupg export GNUPGHOME /home/phablet/myRoot/usr/local/bin/gpg-agent --homedir /home/phablet/.gnupg \ --daemon \ --pinentry-program /home/phablet/myRoot/usr/bin/pinentry-curses /home/phablet/myRoot/usr/local/bin/gpg-connect-agent /bye /home/phablet/myRoot/usr/local/bin/gpg2 --full-generate-key fails at the end (after the dialog and asking the passphrase) with: gpg: signing failed: End of file gpg: make_keysig_packet failed: End of file Key generation failed: End of file I instructed via gpg-agent.conf the gpg-agent to do a debug log which follows. The proc gpg-agent crashes with SIG_BUS. Any help? matthias 2017-09-22 16:46:49 gpg-agent[15163] listening on socket '/run/user/32011/gnupg/S.gpg-agent' 2017-09-22 16:46:49 gpg-agent[15163] listening on socket '/run/user/32011/gnupg/S.gpg-agent.extra' 2017-09-22 16:46:49 gpg-agent[15163] listening on socket '/run/user/32011/gnupg/S.gpg-agent.browser' 2017-09-22 16:46:49 gpg-agent[15163] listening on socket '/run/user/32011/gnupg/S.gpg-agent.ssh' 2017-09-22 16:46:49 gpg-agent[15166] gpg-agent (GnuPG) 2.1.19 started 2017-09-22 16:46:49 gpg-agent[15166] DBG: chan_9 -> OK Pleased to meet you, process 15167 2017-09-22 16:46:49 gpg-agent[15166] DBG: chan_9 <- RESET 2017-09-22 16:46:49 gpg-agent[15166] DBG: chan_9 -> OK 2017-09-22 16:46:49 gpg-agent[15166] DBG: chan_9 <- OPTION ttyname=/dev/pts/58 2017-09-22 16:46:49 gpg-agent[15166] DBG: chan_9 -> OK 2017-09-22 16:46:49 gpg-agent[15166] DBG: chan_9 <- OPTION ttytype=linux 2017-09-22 16:46:49 gpg-agent[15166] DBG: chan_9 -> OK 2017-09-22 16:46:49 gpg-agent[15166] DBG: chan_9 <- OPTION putenv=DBUS_SESSION_BUS_ADDRESS=unix:abstract=/tmp/dbus-Y5hTZhXCoe 2017-09-22 16:46:49 gpg-agent[15166] DBG: chan_9 -> OK 2017-09-22 16:46:49 gpg-agent[15166] DBG: chan_9 <- OPTION putenv=QT_IM_MODULE=maliitphablet 2017-09-22 16:46:49 gpg-agent[15166] DBG: chan_9 -> OK 2017-09-22 16:46:49 gpg-agent[15166] DBG: chan_9 <- OPTION lc-ctype=en_GB.UTF-8 2017-09-22 16:46:49 gpg-agent[15166] DBG: chan_9 -> OK 2017-09-22 16:46:49 gpg-agent[15166] DBG: chan_9 <- OPTION lc-messages=en_GB.UTF-8 2017-09-22 16:46:49 gpg-agent[15166] DBG: chan_9 -> OK 2017-09-22 16:46:49 gpg-agent[15166] DBG: chan_9 <- [eof] 2017-09-22 16:46:59 gpg-agent[15166] DBG: chan_9 -> OK Pleased to meet you, process 15169 2017-09-22 16:46:59 gpg-agent[15166] DBG: chan_9 <- RESET 2017-09-22 16:46:59 gpg-agent[15166] DBG: chan_9 -> OK 2017-09-22 16:46:59 gpg-agent[15166] DBG: chan_9 <- OPTION ttyname=/dev/pts/58 2017-09-22 16:46:59 gpg-agent[15166] DBG: chan_9 -> OK 2017-09-22 16:46:59 gpg-agent[15166] DBG: chan_9 <- OPTION ttytype=linux 2017-09-22 16:46:59 gpg-agent[15166] DBG: chan_9 -> OK 2017-09-22 16:46:59 gpg-agent[15166] DBG: chan_9 <- OPTION putenv=DBUS_SESSION_BUS_ADDRESS=unix:abstract=/tmp/dbus-Y5hTZhXCoe 2017-09-22 16:46:59 gpg-agent[15166] DBG: chan_9 -> OK 2017-09-22 16:46:59 gpg-agent[15166] DBG: chan_9 <- OPTION putenv=QT_IM_MODULE=maliitphablet 2017-09-22 16:46:59 gpg-agent[15166] DBG: chan_9 -> OK 2017-09-22 16:46:59 gpg-agent[15166] DBG: chan_9 <- OPTION lc-ctype=en_GB.UTF-8 2017-09-22 16:46:59 gpg-agent[15166] DBG: chan_9 -> OK 2017-09-22 16:46:59 gpg-agent[15166] DBG: chan_9 <- OPTION lc-messages=en_GB.UTF-8 2017-09-22 16:46:59 gpg-agent[15166] DBG: chan_9 -> OK 2017-09-22 16:46:59 gpg-agent[15166] DBG: chan_9 <- GETINFO version 2017-09-22 16:46:59 gpg-agent[15166] DBG: chan_9 -> D 2.1.19 2017-09-22 16:46:59 gpg-agent[15166] DBG: chan_9 -> OK 2017-09-22 16:46:59 gpg-agent[15166] DBG: chan_9 <- OPTION allow-pinentry-notify 2017-09-22 16:46:59 gpg-agent[15166] DBG: chan_9 -> OK 2017-09-22 16:46:59 gpg-agent[15166] DBG: chan_9 <- OPTION agent-awareness=2.1.0 2017-09-22 16:46:59 gpg-agent[15166] DBG: chan_9 -> OK 2017-09-22 16:46:59 gpg-agent[15166] DBG: chan_9 <- RESET 2017-09-22 16:46:59 gpg-agent[15166] DBG: chan_9 -> OK 2017-09-22 16:46:59 gpg-agent[15166] DBG: chan_9 <- GENKEY 2017-09-22 16:46:59 gpg-agent[15166] DBG: chan_9 -> S INQUIRE_MAXLEN 1024 2017-09-22 16:46:59 gpg-agent[15166] DBG: chan_9 -> INQUIRE KEYPARAM 2017-09-22 16:46:59 gpg-agent[15166] DBG: chan_9 <- D (genkey(rsa(nbits 4:2048))) 2017-09-22 16:46:59 gpg-agent[15166] DBG: chan_9 <- END 2017-09-22 16:46:59 gpg-agent[15166] starting a new PIN Entry 2017-09-22 16:46:59 gpg-agent[15166] DBG: connection to PIN entry established 2017-09-22 16:46:59 gpg-agent[15166] DBG: chan_9 -> INQUIRE PINENTRY_LAUNCHED 15347 unknown 0.8.3 ? ? ? 2017-09-22 16:46:59 gpg-agent[15166] DBG: chan_9 <- END 2017-09-22 16:47:30 gpg-agent[15166] starting a new PIN Entry 2017-09-22 16:47:30 gpg-agent[15166] DBG: connection to PIN entry established 2017-09-22 16:47:30 gpg-agent[15166] DBG: chan_9 -> INQUIRE PINENTRY_LAUNCHE
