@werner How can I install libgpgme-develp package on windows 7?

Sorry, we don't use or support PIP. Please ask whoever packaged that for PIP.

... https://lists.gnupg.org/pipermail/gcrypt-devel/2019-July/004760.html

Patches send to mailing list:
https://lists.gnupg.org/pipermail/gcrypt-devel/2019-August/004800.html
https://lists.gnupg.org/pipermail/gcrypt-devel/2019-August/004799.html

this has been commited

this has been commited

If helpful I can demonstrate or let you debug in a TeamViewer (I have a license) or VNC remote session in a fresh VM.
For sure this is not urgent for me. So, take your time!

Mmh, No Data usually means that our parser had a hickup. I'll look at your examples.

Mmh, No Data usually means that our parser had a hickup. I'll look at your examples.

The Python doc build system we implemented the last year is a complete mess - I had so much trouble the last time I did a release :-(.

For OpenPGP card v3.x, the data object is available, but it doesn't come with a button physically. So, I think it's no use.

Hi Andre,

Strange. Can you please go to the command line (cmd.exe) and run gpg --verify "c:\<path to>\gpg4win-3.1.10.exe.sig" "c:\<path to>\gpg4win-3.1.10.exe.sig"

can you hover over the GpgOL Icon and look at the tooltip? Maybe there was an error during validation.

Account disabled and I'm closing this as resolved.

Thanks for reporting this! I've added it to our list of know problematic Addins. https://wiki.gnupg.org/GpgOL/IncompatibleAddons#Mimecast_for_Outlook

I've sent multiple PGP/MIME mails in various formats to a protonmail developer and all worked fine. So we have confirmed that protonmail and GpgOL are generally compatible.

Thanks. Fixed in stanble and master.

For OpenPGP card v3.x, the data object is available, but it doesn't come with a button physically. So, I think it's no use.

I am sorry it just needed to be run as root.

I have OpenPGP Smart Cards V3.3 from FLOSS Shop - these should support UIF, shouldn't they? I assumed so, because the spec includes it as of 3.0.

For information, I can’t reproduce here, either with GnuPG 2.2.17 / Pinentry 1.1.0 or with a fresh build from the tip of the master branches. Both pinentry-tty and pinentry-curses prompt for the password as expected, independently of whether the file to decrypt is specified as an argument or sent through standard input.

i'm actually running make -j3 check, since make -j3 distcheck has the problems described in T4688.

So i've been able to (intermittently) reproduce the failures that i think @werner was alluding to here, but not under any circumstances where i can get them to happen reliably to understand what's going on.

I've sent a mail to a protonmail dev asking if protonmail supports PGP/MIME.

Please read my answer again. Posting to gnupg-users does not require a subscription.

Please do not force me subscribe to yet another mailing list to see the answer.
So do you have any plans to make new release? :)

See T4683 and T4684.

I'll start working on PowerPC GHASH implementation in September after SHA2 is done.

I'll start working on new PowerPC SHA2 implementations for libgcrypt in coming weeks.

Patches for PowerPC AES acceleration sent to mailing-list, based partly on initial work by Shawn Landden (@slandden): https://lists.gnupg.org/pipermail/gcrypt-devel/2019-August/004788.html

It has now been more than a month since:

And also this is excellent point.

oops: That was an accidential priority change