We decided in T7579: Kleopatra: improve menu items to remove this action. Users will instead have to mark certificates they want to update and use the Update Certificates action in the "Certificates" menu.
- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
All Stories
Today
After several gpg4win-5 betas be can set this task to resolved.
I claim this resolved given several gpg4win-5 betas.
I claim this resolved given that we had several gpg4win-5 betas and no reported problems was related to this.
The actual project we had in mind for this was more or less canceled and thus I re-prioritize this task.
Reminder mostly to self: This is about the KDF parameters. In the light of PQC composite algorithms we may want to also prepare for PQC required stuff.
There should be a workaround by using
This was release with 2.5.7.
Yesterday
Funny old bug which shows up only if you don't have any keyserver configured. Note the FIXME in the commit ;-)
In the log, we can observe duplicated lines generated by
https://dev.gnupg.org/source/gpgme/browse/master/src/posix-io.c$545
Example is like:
2025-05-19 20:16:35 gpgme[21970.55d7] _gpgme_io_spawn: check: fd[0] = 0x1c -> 0x1 2025-05-19 20:16:35 gpgme[21970.55d7] _gpgme_io_spawn: check: fd[0] = 0x1c -> 0x1
Done in 1.11.1.
Done in 1.11.1.
Done in 1.11.1.
Mon, Jun 16
Can be tested with next VSD 3.3.x build.
The only time I succeded in reproducing this was when I broke my gnupg setup and got a mix between gpg from one version and gpg-agent from another.
The question is whether any part of Qt/KF6/MTP forks another process and does not do it correctly. For example it is required that the child figures out the fds to close and then closes them and does not rely here on the parent.
Sun, Jun 15
Sat, Jun 14
Fri, Jun 13
For each part that needs to be reencrypted I create a QGpgME Encrypt Job
Do you start other process while this context is in use? If you do a fork, you need to make sure that all file descriptors are closed. How is that done?
Interesing part of the logs:
Thanks! Maybe we should add a tooltip? "Default Appearance" does not have one and I do not find this self explanatory.
Reading https://openssl-library.org/files/blog/Request_to_Extend_IETF_WGLC_for_PQ_Key_Specifications.pdf ,
seed (with "S") is included in the private-key.
The commit rC23543b6c1497: Add mldsa_compute_keygrip and let private-key include "p". works well for me.
To support Dilithium, we need to extend data handling of libgcrypt.
I propose following changes:
- internal flag of PUBKEY_FLAG_BYTE_STRING to ask opaque MPI for data to be signed/verified.
- The format of data as: (data(raw)[(flags no-prefix)](value ...)[(label ...)][(random-override ...)]): message, context, and random. Optional no-prefix flag to ask specific way of signing, controlling the internal, for Known Answer Tests (siggen).
Thu, Jun 12
In T7212#201964, @ebo wrote:Why are there 2 buttons for (probably) the same thing: "Default Appearance" and "Defaults"?
I have added the changes/patches to the vsd-3.3-branch of gpg4win
The relevant changes have been merged to the gpg4win branches of kleopatra and libkleo. We can start creating a test build
in 5.0-Beta-190
its not cleared any more in 5.0 Beta-190