Fixed:
- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
All Stories
Apr 27 2025
Apr 26 2025
Apr 25 2025
Apr 24 2025
Thanks for the patch but I think it is better to fix this in yat2m. I created a new tag for bugs related to it.
turned out that not the flowcrypt encryption is the issue here. The cause seems to be the usage of Proofpoint "Email Warning Tags".
Apr 23 2025
This is really a minor thing and and it is actually true if you also sign something.
Apr 22 2025
BTW, fingerprints for X.509 are not well defined because you get a different one when changing the *unsigned" attributes. Not a common case but one should be aware of it.
No more octals .-)
regarding the 403: one has to try the correct page AFAIK. Didn't research which one, look in the update checker code.
doc/HACKING says it's OK to use variadic arg macros (from C99 features).
If it's OK, this patch can fix the initialization (which silences GCC 15 warnings):
Apr 21 2025
Apr 20 2025
Apr 19 2025
Good morning,
I stumbled upon this when digging through old Debian bug reports against 1.4 and checking whether they still applied to 2.4. This one really still applies.
Apr 18 2025
IIUC, it's GCC 8 which starts the support of __nonstring__ attribute.
Apr 17 2025
In any case, the actual connectivity test needs to be performed by GnuPG. Otherwise we might just test whether the Qt/KDE libraries can reach versions.gnupg.org, but not whether dirmngr can. Werner proposed something like gpg --fetch-key https://gnupg.org/index.html.
Creating a new entry with the name of an existing entry will override the existing entry without warning.
Fixed.