Mon, Sep 30
Jun 28 2019
Feb 4 2019
I don't see it as a priority right now. We should keep it in mind for T3811 .
Jan 24 2019
The problem only occurs with the gtk platformtheme.
Aug 22 2018
Hi, gpg4o does not send PGP/MIME (the proper format for including attachments and no encoding problems). As such it does not have the Problem described here. You can use "Send PGP Mails without attachments as PGP/Inline" in the options of GpgOL to have something similar. This will also work for Kopano.
Jul 24 2018
I can't reproduce this. When I make Dirmngr offline I correctly get a No CRL known error. So it must be something different.
Jul 18 2018
The problem with mnemonics based on words is that they are language dependent and only a small part of the world is fluent enough in English to spell/use them correctly. Thus anything based on ICAO spelling (Alfa, Bravo,...) is a better choice than arbitrary words from one language. Even if that meas to write down a longer string. A CRC is of course very useful.
It would be great if this feature were implemented with a mnemonic code option, with a built in checksum, as described in bip39: https://github.com/bitcoin/bips/blob/master/bip-0039.mediawiki Using the same bip39 standard (and perhaps others, as alluded to in T3497) would also improve compatibility with existing crypto key storage devices (i.e. cryptocurrency wallets used as smart cards).
Jun 26 2018
Good news! :)
Just as a note as you were the first to report this: I've finally found a solution. In the next version it will be possible to move around crypto mails. Hopefully your wife can then use GpgOL :-)
A new Idea which I'll have to test:
Register an event handler for each folder in which a decrypted item is read. "Mailitem->parent" In this event handler listen to the beforeitemmove event. In that event then close the mail / discard the decrypted contents.
May 7 2018
As I link this Ticket often when talking about this limitation. Here is a short animation to show what is meant by moving but not opening a mail:
Apr 20 2018
I got an Idea how to improve the situation here. But its very complex and might break Outlook even for unencrypted mails. So it's very invasive.
Apr 19 2018
Apr 3 2018
@dkg thanks for the link.
Mar 27 2018
The severe delay caused by check-trustdb continues to cause problems elsewhere in the ecosystem. It would be great to try to address this so that GnuPG was more responsive for routine tasks like importing a single key.
Mar 18 2018
I experienced this issue today while cleaning up my keychain. I recently switched from pgp to tofu+pgp trustmodel and this caused me the above error when doing:
Mar 2 2018
Nov 28 2017
Can't reproduce and there were tons of fixes to gpgol in the meantime -> invalid.
Nov 27 2017
I'm closing this as a duplicate of T3459 even if this bug is older we used it to discuss side topics.
Hi, sorry this is a known issue. To quote the README:
Nov 14 2017
Sep 7 2017
Sep 1 2017
Ok, I implemented this for Inline messages. The resulting armored literal data packet is encrypted as PGP/MIME message. I'm not sure this is what we want.
Aug 23 2017
Is this even something that we can control?
Aug 14 2017
Ok. Lets put this problem back until we have a possibility to encrypt through filters so that can maybe enable this just for some kind of reenecrypt workflow.
Jul 31 2017
I can't reproduce this I even tried to completly remove TCP/IP from the DCOM Protocols. No problems.
Jul 27 2017
As others have pointed out, we don't implement the Bell-Lapadula model.
Well, iff we implement that for gpg we also need to implement it for gpgsm.
Jul 26 2017
Jul 24 2017
A decision must be made what the desired behaviour should be.
Jul 19 2017
T3252 is about meta data for each key.
Jul 17 2017
Jul 13 2017
I am closing this, because this particular change was rejected. Eventually libtool might get updated on its own merits, so no need to track this here.
The revert was done in 7195b94345b0bb937477dc47fc5ec27fb108a099.
Jul 10 2017
Jul 4 2017
FWIW, OpenPGP's S2K and PKCS's PBKDF2 are very similar and don't make a difference except that we have calibration code for S2K in gpg-agent.
Jun 29 2017
The change werner mentioned previously is eaba8d58acda66f428870794115cb22c2590ec5e, but this is based on Elgamal. RFC4880 since then specified S2K, and better approaches are available, too (at least PBKDF2 is in libgcrypt). These could be used with HKDF for RSA and other asymmetric key generation methods.