Re: gpg-preset-passphrase not working with 2.1
On 14 July 2016 at 07:29, David Matthews <davidmatthew...@gmail.com> wrote: > On 13 July 2016 at 13:13, Daniel Kahn Gillmor <d...@fifthhorseman.net> wrote: >> Hi David-- >> >> On Tue 2016-07-12 16:46:53 +0200, David Matthews wrote: >>> I can't get gpg-preset-passphrase to work with GnuPG 2.1.7. >> >> there have been significant changes to GnuPG between 2.1.7 and 2.1.13. >> >> can you try upgrading to 2.1.13? > > I've compiled 2.1.13 on Fedora 23 and get the same result (test output below). > > According to issue 2015 this was caused by a change that went into > release 2.1.5. Could someone with the necessary permissions please add a comment to https://bugs.gnupg.org/gnupg/issue2015 to indicate that this bug still exists at 2.1.13 and also update the title? I only have permission to create a new bug and I don't want to create a duplicate. Thanks, David ___ Gnupg-users mailing list Gnupg-users@gnupg.org http://lists.gnupg.org/mailman/listinfo/gnupg-users
Re: gpg-preset-passphrase not working with 2.1
On 13 July 2016 at 13:13, Daniel Kahn Gillmor <d...@fifthhorseman.net> wrote: > Hi David-- > > On Tue 2016-07-12 16:46:53 +0200, David Matthews wrote: >> I can't get gpg-preset-passphrase to work with GnuPG 2.1.7. > > there have been significant changes to GnuPG between 2.1.7 and 2.1.13. > > can you try upgrading to 2.1.13? I've compiled 2.1.13 on Fedora 23 and get the same result (test output below). According to issue 2015 this was caused by a change that went into release 2.1.5. Thanks, David ++ gpg-agent -vv --daemon --allow-preset-passphrase --debug-level 9 gpg-agent[12163]: enabled debug flags: command mpi crypto memory cache memstat ipc gpg-agent[12163]: listening on socket '/run/user/1000/gnupg/S.gpg-agent' gpg-agent[12164]: gpg-agent (GnuPG) 2.1.13 started + eval '' + /usr/local/libexec/gpg-preset-passphrase -vv --preset -P test myid gpg-agent[12164]: handler 0x7fc9c028a700 for fd 4 started gpg-agent[12164]: DBG: chan_4 -> OK Pleased to meet you, process 12165 gpg-agent[12164]: DBG: chan_4 <- OPTION ttyname=/dev/pts/0 gpg-agent[12164]: DBG: chan_4 -> OK gpg-agent[12164]: DBG: chan_4 <- OPTION ttytype=xterm gpg-agent[12164]: DBG: chan_4 -> OK gpg-agent[12164]: DBG: chan_4 <- OPTION lc-ctype=en_US.UTF-8 gpg-agent[12164]: DBG: chan_4 -> OK gpg-agent[12164]: DBG: chan_4 <- OPTION lc-messages=en_US.UTF-8 gpg-agent[12164]: DBG: chan_4 -> OK gpg-agent[12164]: DBG: chan_4 <- PRESET_PASSPHRASE myid -1 74657374 gpg-agent[12164]: DBG: agent_put_cache 'myid' (mode 1) requested ttl=-1 gpg-agent[12164]: DBG: chan_4 -> S PROGRESS need_entropy X 60 120 gpg-agent[12164]: DBG: chan_4 -> S PROGRESS need_entropy X 120 120 Removed lots of repeated lines gpg-agent[12164]: DBG: chan_4 -> S PROGRESS need_entropy X 60 120 gpg-agent[12164]: DBG: chan_4 -> S PROGRESS need_entropy X 120 120 gpg-agent[12164]: DBG: chan_4 -> OK gpg-agent[12164]: DBG: chan_4 <- [eof] gpg-agent[12164]: handler 0x7fc9c028a700 for fd 4 terminated + echo 'GET_PASSPHRASE --no-ask myid Err Pmt Des' + gpg-connect-agent -vv gpg-agent[12164]: handler 0x7fc9c028a700 for fd 4 started gpg-agent[12164]: DBG: chan_4 -> OK Pleased to meet you, process 12168 gpg-agent[12164]: DBG: chan_4 <- RESET gpg-agent[12164]: DBG: chan_4 -> OK gpg-agent[12164]: DBG: chan_4 <- OPTION ttytype=xterm gpg-agent[12164]: DBG: chan_4 -> OK gpg-agent[12164]: DBG: chan_4 <- GET_PASSPHRASE --no-ask myid Err Pmt Des gpg-agent[12164]: DBG: agent_get_cache 'myid' (mode 3) ... gpg-agent[12164]: DBG: ... miss gpg-agent[12164]: command 'GET_PASSPHRASE' failed: No data gpg-agent[12164]: DBG: chan_4 -> ERR 67108922 No data gpg-connect-agent: closing connection to agent ERR 67108922 No data gpg-agent[12164]: DBG: chan_4 <- [eof] gpg-agent[12164]: handler 0x7fc9c028a700 for fd 4 terminated ___ Gnupg-users mailing list Gnupg-users@gnupg.org http://lists.gnupg.org/mailman/listinfo/gnupg-users
gpg-preset-passphrase not working with 2.1
I can't get gpg-preset-passphrase to work with GnuPG 2.1.7. The command appears to work successfully but the passphase is not found by GET_PASSPHRASE. I've included details of my simple test below plus the output from running it on Centos 7.2 (where it works using 2.0.22) and Fedora 23 (where it fails using 2.1.7). Searching through the issue tracker I found https://bugs.gnupg.org/gnupg/issue2015. The title of this issue is "GET_PASSPHRASE with --no-ask always return error in gnupg 2.1.5" but, based on the discussion in the issue, I think the title is now wrong and should really be "gpg-preset-passphrase does not work". Have I understood that correctly? If so I assume I will see the same issue with the latest release? Any advice much appreciated. Thanks ## Test script #!/bin/bash set -x eval "$(gpg-agent -vv --daemon --allow-preset-passphrase --debug-level 9)" /usr/libexec/gpg-preset-passphrase -vv --preset -P test myid echo "GET_PASSPHRASE --no-ask myid Err Pmt Des" | gpg-connect-agent -vv ## Centos 7.2 output ++ gpg-agent -vv --daemon --allow-preset-passphrase --debug-level 9 gpg-agent[3239]: enabled debug flags: command mpi crypto memory cache memstat assuan gpg-agent[3239]: listening on socket `/home/vagrant/.gnupg/S.gpg-agent' gpg-agent[3240]: gpg-agent (GnuPG) 2.0.22 started + eval 'GPG_AGENT_INFO=/home/vagrant/.gnupg/S.gpg-agent:3240:1; export GPG_AGENT_INFO;' ++ GPG_AGENT_INFO=/home/vagrant/.gnupg/S.gpg-agent:3240:1 ++ export GPG_AGENT_INFO + /usr/libexec/gpg-preset-passphrase -vv --preset -P test myid gpg-agent[3240]: handler 0xcfcb70 for fd 7 started gpg-agent[3240]: chan_7 -> OK Pleased to meet you, process 3241 gpg-agent[3240]: chan_7 <- OPTION display=localhost:10.0 gpg-agent[3240]: chan_7 -> OK gpg-agent[3240]: chan_7 <- OPTION ttyname=/dev/pts/1 gpg-agent[3240]: chan_7 -> OK gpg-agent[3240]: chan_7 <- OPTION ttytype=dumb gpg-agent[3240]: chan_7 -> OK gpg-agent[3240]: chan_7 <- OPTION lc-ctype=en_US.UTF-8 gpg-agent[3240]: chan_7 -> OK gpg-agent[3240]: chan_7 <- OPTION lc-messages=en_US.UTF-8 gpg-agent[3240]: chan_7 -> OK gpg-agent[3240]: chan_7 <- PRESET_PASSPHRASE myid -1 74657374 gpg-agent[3240]: DBG: agent_put_cache `myid' requested ttl=-1 mode=1 gpg-agent[3240]: chan_7 -> OK gpg-agent[3240]: chan_7 <- [eof] gpg-agent[3240]: handler 0xcfcb70 for fd 7 terminated + echo 'GET_PASSPHRASE --no-ask myid Err Pmt Des' + gpg-connect-agent -vv gpg-agent[3240]: handler 0xcfe550 for fd 7 started gpg-agent[3240]: chan_7 -> OK Pleased to meet you, process 3243 gpg-connect-agent: connection to agent established gpg-agent[3240]: chan_7 <- RESET gpg-agent[3240]: chan_7 -> OK gpg-agent[3240]: chan_7 <- OPTION ttytype=dumb gpg-agent[3240]: chan_7 -> OK gpg-agent[3240]: chan_7 <- OPTION display=localhost:10.0 gpg-agent[3240]: chan_7 -> OK gpg-agent[3240]: chan_7 <- GET_PASSPHRASE --no-ask myid Err Pmt Des gpg-agent[3240]: DBG: agent_get_cache `myid'... gpg-agent[3240]: DBG: ... hit gpg-agent[3240]: chan_7 -> [[Confidential data not shown]] OK 74657374 gpg-connect-agent: closing connection to agent ## Fedora 23 output ++ gpg-agent -vv --daemon --allow-preset-passphrase --debug-level 9 gpg-agent[1420]: enabled debug flags: command mpi crypto memory cache memstat ipc gpg-agent[1420]: listening on socket '/home/vagrant/.gnupg/S.gpg-agent' gpg-agent[1421]: gpg-agent (GnuPG) 2.1.7 started + eval '' + /usr/libexec/gpg-preset-passphrase -vv --preset -P test myid gpg-agent[1421]: handler 0x7f8092ffc700 for fd 4 started gpg-agent[1421]: DBG: chan_4 -> OK Pleased to meet you, process 1422 gpg-agent[1421]: DBG: chan_4 <- OPTION ttyname=/dev/pts/1 gpg-agent[1421]: DBG: chan_4 -> OK gpg-agent[1421]: DBG: chan_4 <- OPTION ttytype=dumb gpg-agent[1421]: DBG: chan_4 -> OK gpg-agent[1421]: DBG: chan_4 <- OPTION lc-ctype=en_US.UTF-8 gpg-agent[1421]: DBG: chan_4 -> OK gpg-agent[1421]: DBG: chan_4 <- OPTION lc-messages=en_US.UTF-8 gpg-agent[1421]: DBG: chan_4 -> OK gpg-agent[1421]: DBG: chan_4 <- PRESET_PASSPHRASE myid -1 74657374 gpg-agent[1421]: DBG: agent_put_cache 'myid' (mode 1) requested ttl=-1 gpg-agent[1421]: DBG: chan_4 -> OK gpg-agent[1421]: DBG: chan_4 <- [eof] gpg-agent[1421]: handler 0x7f8092ffc700 for fd 4 terminated + echo 'GET_PASSPHRASE --no-ask myid Err Pmt Des' + gpg-connect-agent -vv gpg-agent[1421]: handler 0x7f8092ffc700 for fd 4 started gpg-agent[1421]: DBG: chan_4 -> OK Pleased to meet you, process 1425 gpg-agent[1421]: DBG: chan_4 <- RESET gpg-agent[1421]: DBG: chan_4 -> OK gpg-agent[1421]: DBG: chan_4 <- OPTION ttytype=dumb gpg-agent[1421]: DBG: chan_4 -> OK gpg-agent[1421]: DBG: chan_4 <- OPTION putenv=INSIDE_EMACS=24.5.1,comint gpg-agent[1421]: DBG: chan_4 -> OK gpg-agent[1421]: DBG: chan_4 <- GET_PASSPHRASE --no-ask myid Err Pmt Des gpg-agent[1421]: DBG: agent_get_cache 'myid' (mode 3) ... gpg-agent[1421]: DBG: ... miss gpg-agent[1421]: command 'GET_PASSPHRASE' failed: No data gpg-agent[1421]: DBG: chan_4 -> ERR 67108922 No data ERR 67108922 No data gpg-connect-agent: closing connection to
gpg-preset-passphrase not working with 2.1
I can't get gpg-preset-passphrase to work with GnuPG 2.1.7. The command appears to work successfully but the passphase is not found by GET_PASSPHRASE. I've included details of my simple test below plus the output from running it on Centos 7.2 (where it works using 2.0.22) and Fedora 23 (where it fails using 2.1.7). Searching through the issue tracker I found https://bugs.gnupg.org/gnupg/issue2015. The title of this issue is "GET_PASSPHRASE with --no-ask always return error in gnupg 2.1.5" but, based on the discussion in the issue, I think the title should really be "gpg-preset-passphrase does not work". Have I understood that correctly? If so I assume I will see the same issue with the latest release? Any advice much appreciated. My setup relies on using gpg-preset-passphrase so I'll need to install 2.0 for the moment unless I can get this working. Thanks, David ## Test script #!/bin/bash set -x eval "$(gpg-agent -vv --daemon --allow-preset-passphrase --debug-level 9)" /usr/libexec/gpg-preset-passphrase -vv --preset -P test myid echo "GET_PASSPHRASE --no-ask myid Err Pmt Des" | gpg-connect-agent -vv ## Centos 7.2 output ++ gpg-agent -vv --daemon --allow-preset-passphrase --debug-level 9 gpg-agent[3239]: enabled debug flags: command mpi crypto memory cache memstat assuan gpg-agent[3239]: listening on socket `/home/vagrant/.gnupg/S.gpg-agent' gpg-agent[3240]: gpg-agent (GnuPG) 2.0.22 started + eval 'GPG_AGENT_INFO=/home/vagrant/.gnupg/S.gpg-agent:3240:1; export GPG_AGENT_INFO;' ++ GPG_AGENT_INFO=/home/vagrant/.gnupg/S.gpg-agent:3240:1 ++ export GPG_AGENT_INFO + /usr/libexec/gpg-preset-passphrase -vv --preset -P test myid gpg-agent[3240]: handler 0xcfcb70 for fd 7 started gpg-agent[3240]: chan_7 -> OK Pleased to meet you, process 3241 gpg-agent[3240]: chan_7 <- OPTION display=localhost:10.0 gpg-agent[3240]: chan_7 -> OK gpg-agent[3240]: chan_7 <- OPTION ttyname=/dev/pts/1 gpg-agent[3240]: chan_7 -> OK gpg-agent[3240]: chan_7 <- OPTION ttytype=dumb gpg-agent[3240]: chan_7 -> OK gpg-agent[3240]: chan_7 <- OPTION lc-ctype=en_US.UTF-8 gpg-agent[3240]: chan_7 -> OK gpg-agent[3240]: chan_7 <- OPTION lc-messages=en_US.UTF-8 gpg-agent[3240]: chan_7 -> OK gpg-agent[3240]: chan_7 <- PRESET_PASSPHRASE myid -1 74657374 gpg-agent[3240]: DBG: agent_put_cache `myid' requested ttl=-1 mode=1 gpg-agent[3240]: chan_7 -> OK gpg-agent[3240]: chan_7 <- [eof] gpg-agent[3240]: handler 0xcfcb70 for fd 7 terminated + echo 'GET_PASSPHRASE --no-ask myid Err Pmt Des' + gpg-connect-agent -vv gpg-agent[3240]: handler 0xcfe550 for fd 7 started gpg-agent[3240]: chan_7 -> OK Pleased to meet you, process 3243 gpg-connect-agent: connection to agent established gpg-agent[3240]: chan_7 <- RESET gpg-agent[3240]: chan_7 -> OK gpg-agent[3240]: chan_7 <- OPTION ttytype=dumb gpg-agent[3240]: chan_7 -> OK gpg-agent[3240]: chan_7 <- OPTION display=localhost:10.0 gpg-agent[3240]: chan_7 -> OK gpg-agent[3240]: chan_7 <- GET_PASSPHRASE --no-ask myid Err Pmt Des gpg-agent[3240]: DBG: agent_get_cache `myid'... gpg-agent[3240]: DBG: ... hit gpg-agent[3240]: chan_7 -> [[Confidential data not shown]] OK 74657374 gpg-connect-agent: closing connection to agent ## Fedora 23 output ++ gpg-agent -vv --daemon --allow-preset-passphrase --debug-level 9 gpg-agent[1420]: enabled debug flags: command mpi crypto memory cache memstat ipc gpg-agent[1420]: listening on socket '/home/vagrant/.gnupg/S.gpg-agent' gpg-agent[1421]: gpg-agent (GnuPG) 2.1.7 started + eval '' + /usr/libexec/gpg-preset-passphrase -vv --preset -P test myid gpg-agent[1421]: handler 0x7f8092ffc700 for fd 4 started gpg-agent[1421]: DBG: chan_4 -> OK Pleased to meet you, process 1422 gpg-agent[1421]: DBG: chan_4 <- OPTION ttyname=/dev/pts/1 gpg-agent[1421]: DBG: chan_4 -> OK gpg-agent[1421]: DBG: chan_4 <- OPTION ttytype=dumb gpg-agent[1421]: DBG: chan_4 -> OK gpg-agent[1421]: DBG: chan_4 <- OPTION lc-ctype=en_US.UTF-8 gpg-agent[1421]: DBG: chan_4 -> OK gpg-agent[1421]: DBG: chan_4 <- OPTION lc-messages=en_US.UTF-8 gpg-agent[1421]: DBG: chan_4 -> OK gpg-agent[1421]: DBG: chan_4 <- PRESET_PASSPHRASE myid -1 74657374 gpg-agent[1421]: DBG: agent_put_cache 'myid' (mode 1) requested ttl=-1 gpg-agent[1421]: DBG: chan_4 -> OK gpg-agent[1421]: DBG: chan_4 <- [eof] gpg-agent[1421]: handler 0x7f8092ffc700 for fd 4 terminated + echo 'GET_PASSPHRASE --no-ask myid Err Pmt Des' + gpg-connect-agent -vv gpg-agent[1421]: handler 0x7f8092ffc700 for fd 4 started gpg-agent[1421]: DBG: chan_4 -> OK Pleased to meet you, process 1425 gpg-agent[1421]: DBG: chan_4 <- RESET gpg-agent[1421]: DBG: chan_4 -> OK gpg-agent[1421]: DBG: chan_4 <- OPTION ttytype=dumb gpg-agent[1421]: DBG: chan_4 -> OK gpg-agent[1421]: DBG: chan_4 <- OPTION putenv=INSIDE_EMACS=24.5.1,comint gpg-agent[1421]: DBG: chan_4 -> OK gpg-agent[1421]: DBG: chan_4 <- GET_PASSPHRASE --no-ask myid Err Pmt Des gpg-agent[1421]: DBG: agent_get_cache 'myid' (mode 3) ... gpg-agent[1421]: DBG: ... miss gpg-agent[1421]: command 'GET_PASSPHRASE' failed: No data