- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
All Stories
May 13 2025
currently not testable. some urls in download.sh are broken (404):
Meanwhile we have some support for an empty subject but gpgsm still prints an error notice. See the T7171 for more.
I suspect there's also a bug somewhere between qt and windows involved here: The overlay is supposed to be modal to the composer window, so it shouldn't be possible to move the overlay behind the compositor. This is probably the reason why the overlay is forced to stay on top in the first place...
there are no display warnings
Thank you for the concrete test case, it helps me.
NIST has an initial public draft for KEM: https://csrc.nist.gov/pubs/sp/800/227/ipd
May 12 2025
Added the additional parenthesis and I merged it
looks good to me on gpg4win-5.0.0-beta190@win10
looks good to me on gpg4win-5.0.0-beta190@win10
on gpg4win-5.0.0-beta190@win10 (high contrast):
looks good to me on gpg4win-5.0.0-beta190@win10
looks good to me on gpg4win-5.0.0-beta190@win10
looks good to me on gpg4win-5.0.0-beta190@win10
May 11 2025
It's in 1.11.1.
Included in 1.11.1.
May 10 2025
May 9 2025
I guess
alwaysTrust ? Context::AlwaysTrust : Context::None | (encryptionFlags() & ~Context::EncryptFile)
is identical to
(alwaysTrust ? Context::AlwaysTrust : Context::None) | (encryptionFlags() & ~Context::EncryptFile)
Well it kind of works but it is a bit ugly and the encoding in the "Encrypt" message is broken:
(2) Update the documentation of default-cache-ttl zero value disabling caching.
Propagate encryption flags in other places
I don't understand why we need to remove the Context::EncryptFile flag. It seems wrong/error-prone to propagate all but one flag. The caller shouldn't have set this flag in the first place. In other words: Remove the & ~Context::EncryptFile.
There are two other methods that also take alwaysTrust as input and that should likely also propagate the other encryption flags.
I think we have another report on this in the tracker. The problem is indeed the ugly Windows time functions to print a string. Let me only remind that until a few years, Windows had the opinion that Germany uses the Westeuropäische Zeit like Portugal or the UK.