- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
All Stories
Oct 7 2024
Oct 6 2024
Oct 5 2024
Oct 4 2024
Yes, gpg logs "invalid ADSK ... specified", but it doesn't emit a status error. This needs to be changed in gpg.
Tested with VS-Desktop-3.2.94.2-Beta.
Works as expected on the cli.
works for VS-Desktop-3.2.94.2-Beta (Beta for VSD 3.2.4)
Test with gpg4win-Beta-50 shows the same as described in the last comment.
tested with gpg4win-Beta-50:
works as described in https://dev.gnupg.org/T6866#179915
Test on a dedicated Windows box (T 460, i5-6300U@2.40GHz, harddisk):
VSD Version | gpg version | Load time |
3.1.26 | 2.2.41 | 1:59 |
3.2.4 beta-2 | 2.2.45 beta 25 | 0:46 |
gpg4win-Beta-50:
Columns are now displayed as expected with a fresh installation, too.
Tested with gpg4win-beta-50:
Adding a subkey works, its possible to add A, E or S subkeys with different algorithms and expiration dates.
I knew that we'd need something like D604 when I saw rM409e31458227, but then I forgot about it. :/
Looks good! Thanks!
closing this ticket as duplicate as adding and changing expiry works.
Revocation of a single subkey is not yet possible in Kleopara, though
should be fixed with D604
As we now have tabs for the subkeys this task is obsolete, really. Its useful as a parent ticket though.
Overall effect of these changes tested on a small Windows VM is only 47 -> 26 seconds. Did also tests with --kbx-buffer-size but that does not make it better than the default, either.
Porting to 2.2 was straightforward - we won't give it an extra QA run.
We won't fix that for 2.2.
Oct 3 2024
The OID is used for fingerprint computation, which complicates things.
Oct 2 2024
gpg4win 4.3.1 was with keyboxd, too. And vsd33 is only to mark that it would need to be backported for the next release (if this is a Kleopatra issue)
Given that this only happens if keyboxd is used I doubt that this is relevant for VSD 3.3.
This happens only if keyboxd is used because then Kleopatra doesn't notice any changes in GNUPGHOME and therefore doesn't run a key listing.
gpgme should handle lists correctly. In Kleopatra those options are not shown in the configuration dialog because they are GC_LEVEL_INVISIBLE, i.e. Kleopatra can read them programmatically but they are not shown to the user.
Translations of the tooltips (and names) of the filters defined in the libkleopatrarc*.desktop files have to be merged/copied manually for VSD 3.3. With rLIBKLEO2349aea7f7f3ad7d785cef644befd4bdbc9d0962 I have updated the translations to the state in master. Currently, none of the tooltips have a German translation.
Backported for VSD 3.3
Backported for VSD 3.3
Backported for VSD 3.3 (backported manually because in master the code has been moved from kleopatra to libkleo)
oh, I should have reloaded before commenting ;-)