You are right. Printing the algo was missing in gnupg22.
- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
All Stories
Nov 21 2024
Yeah, it's a dilemma. How about if we use the narrower formatting everywhere only starting from 6 or 7 words in the English string? Or some count of characters?
Nov 20 2024
Backported for VSD 3.3
Shall we use the narrower tooltips in general? I'm undecided. On one hand, we'd avoid an unholy mix of wider (but not too long) one-line tooltips (at least for English and maybe German) and narrower multi-line tooltips. On the other hand, I think the multi-line tooltips are too narrow and a narrow two-liner might look uglier than a slightly wider one-liner.
thanks for the clarification. i was not objecting to the workflow, i was trying to understand so that i can interact with the bug tracker appropriately. I was unaware of the difference between "milestones" and other project tags. I'll try to get that right in the future.
I have added the NEWS for Kleopatra for Gpg4win 4.4.0. I have excluded the following tickets from the NEWS for various reasons:
Please do not add milestone tags.
gnupg24 (gnupg-2.4.5) is a milestone and means "fixed in gnupg24 (gnupg-2.4.5)". I suggest not to question the workflow of the people running this bug tracker.
Nov 19 2024
@ebo i'm not sure i understand why you removed the gnupg24 (gnupg-2.4.5) project label. the report indicates that GnuPG 2.4.6 at least (other versions untested, but i didn't see a gnupg24 (gnupg-2.4.6) label in this system) produces MPI artifacts for EdDSA/Ed25519 signatures that are non-compliant with all the known specifications. the 2.2 series appears to retain compatible MPI formats.
Fixed and now autosaved draft are also correctly restored when restarting gpgol.js
with no real world impact.
This is not a bug in 2.2, this is a bug in 2.4.
2.2. reaches EOL in 6 weeks and thus we won't look at a potential problem with no real world impact.
I suggest to make the following text changes for the VSD versions only:
Nov 18 2024
after a bit more testing, it looks to me like 2.2.45 will revise the signature packet to use 0x00ed as the MPI header for r, if it receives input from 2.4.6. And 2.4.6 will revise the signature packet to use 0x0100 as the MPI header for r. So the same OpenPGP self-sig will change shape each time it is passed back and forth between the different versions.