Possible GPGME bug

[Adam Schreiber]

On 11/1/07, Marcus Brinkmann <marcus.brinkmann at ruhr-uni-bochum.de> wrote:
> At Wed, 31 Oct 2007 15:37:52 -0400,
> "Adam Schreiber" <sadam at clemson.edu> wrote:
> >
> > In fixing a bug in Seahorse, I found that our feature to revoke a sub
> > key was no longer working.  It uses the gpgme_op_edit API.  I checked
> > the challenge and responses of gpg --edit-key manually and found that
> > they matched those our state machine expected.
>
> Did you check using the same arguments to gpg for invocation?  GPGME
> adds a whole bunch of arguments to the command line (check with ps).

Using the same arguments to gpg except for changing the status-fd and
command-fd arguments, I get what's pasted below.  This is the expected
order of statements.  DO you have any other suggestions of what I
could check?

Cheers,

Adam

gpg --use-agent --no-sk-comment --lc-messages C --lc-ctype C
--status-fd 2 --no-tty --charset utf8 --enable-progress-filter
--display :0.0 --ttyname /dev/pts/1 --command-fd 0 --with-colons
--edit-key -- 9B6A8AABE2EB80683AE418730116FD16FA676606
gpg (GnuPG) 1.4.7; Copyright (C) 2006 Free Software Foundation, Inc.
This program comes with ABSOLUTELY NO WARRANTY.
This is free software, and you are welcome to redistribute it
under certain conditions. See the file COPYING for details.

pub:u:1024:17:0116FD16FA676606:1181933414:0::u:
fpr:::::::::9B6A8AABE2EB80683AE418730116FD16FA676606:
sub:u:2048:16:312839264174BB1E:1181933414:0:::
fpr:::::::::0BE8689516056C34C7B19768312839264174BB1E:
sub:u:1024:17:E9AAAE226AE18AAF:1193753469:0:::
fpr:::::::::E4E21D34B594F9448B591278E9AAAE226AE18AAF:
uid:u::::::::fake1:::S9 S8 S7 S3 S2 H2 H8 H3 Z2 Z3 Z1,mdc,no-ks-modify:1,p:
uat:u::::::::1 3892:::S9 S8 S7 S3 S2 H2 H8 H3 Z2 Z3 Z1,mdc,no-ks-modify:2,p:
uat:u::::::::1 4846:::S9 S8 S7 S3 S2 H2 H8 H3 Z2 Z3 Z1,mdc,no-ks-modify:3,:
[GNUPG:] GET_LINE keyedit.prompt
key 2
[GNUPG:] GOT_IT
pub:u:1024:17:0116FD16FA676606:1181933414:0::u:
fpr:::::::::9B6A8AABE2EB80683AE418730116FD16FA676606:
sub:u:2048:16:312839264174BB1E:1181933414:0:::
fpr:::::::::0BE8689516056C34C7B19768312839264174BB1E:
sub:u:1024:17:E9AAAE226AE18AAF:1193753469:0:::
fpr:::::::::E4E21D34B594F9448B591278E9AAAE226AE18AAF:
uid:u::::::::fake1:::S9 S8 S7 S3 S2 H2 H8 H3 Z2 Z3 Z1,mdc,no-ks-modify:1,p:
uat:u::::::::1 3892:::S9 S8 S7 S3 S2 H2 H8 H3 Z2 Z3 Z1,mdc,no-ks-modify:2,p:
uat:u::::::::1 4846:::S9 S8 S7 S3 S2 H2 H8 H3 Z2 Z3 Z1,mdc,no-ks-modify:3,:
[GNUPG:] GET_LINE keyedit.prompt
revkey
[GNUPG:] GOT_IT
[GNUPG:] GET_BOOL keyedit.revoke.subkey.okay
yes
[GNUPG:] GOT_IT
[GNUPG:] GET_LINE ask_revocation_reason.code
3
[GNUPG:] GOT_IT
[GNUPG:] GET_LINE ask_revocation_reason.text
test key
[GNUPG:] GOT_IT
[GNUPG:] GET_LINE ask_revocation_reason.text

[GNUPG:] GOT_IT
[GNUPG:] GET_BOOL ask_revocation_reason.okay
yes
[GNUPG:] GOT_IT
[GNUPG:] USERID_HINT 0116FD16FA676606 fake1
[GNUPG:] NEED_PASSPHRASE 0116FD16FA676606 0116FD16FA676606 17 0
[GNUPG:] GOOD_PASSPHRASE
pub:u:1024:17:0116FD16FA676606:1181933414:0::u:
fpr:::::::::9B6A8AABE2EB80683AE418730116FD16FA676606:
sub:u:2048:16:312839264174BB1E:1181933414:0:::
fpr:::::::::0BE8689516056C34C7B19768312839264174BB1E:
sub:r:1024:17:E9AAAE226AE18AAF:1193753469:0:::
fpr:::::::::E4E21D34B594F9448B591278E9AAAE226AE18AAF:
uid:u::::::::fake1:::S9 S8 S7 S3 S2 H2 H8 H3 Z2 Z3 Z1,mdc,no-ks-modify:1,p:
uat:u::::::::1 3892:::S9 S8 S7 S3 S2 H2 H8 H3 Z2 Z3 Z1,mdc,no-ks-modify:2,p:
uat:u::::::::1 4846:::S9 S8 S7 S3 S2 H2 H8 H3 Z2 Z3 Z1,mdc,no-ks-modify:3,:
[GNUPG:] GET_LINE keyedit.prompt