gpgme_op_delete() does not work with gpg 2.x

[Jeroen Ooms]

On Sat, Dec 29, 2018 at 5:01 PM brent s. <bts at square-r00t.net> wrote:
>
> On 12/29/18 9:01 AM, Jeroen Ooms wrote:
> > A user of the R bindings has reported (and I have confirmed) that
> > deleting secret keys in gpgme does not work with gnupg2. We call (on
> > an existing key):
> >
> >   gpgme_op_delete(ctx, key, 1)
> >
> > This returns success if the key exists, and when we are running with
> > GnuPG 1.4 the key is deleted. However when running gpg2 it returns
> > success but the key is still there.
> >
> > Downstream issue: https://github.com/jeroen/gpg/issues/3
> >
> > _______________________________________________
> > Gnupg-devel mailing list
> > Gnupg-devel at gnupg.org
> > http://lists.gnupg.org/mailman/listinfo/gnupg-devel
> >
>
> I'm not sure how much this will help you, but deleting a private key
> works in the Python bindings if I use the abstracted method but not the
> direct gpgme method (see attached POC).

So which C function does the latter use then? I don't use python but
to me it looks like both those methods are different syntax for the
same thing? Why would they show different behavior?


> Haven't taken a look at the R bindings; is there a similar
> context-specific method there?

I maintain these bindings so I can add it a working implementation if
I know which C API to call.