Feb 16 2024
No, I am not aware. I can't remember whether PGP once had such a bug because @dshaw did most cross-testing and fixing for PGP bugs. I would suggest to remove any such checks. IIRC, this was introduced by PGP 2 to speed up signature checking. 30 years ago RSA operations were quite expensive.
Feb 7 2024
VS-NfD is not a standard but a classification for restricted data. Software used to convey such material needs an official approval and is bound to certain organizational requirements. That is what "VS-NfD konform" says. The community version of gpg4win does not have this approval despite that it is technically the same code as the approved GnuPG VS-Desktop.
Feb 5 2024
Unfortunately there are real world applications which make use of this option in special environments. Thus we can't remove it. I improved the warning in the man page.
Jan 24 2024
Dec 28 2023
Dec 12 2023
In 2.4, a user need to specify disable-ccid in scdaemon.conf when scdaemon is built with integrated CCID driver (using libusb) but the user wants to use PC/SC driver instead.
Nov 16 2023
To align the documentation of GnuPG, we should not use GNUPGHOME in FILES section.
It may be controlled by --homedir as well as GNUPGHOME.
GNUPGHOME is addressed in the ENVIRONMENT section, so, I don't think it makes sense using $GNUPGHOME}/trustedkeys.kbx.
Thank you. Applied and pushed in: rG260004747016: gpgv: Update used keyrings in doc FILES section
Nov 12 2023
Oct 25 2023
Oct 17 2023
Your tools don't use the chain validation model which is required for QES (at least according to German laws). A signature is still valid even if the certificate has been revoked. You need to consider the context and the time the certificate was revoked.
Sep 26 2023
Here's another data point.
Aug 22 2023
Aug 1 2023
Okay, will go into the next revision. Thanks.
Jul 31 2023
Thanks for the reply!
Jul 20 2023
Jun 13 2023
Thanks. I think that it was the oldest one: FSF used to be there in Cambridge, then moved to Tremont St. in Boston, and now it's in Franklin St.
Jun 12 2023
FYI, while going through the licenses again I noticed one of the pinentry files have even older address that so if you would do sed, this would not be matched:
May 26 2023
May 2 2023
The user tried to sneak in an ad link and he has thus been banned. Here is his probably AI generated comment for documentation:
Apr 27 2023
Fixed for libgcrypt, updating copyright notices and license files.
Apr 26 2023
@ikloecker Thanks for your comment. I put a comment in the commit.
Apr 25 2023
Note that this may not work for Python 2.7, but since those are just examples that doesn't matter that much.
So, here are fixes. I'll apply soonish.
Apr 24 2023
Funny enough that Python seems not to allow to set the permission with open. Low priority because a proper umask must anyway be used on a multi-user system.
Apr 13 2023
Fixed in 1.19.0.
Apr 12 2023
The crypto profiles have been removed in Gpg4win 4.1.1
Apr 4 2023
Any volunteers to write a manual? ;-)
Mar 28 2023
Actually this is about improving an error message.
Mar 24 2023
Thanks for your follwup. Let me remark that it is sufficient to stop all gnupg processes (pkill gpg-agent) and then rename the ~/.gnupg to .gnupg-save-NNNN. This way you have a backup and gpg will create a new ~/.gnupg.
Mar 3 2023
Thanks for the description; this is good for documentation.
Jan 31 2023
Thanks. I fixed the documentation. Will go into 1.19