Merged.

Merged.

Merged.

3DES is indeed an allowed cipher, so that is not a concern. Changing the cipher to something that is not allowed does not work.

In T3236#99866, @aheinecke wrote:

In T3236#99865, @justus wrote:

The whole "GnuPG System" section?

No, only the options that are marked as "advanced" by gpgconf.

Actually, Andre has some uncommitted changes that do implement the wanted behavior. AIUI those mainly needs a little fix to so that it wont break with old GPGME versions. Once merged, I will amend it further if necessary.

"aheinecke (Andre Heinecke)" <noreply@dev.gnupg.org> writes:

In T3236#99865, @justus wrote:

The whole "GnuPG System" section?

"aheinecke (Andre Heinecke)" <noreply@dev.gnupg.org> writes:

I'm not sure if this is really a thing, maybe it would be enough to just disable showing the advanced options in Kleopatra again. I only recently enabled them.

Yes, it is probably correct: the concept mockup was done a lot earlier. Whatever we have in master is most likely the current status.

The mockup in the design document shows a completely redesigned key selection dialog. I did not see anything like that currently in Kleopatra. Is that right or did I miss the new dialog somehow?

Can you please provide more information about the versions you are using?

PGP/MIME is supported since Gpg4win 2.3.

Some details of these tasks are outline in the internal concept, including mockups.

Hi,
on which platform? (You can probably compare it to a working version and see which libraries is uses there.)

This actually uses the same infrastructure.

I implemented a key filter that is used to modify the key appearances. For now I use a light green for compliant keys, and a light red for non-compliant keys. One could as well introduce an icon with the same method (i.e. it is easy to change), but aiui the icons are already used to display trust levels. Patch is pending.

I now display the compliance status d for the decryption process. Patch is pending.

Disregard my comment above. I now display the compliance status for every signature and for the decryption process.

I patched Kleopatra only to offer compliant options in the generation dialog. Patch is pending.

Relevant upstream patch submissions:

We need a more prominent visualisation for compliant keys in key selection dialog of Kleopatra. E.g. as icon.

Unfortunately, the configuration dialog does not work at all for me. It says "The shared library was not found.", but it fails to say which library was not found.

The compliance with VS is stated in the tooltip. Is that sufficient or shall we make it more prominent with a background color?

There is a tooltip saying "May be used for VS-compliant communication." for compliant keys, is that enough highlighting? Or shall we give those keys a light green background color or something?

So I started with this one because it was the easiest. To reduce message fatigue, I only display compliance information if gnupg is in co-de compliance mode.

Is this about the gui not offering e.g. the wrong algorithm or key sizes in the first place? If so, then we have to either hard-code it in kleopatra, or communicate it from gnupg. I guess at this point, we'll have to hard-code it :/

Please reopen if this is still an issue with the latest version of gpg4win.

Please reopen if it can be reproduced with a recent version of gpg4win.

https://files.gpg4win.org/Beta/current/

Unlikely

GpgOL has even been revamped 2 times since then.

Is this still an issue with the latest version?

Is this still an issue?

I don't think we can do anything about slow startup times due to anti-virus software, sorry.

Is this still an issue?

According to Wikipedia, Live Meeting was discontinued. https://en.wikipedia.org/wiki/Microsoft_Office_Live_Meeting

Is this still an issue?

Is this still an issue?

2.3.3 of gpg4win

1.4.0 of gpgol

Which version of gpgol (or Gpg4win) are you using?

We can close this. The current Master of GpgOL states that Outlook 2003 and 2007 Support is no longer maintained and we will remove support for this altogether in new versions. With current Master this issue also no longer occurs.

GpgEX is now also compiled with ASLR + DEP. I still have to check some other binaries of Gpg4win before I close this task but I no longer see it as blocking a 3.0 release where I wanted to have this included.

beta232 has some basic compliance support mainly missing is Compliance indication for crypto operations (encrypt / decrypt / sign /verify)

Emanuel please add release gpg4win 3.0 as a parent task if you think we should fix this before 3.0. I'm unsure.

I'm very sure this is no longer an issue.

Will be released with 3.0

We no longer use Kleopatra for status in our supported versions (OL >2010). So resolved.

This is fixed in gpgol master.

Accidentally marked this as resolved when I only wanted to update the status.

As a first version you can now apply profiles in Kleopatra. It also respects the default_pubkey_algo_name and shows in tooltips / certificate details if a certificate is compliant.