- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
All Stories
Today
IIUC, it's GCC 8 which starts the support of __nonstring__ attribute.
Yesterday
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.
In T5444#146395, @werner wrote:You should anyway use --quick-gen-key.
This is still broken on 2.5.5.
Wed, Apr 16
Gpg4win is a community version and we may or may not apply Authenticode signatures. You can do that yourself, after having checked our OpenPGP release signature. You may however be interested in GnuPG Desktop, which comes with full support and also Authenticode signature.
This is resolved in the final Beta15.
Unfortunately, the attempt on my end still fails. The MSI package was successfully built; however, testing installing it on a Windows host resulted in garbled UI text and a bunch of errors.
Possibly related upstream bug:
light.exe : error LGHT0216 : An unexpected Win32 exception with error code 0x65B occurred: Function failed
Tue, Apr 15
Yes. I did only one test though, with an inline PGP mail sent with Claws.
Yes it does. I even tested it yesterday.
Looks like plain old inline PGP. Does GpgOL even support inline PGP?
POSIX specifies and requires grep -E, but only mentions egrep as old.
https://flowcrypt.com/
They use OpenPGP.js according to https://flowcrypt.com/docs/getting-started/overview/openpgp-compatibility.html
They have a cooperation with Google.