I've tested this issue on my Windows10 laptop.
- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
All Stories
Apr 1 2020
I've checked: this issue is reproducible in Kleopatra 3.1.11 / Win10
I have installed version of Gpg4win, not portable
Also see Issue #10, Add Travis testing in the GnuPG GitHub. The PR adds Travis testing to the entire GnuPG suite.
Applied the fix also to master with a comment to ebentually replace it with es_fopenmem.
The problem itself is fixed (in T4495: UBsan finding "certdump.c:695:3: runtime error: null pointer passed as argument 2"). The variable buffer cannot be NULL at memcpy.
Mar 31 2020
genkey for Ed25519 works now with libksba in master.
For public key, it's done.
Mar 30 2020
thanks!
Done; will go into 2.2.21 (T4897).
Thanks.
The problem was the comment field which was not expected in an rsa key. However ist makes sense to allow additional fields and thus I pushed a change to Libksba.
Mar 29 2020
This bug is linked to restoring window size in case of multi-monitor multi-DPI setup.
There is QT bug report: https://bugreports.qt.io/browse/QTBUG-77385
Thanks for following up!
No, we always stated that the user id is a mandatory part of OpenPGP keyblocks and that non-compliant keyblocks are rejected. The only exception we made are for revocation signatures where we allow a standalone packet. That exception is done to allow typing in a printed out revocation signature.
To be clear: marking this ticket wontfix means (among other things) that it is the GnuPG project's upstream position that:
With OpenPGP we made user ids mandatory to avoid problems we had with PGP2. I see no reason to revert this.
Mar 28 2020
Nine months have passed since the patches for this problem have been available.
Mar 27 2020
I recall that I talked with Stephan about it but things got lost.
NIST P-256 key generation looks good.
Mar 26 2020
Of course it is important, that's why it it printed by default.
This is an important information to know because it can help to avoid bug reports.
OK, i've asked on gnupg-devel.
Please use the mailing list for help on generating keys. I would also suggest to use GnuPG master for such experiments.
Mar 25 2020
FWIW, a log of the decryption process will always show the sender's key because a message is usually also encrypted to that one (--encrypt-to).
If you run into build problems on OpenBSD for gpg-wks-server, see T4886 for a required minor fix.