gpgme_op_delete_ext flag GPGME_DELETE_FORCE not working?

Hi, I've been trying to use the GPGME_DELETE_FORCE flag in gpgme_op_delete_ext, but I'm still getting not one, but two "Do you really want to delete..." prompts popping up, one for the secret key, one for the sub-key. I am using GPGme version 1.11.1 in combination with gpg 2.2.8 (as confirmed by

Re: gnupg.org Listserver maybe misconfigured?

On 18/06/2018 18:24, Juergen BRUCKNER wrote: > Hello Mark! > > Thank you very much for your answer and clarificattion. My pleasure. -- Mark Rousell ___ Gnupg-users mailing list Gnupg-users@gnupg.org

Re: gnupg.org Listserver maybe misconfigured?

Hello Mark! Thank you very much for your answer and clarificattion. Am 2018-06-18 um 19:18 schrieb Mark Rousell: > I note that your bruckner.tk domain appears to have a p=none policy so, > if I understand all this correctly, it should not matter to you. > > In short, there is nothing to worry

Re: gnupg.org Listserver maybe misconfigured?

On 18/06/2018 17:23, Juergen BRUCKNER wrote: > Hello guys, > > could it be happen that the Server for the GnuPG.org Mailinglists is > kinda misconfigured? > > My weekly DMARC-Report says that gnupg.org sent in sum 477 Mails in the > name of the Domain 'bruckner.tk' last week. > > ---snip--- >

gnupg.org Listserver maybe misconfigured?

Hello guys, could it be happen that the Server for the GnuPG.org Mailinglists is kinda misconfigured? My weekly DMARC-Report says that gnupg.org sent in sum 477 Mails in the name of the Domain 'bruckner.tk' last week. ---snip--- gnupg.org 217.69.76.57

Re: Upgrading 2.0.20 to 2.2.24

On Mon, Jun 18, 2018 at 03:19:53PM +0200, Kristian Fiskerstrand wrote: > On 06/18/2018 03:06 PM, fe...@crowfix.com wrote: > > Says it imported the secret keys, but doesn't show them. > > Any chance they are expired? Try playing with --list-options, in > particular the show-unusable-* variants >

Re: Upgrading 2.0.20 to 2.2.24

On 06/18/2018 03:06 PM, fe...@crowfix.com wrote: > Says it imported the secret keys, but doesn't show them. Any chance they are expired? Try playing with --list-options, in particular the show-unusable-* variants Are they listed with --list-keys ? Try importing the public keyring separately, in

Re: Upgrading 2.0.20 to 2.2.24

On Mon, Jun 18, 2018 at 08:36:38AM +0200, Werner Koch wrote: > On Mon, 18 Jun 2018 07:44, skqu...@rushpost.com said: > > > The format secret keys are stored in changed between 2.0.x and 2.1.x. It > > is possible that 2.2.x no longer has the code in it to migrate to the > > 2.2 still has the

Re: Upgrading 2.0.20 to 2.2.24

On Mon, 18 Jun 2018 07:44, skqu...@rushpost.com said: > The format secret keys are stored in changed between 2.0.x and 2.1.x. It > is possible that 2.2.x no longer has the code in it to migrate to the 2.2 still has the migration code. However, once a migration is done it will not be done again.