- User Since
- Mar 27 2017, 4:49 PM (152 w, 1 d)
Wed, Feb 19
@Valodim probably not so much as dirmngr might behave differently and not mark hosts as dead.
Tue, Feb 18
Mon, Feb 17
- The usual
- Packaged GnuPG master for Ubuntu 19.10 and buster.
- Started working on gpgcardgui, moving kleopatra code around to libkleo to have it more usable with little dependencies.
- Problem is there that the code relies on many commands in Kleopatra so I have to decide what to take. Ultimately the commands could go into libkleo, too so that I can use them from gpg4win-tools in GpgOL.
Wed, Feb 12
Tue, Feb 11
Mon, Feb 10
- More work on "Split Sending" in GpgOL oded the idea how to do it down. I'm now focusing more on OpenPGP & S/MIME combined operations.
Thanks for the report but, but we are not developers of KMymoney, I can only offer to help the developers if they have questions but please rather report a bug at bugs.kde.org regarding that so that they can figure out what might be wrong.
Thu, Feb 6
Wed, Feb 5
I renamed the ticket so that others don't think we generally don't support Office2019 because I use it myself and it works for me.
Hi, I am not sure what you mean by "The Icon does not recognize the created certificate".
Does it show you that the mail is unsigned when you view a signed mail?
What does the tooltip of the icon say?
Thank you for the detailed report.
I remember that I tested inline content-disposition handling in Outlook without GpgOL and try to do the same handling as Outlook would handle them. But then at the very least It should be shown as an attachment and not hidden.
Fri, Jan 31
Thu, Jan 30
That means that the GnuPG Backend does not work. I do not think that the office update is the reason, me and others use GpgOL with the most recent versions of Office Pro Plus without issue.
Have you possibly modified you gnupg config files? If there is a bad value in there it would result in such an error.
Wed, Jan 29
Well thanks for reporting it ;-)
Tue, Jan 28
Mon, Jan 27
That issue was created because I am interested in that. I have a yubikey here that I wish to use productively for brainpool-256 signing, bp-512 (just for fun) encrypting and cv25519 authentication. I need to use brainpool signing and encryption subkeys for VS-NfD compliant communication and I want to be more modern then RSA ;-)
Merged into master. Thanks!
Thanks! I would merge your commits but I'll like to talk to werner tomorrow about the always adding "--with-keygrip" I also think its useful but it might have expensive internal side effects that I am not aware of.
I have difficutlty to accept that as an issue in our tracker. Somehow the GUI for Kleopatra appears to be confusing for your "Sender" which apparently is not you, correct? This results in the wrong keys selected for encryption.
With this amount of information I cannot see any path of change for our software.
Could you maybe provide a screenshot how the recipient selection looks for your user in Kleopatra, so that we can discover why it might be confusing or why the recipients key is not selected correctly?
Jan 21 2020
Thanks for the report. I have observed that the Window is sometimes opened in the background so I accept that this is an issue for Kleopatra somehow and we need to look into it. I know that your problem is a bit different but that is related.
Jan 17 2020
An updated build is available here: https://files.gpg4win.org/Beta/gpgol/2.4.6-beta3/
Jan 16 2020
Yes that is fine with me.
thanks for the report. This is definitely a sore spot and we need to look at it again. I did some experiments a while a go trying to fix this issue but so far I was unable to get to stable results so for now this is a known issue.
I'm a bit suprised that the workaround with not having the mail open does not work for you.
Is this about any special version of Symantec? As far as I knew Symantec Endpoint Security Desktop (or whatever they call it nowadays) supports reading PGP/MIME and even sending it if forced.
That error always occurs when the Exchange Server is unhappy with the structure of our PGP/MIME Mails. It has nothing to do with S/MIME, that is only because Exchange only knows about S/MIME, so our PGP/MIME Mails also claim to be S/MIME mails.
Display now looks good to me in all cases. We still keep the subject when a reply / forward is done, but that is the same as before. To do this properly I would have to actually do the protected headers sending,.. as then I could automatically flag such a message to be sent with protected headers. But that would be a new feature and I rather work on properly doing BCC sending as the next privacy enhancing feature.
Jan 13 2020
Jan 10 2020
Jan 9 2020
I'll keep this on needs triage because I don't know what the issue could be. I have a yubikey 5 at hand and just tested it with Gpg4win 3.1.11. It works without problems.
Jan 8 2020
note that it *does* sometimes hide the legacy display part, for some messages, including unfortunately-complex -- that's good! -- but maybe this points to some internal inconsistency: