- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
All Stories
Nov 12 2025
I checked the code under gnupg/dirmngr. Those are no harm.
Nov 11 2025
Removing VSD 3.4 tag. I don't intend to backport the changes in Qt 6 to Qt 5.
In T7588#207022, @timegrid wrote:
- unselected radio/checkboxes are a bit hard to see and worse to distinguish
In T7588#207022, @timegrid wrote:
- calendar (weekend days: general/selected/hover on dark background)
There are a lot of other ways to confuse the user. We can't fix them all because the whole purpose of a cleartext signature is to make it easy to use in legacy environments like an BBS. Modern systems use MIME to handle this in a more stringent specified way. For any use it is stongly suggested to check the actual signed data which is avaialable with the --output options. At least a sanitizing viewer should be used which filters out all escape characters (something like cat -v |less).
We have seen wrong encodings quite often in the past and thus we won't apply the patch. After all the armor header is a different layer and could also be applied or removed by other software or tools. The integrity of an OpenPGP message does not depend on its concrete outer encoding.
For someone who considers the rejection is the requirement of the spec., here is a change:
Here is a revised patch (hopefully the last one):
Nov 10 2025
We can use:
_("Wrongly armored signature\n"));Taking over revision to close it as done.
Taking over revision because it's obsolete (gpgmepp 2.x requires C++17) and I want to close it.
Taking over revision because it's obsolete (gpgmepp 2.x uses cmake/ECM to generate the export file) and I want to close it.