The state machine in GpgSignKeyEditInteractor expects to see GET_BOOL sign_uid.okay and it should have answered with Y.
- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
Advanced Search
Apr 9 2025
The dialog between gpg and Kleopatra looks like this:
[GNUPG:] KEY_CONSIDERED FADC4675146CFAF3D86F137E1D3C5E6E3DB3C71D 0<LF> [GNUPG:] GET_LINE keyedit.prompt<LF> sign <LF> [GNUPG:] GOT_IT<LF> [GNUPG:] GET_BOOL keyedit.sign_all.okay<LF> N <LF> [GNUPG:] GOT_IT<LF> [GNUPG:] GET_LINE keyedit.prompt<LF> uid D2C00A207DC184562E41517CBC5EF7175E8535E8 <LF> [GNUPG:] GOT_IT<LF> [GNUPG:] GET_LINE keyedit.prompt<LF> uid 648AC172C3EC45F85AA2E68E46D3FEFABD1F5BD7 <LF> [GNUPG:] GOT_IT<LF> [GNUPG:] GET_LINE keyedit.prompt<LF> sign <LF> [GNUPG:] GOT_IT<LF> [GNUPG:] KEY_CONSIDERED FFDFEE2F0C8F278023284D90B0FBC8D8324859B9 0<LF> [GNUPG:] GET_BOOL sign_uid.local_promote_okay<LF> Y <LF> [GNUPG:] GOT_IT<LF> [GNUPG:] GET_BOOL sign_uid.okay<LF>
and then nothing else.
with VSD-Beta-3.3.90.10:
this is not yet in master and not included in the current testbulid
Apr 7 2025
My above comment is true for the main case described in the ticket, cancelling decryption followed by "permanently decrypt".
I see no improvement in VSD-Beta-3.3.90.6, the issue persists.
Btw: Is this maybe related to T7596: GpgOL: Draft is not decrypted after cancelling decryption once?
Apr 4 2025
with Version VS-Desktop-3.3.90.6-Beta:
Apr 3 2025
Apr 1 2025
Mar 24 2025
work/markus_montkowski/T7485
work/markus_montkowski/T5681
Mar 21 2025
In version Version VS-Desktop-3.3.0.0 a certificate imported via WKD is correctly shown as level 2 security:
Mar 20 2025
Mar 17 2025
Done.
Mar 11 2025
As this is minor anyway and does not show in kf6, I close this again
Backported for VSD 3.3.x / Gpg4win 4.4.x
Mar 10 2025
Version 4.0.0.250370 (Gpg4win-5.0.0-beta145):
This should now work on master, I will write here once this is in the next beta
Feb 28 2025
You could probably check that Kleopatra/gpgme calls gpg with the import option "only-pubkeys". For a real world test you'd have to upload a secret key to WKD.
I have no idea how to test this aside from the test done in T7146.
Feb 27 2025
No totally new install: I quit Kleopatra, then deleted %APPDATA%\kleopatra\kleopatrastaterc and %APPDATA%\gnupg and restarted Kleopatra. Then I imported the shown test certificate which has no expiry date.
I can't reproduce this. Was this with a fresh install or is it possible that there were existing column widths loaded from a state file?
Carl found some issue with this himself.
Feb 26 2025
Feb 24 2025
VSD 3.3.0:
Feb 13 2025
Feb 11 2025
Everything mentioned above was translated and is now shown that way in all three languages.
Feb 3 2025
Tested encryption (+ signature) via Kleopatra with a 3 GB file (random data) with:
- VSD 3.2.4: ~ 5:20
- VSD 3.3.0: ~ 4:25
- command line; ~4:25
Jan 31 2025
21f7ad563d9b was not backported to gnupg 2.2, so this can't be done yet
Jan 30 2025
It's missing a check for the required gpg-2.2 version. I will add that
Jan 29 2025
Jan 23 2025
In contrast to Gpg4win 4.4 in VSD 3.3.0 dragging a plain file onto Kleopatra will return an error. Decryption and importing certificates works, though.
Jan 22 2025
In VS-Desktop-3.2.94.481-Beta the feature is not available in the context menu in Kleopatra.
So in VSD 3.3.0 this will be missing. What works is disable/enable on the command line and Kleopatra will then not list a disabled certificate with most filters.
Jan 21 2025
With VS-Desktop-3.2.94.481-Beta:
If an Ldap NtdsKeyserver is configured, there is now no warning on the upload. But the success message is wrong or at least not right:
"OpenPGP certificates exported successfully." Made me think I did mistakenly choose something other than "Publish on server".
And the menu entry is "Publish on Server..." so there has to be another window before action is taken.
Jan 20 2025
Jan 17 2025
In VSD Beta-481 the translation is missing
Jan 16 2025
works with VS-Desktop-3.2.94.481-Beta
VS-Desktop-3.2.94.481-Beta: works, if no kleopatragroupsrc is found at the new location, the one at the old location is used.
This is only relevant in the case that after the update to this version GpgOL is used without starting Kleopatra in between.
Because when Kleopatra is started it will copy the kleopatragroupsrc from the old location to the new one. After that the config file in the old location is ignored.
works in VS-Desktop-3.2.94.481-Beta. The "Trust Root Certificate" is no longer offered in the context menu.
works in VS-Desktop-3.2.94.481-Beta
works in VS-Desktop-3.2.94.481-Beta, the certificate for the newly generated key has the default expiry date of 3 years there.
Jan 13 2025
Works with VSD-beta-478
Works with VSD-beta-478
Works with VSD-beta-478
I have seen this when doing the following:
Works with VSD-beta-478
Works with VSD-beta-478
works fine with VSD-beta-478
"Tested" with VSD-beta-478, looks as expected
Works with VSD-beta-478
Fixed. No backport needed because we use gpg4win-tools master also for VSD 3.3
@werner: gpg4win-tools needs to be updated in gpg4win master.
works with VSD-beta-478
works with VSD-beta-478
VSD-beta-478: works fine
Works fine in VSD-beta-478
Jan 10 2025
The file path of the group config file in line
https://dev.gnupg.org/source/g4wt/browse/master/src/resolver/resolver.cpp$171
has to be changed to the one in line
https://dev.gnupg.org/source/kleo/browse/master/src/kleopatraapplication.cpp$355 .
It may be best to add a function returning the default path to libkleo. Or to use the new path by default if no other path is passed to the c'tor of KeyGroupConfig. It's unfortunate that the path is GNUPGHOME/kleopatra/kleopatragroupsrc although the groups are also used by GpgOL and they should likely also be supported/used by KMail.
Jan 9 2025
Backported for VSD 3.3
Tested with the VSD beta 478. Works