Fixed in libgpg-error.

We removed assuming "OPENPGP.3" means for ssh.

Having "Use-for-ssh" flag now, experience shows that including OpenPGP.3 keys by default is not convenient.

The general functionality should work now. I looked for labels showing links and converted most of them to HtmlLabel.

Text labels that get keyboard focus are now indicated with a focus frame. It depends on the Qt style how the focus frame looks like (or whether it is drawn at all). For the Breeze style, that is used on Linux systems, I have pushed a merge request (https://invent.kde.org/plasma/breeze/-/merge_requests/229). The necessary changes will be included in the next release of KDE Plasma.

I've tried a few things now. Reinstalled Office, reinstalled GPG4win, reset Windows 11 with recovery when still worked. Nothing helped.

I've tried a few things now. Reinstalled Office, reinstalled GPG4win, reset Windows 11 with recovery when still worked. Nothing helped.

oh no

The user id list is in the wrong tab order (just before the Close button).

In T6040#159431, @Valodim wrote:

I suppose you're right, we might have crossed that bridge a while ago. Simple availability of certificate- or even signature-specific keyserver URIs just make the risks of honor-keyserver-url more obvious than before.

I suppose you're right, we might have crossed that bridge a while ago. Simple availability of certificate- or even signature-specific keyserver URIs just make the risks of honor-keyserver-url more obvious than before.

In T6040#159428, @Valodim wrote:

This is a reasonable feature, however it should be noted that this implies a fairly large metadata leak: You are essentially adding a URI to signatures that will be pinged on signature verification.

This is a reasonable feature, however it should be noted that this implies a fairly large metadata leak: You are essentially adding a URI to signatures that will be pinged on signature verification.

The change allows internal use of HMAC with shorter key.

Considering again, I concluded the patch above should be applied.
The use of SALT in HKDF may be not secret and there are valid use cases with no last or shorter salt. It's different to the use case of HMAC, where KEY is secret.

I don't see why this is a child task of T6020: the features are similar, but they don't actually impact each other in any way.

This patch can be closed, but I seem to lack the permissions to do so.

The patch has been applied as part of rPdd9f76525823: qt: Create all widgets in tab order.

ACK. P[ease add it also to 2.2.

No, unfortunatelly problem is still existing.

Even if it is only a single case (of old version of Wine), I think that it is worth to add es_fflush when writing to file.

What about rejected changes to "Key:"?

Hat sich das Problem gelöst? Bei mir tritt das seit gestern auf auf. Ich kann nichts mehr signieren oder verschlüsseln. andere Plugins habe ich deaktiviert, es beliebt trotzdem.

Some issues with the dialog:

• The user id list is in the wrong tab order (just before the Close button).
• The certificate details are not (easily/separately) accessible for screen readers. (Idea: Use read-only line edits so that they can be assigned to the labels as buddies.)
• The user id table is not accessible at all (neither the whole rows nor the individual cells).

What about rejected changes to "Key:"? Other this command would make it too easy to mess up the actual private key.