Ok with me. setting this to resolved, then.
- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
Feed Advanced Search
Advanced Search
Advanced Search
Nov 8 2024
Nov 8 2024
• ebo moved T7364: Kleopatra: Crash on Quit from Restricted Project Column to Restricted Project Column on the Restricted Project board.
• ebo moved T6091: Kleopatra: "Cancel" in the password dialog of "Print secret key" has no effect from Restricted Project Column to Restricted Project Column on the Restricted Project board.
• ebo moved T6354: All VSD and GPD binaries need a proper product name on Windows. from Restricted Project Column to Restricted Project Column on the Restricted Project board.
• ebo removed a project from T7216: Kleopatra: Integrate "disabled" feature from gpg: Restricted Project.
• ebo closed T7217: Kleopatra: Create an appearance filter for the "disabled" status, a subtask of T7216: Kleopatra: Integrate "disabled" feature from gpg, as Resolved.
• ebo updated the task description for T7217: Kleopatra: Create an appearance filter for the "disabled" status.
• ebo moved T7217: Kleopatra: Create an appearance filter for the "disabled" status from Restricted Project Column to Restricted Project Column on the Restricted Project board.
keep in mind https://dev.gnupg.org/T7217#193778 when tackling this task
• ebo changed the status of T7296: Kleopatra: Change filters "All certificates" etc. so that they do not include disabled ones, a subtask of T7216: Kleopatra: Integrate "disabled" feature from gpg, from Open to Testing.
• ebo changed the status of T7296: Kleopatra: Change filters "All certificates" etc. so that they do not include disabled ones from Open to Testing.
• ebo moved T7296: Kleopatra: Change filters "All certificates" etc. so that they do not include disabled ones from Restricted Project Column to Restricted Project Column on the Restricted Project board.
I like it better than the very long tool tip.
• ebo moved T7234: Kleopatra: add disable/enable certificate in context menu from WiP to Backlog on the vsd33 board.
• ebo moved T7234: Kleopatra: add disable/enable certificate in context menu from Restricted Project Column to Restricted Project Column on the Restricted Project board.
• TobiasFella added a comment to T7217: Kleopatra: Create an appearance filter for the "disabled" status.
Testing the removal of the appearance flag from this filter leads to this situation:
• ebo added a comment to T7296: Kleopatra: Change filters "All certificates" etc. so that they do not include disabled ones.
Hm, probably I would be for the html-tags, then. Is there an example where one could see how narrow tool tips really get with that option?
• ikloecker added a comment to T7296: Kleopatra: Change filters "All certificates" etc. so that they do not include disabled ones.
We shouldn't have to add explicit line breaks. Explicit line breaks will lead to bad formatting (German: Flattersatz) for people who use huge font sizes (a11y!) and Qt will wrap long tool tips so that they won't become wider than the screen. Alternatively, we wrap the tool tips (in the code that sets the tool tips) into <html> tags. Then (for whatever reason) Qt will make the tool tips much narrower. (Some people think too narrow, but we have to die one death.)
• ebo changed the status of T7217: Kleopatra: Create an appearance filter for the "disabled" status from Testing to Open.
• ebo changed the status of T7217: Kleopatra: Create an appearance filter for the "disabled" status, a subtask of T7216: Kleopatra: Integrate "disabled" feature from gpg, from Testing to Open.
• ebo changed the status of T7296: Kleopatra: Change filters "All certificates" etc. so that they do not include disabled ones, a subtask of T7216: Kleopatra: Integrate "disabled" feature from gpg, from Testing to Open.
• ebo changed the status of T7296: Kleopatra: Change filters "All certificates" etc. so that they do not include disabled ones from Testing to Open.
setting this to open for the small fix in the tooltip.
I suggest as new text:
"Disabled certificates are not offered when selecting a certificate to sign with or to encrypt for.\nThey are not shown in the certificate list with most filters."
And I think there should be an additional newline somewhere, as I was shown a much too long tool tip. The German text is not that much longer…
Removing the appearance filter won't fix own disabled certificates not being bold; the problem here is that the "My certificates" filter doesn't trigger at all anymore for disabled certificates
• TobiasFella added a comment to T7217: Kleopatra: Create an appearance filter for the "disabled" status.
Agree with removing the appearance filter
• ebo moved T7234: Kleopatra: add disable/enable certificate in context menu from Restricted Project Column to Restricted Project Column on the Restricted Project board.
Yeah. so lets ditch that appearance filter. But that's for ticket T7217. So I'm setting this ticket to done for 4win.
Nov 7 2024
Nov 7 2024
You mean that a disabled certificate with secret key isn't listed with bold font? That's probably because we have an appearance filter for disabled certificates which takes precedence.
• ikloecker added a comment to T7217: Kleopatra: Create an appearance filter for the "disabled" status.
I agree that it doesn't make sense anymore because we never show disabled and not-disabled certificates next to each other.
• ebo added a comment to T7296: Kleopatra: Change filters "All certificates" etc. so that they do not include disabled ones.
Gpg4win-Beta-70:
Looks ok.
Gpg4win-Beta-70:
There is an appearance filter for disabled certificates now.
Though I wonder if it is really necessary / useful, as we now have regular filters, too. I would have thought we only need the regular filters. I think the appearance filter was to be a stopgap as we did not want to touch the filters at the time when this ticket was created.
What do you say?
• ebo closed T7089: Kleopatra: show "disabled" status, a subtask of T7216: Kleopatra: Integrate "disabled" feature from gpg, as Resolved.
Gpg4win-Beta-70:
All 4 items in the task description are realized as described.
gpg4win-Beta-70: works.
I disabled a certificate, it was not shown anymore in the "all" view. Change to the "Disabled" filter and enabled it again -> it shows again with the "All" filter.
Disabling a private certificate does not allow it for signing and not for encrypting to it. It is also not offered for these any more.
But verifying files which were signed by it works.
• ebo added a comment to T7332: Kleopatra: Initial keylisting sometimes fails or hangs for some seconds.
I managed to get the same "loading certificate" message several times in a row on this test instance by stopping and starting Kleopatra in a row twice. After removing the Signature Card 2.0 this did not happen again in 5-6 tries, although I collected 2 lingering listing processes again (not both started on the same startup). Even import of a X.509 certificate worked.
• ebo added a comment to T7332: Kleopatra: Initial keylisting sometimes fails or hangs for some seconds.
Next I managed to have one gpg and one gpgsm process each left over from the last execution of Kleopatra.
After starting Kleopatra new anyway, again "loading certificate cache" and an additional pair of gpg and gpgsm listing processes start.
• ebo added a comment to T7332: Kleopatra: Initial keylisting sometimes fails or hangs for some seconds.
Had a occurrence of the never ending "loading certificate cache" issue again.
There was a leftover gpgsm process from the previous tests (although Kleopatra warned when I closed it, that processes still running in the background were there and would be aborted).
• werner added a comment to T7379: Kleopatra: Learning certificates of Signature v2.0 card fails if a Yubikey is plugged in as well.
In T7379#193696, @ikloecker wrote:I assume by "do such things in the background" you mean that GnuPG should do this automatically in the background.
• gniibe added a comment to T7379: Kleopatra: Learning certificates of Signature v2.0 card fails if a Yubikey is plugged in as well.
SCD SERIALNO serialno can move the first card in the list in scdaemon.
• ikloecker added a comment to T7379: Kleopatra: Learning certificates of Signature v2.0 card fails if a Yubikey is plugged in as well.
I assume by "do such things in the background" you mean that GnuPG should do this automatically in the background.
• gniibe added a comment to T7379: Kleopatra: Learning certificates of Signature v2.0 card fails if a Yubikey is plugged in as well.
@ikloecker Using scdaemon with multiple cards, it is a connection which holds the card.
• ebo added a project to T7378: Kleopatra: loading X.509 certificate from Signature card hangs: Restricted Project.
• ebo removed a project from T6172: Kleopatra: Crash when pulling card during key generation: Restricted Project.
Support for NKS (Telesec NetKey card and Signature card v2, both based on TCOS) is very old and predates the support for multiple applications. They are also not as well separated as with Yubikey applications. Thus the auto switching between the NKS app and the SigG app.
• werner closed T7152: gpgme: Support import options, a subtask of T7150: Kleopatra: Import only public keys from WKD, as Resolved.
@ikloecker Thank you sharing the problem. I don't know much aboug NKS card.
Nov 6 2024
Nov 6 2024
• werner added a comment to T7379: Kleopatra: Learning certificates of Signature v2.0 card fails if a Yubikey is plugged in as well.
The whole learn-card thing is more a hack than a solid way to make cards known. We should do such things in the background when a new card has been seen.
I cannot reproduce the crash anymore. I guess this was fixed with the fix of T7372: Kleopatra: Crash when unplugging smartcard while operation is in progress. I'll close this ticket as duplicate of T7372.
@ebo I suspect that we want to fix this crash also for VSD 3.3 (if it is still reproducible). I found this ticket by accident while searching for READKEY.
• ikloecker added a comment to T7379: Kleopatra: Learning certificates of Signature v2.0 card fails if a Yubikey is plugged in as well.
I haven't added any project tags because I'm not sure for which projects this is relevant. Since GnuPG 2.2 doesn't support multiple smartcards it's likely not relevant for VSD 3.3.
• ikloecker updated subscribers of T7378: Kleopatra: loading X.509 certificate from Signature card hangs.
@gniibe It seems that a keylisting (with gpg and gpgsm) interferes with a READKEY --card --no-data -- NKS-NKS3.4571 gpg-agent command and makes it hang until scdaemon is killed.
• ikloecker added a comment to T7378: Kleopatra: loading X.509 certificate from Signature card hangs.
It looks as if a keylisting interfered with a gpg-agent/scdaemon command.
48458.670390 2024/11/06 12:43:04.238 5772 kleopatra.exe org.kde.pim.kleopatra: ReaderStatusThread[GUI]::ping()
^ update of the smart cards is requested
48458.670695 2024/11/06 12:43:04.238 5772 kleopatra.exe org.kde.pim.kleopatra: ReaderStatusThread[2nd]: new iteration command= "__update__" ; nullSlot= true
^ background thread starts update of the smart cards
48459.147743 2024/11/06 12:43:04.728 5772 kleopatra.exe org.kde.pim.kleopatra: ReaderStatusThread[GUI]::ping()
^ another update of the smart cards is requested (the request is queued)
48464.804883 2024/11/06 12:43:10.393 5772 kleopatra.exe org.kde.pim.kleopatra: ReaderStatusThread: Card "89490171500022806460" with app "nks" was added 48464.805095 2024/11/06 12:43:10.393 5772 kleopatra.exe org.kde.pim.kleopatra: ReaderStatusThread: Card "D2760001240100000006154932910000" with app "openpgp" was added 48464.807483 2024/11/06 12:43:10.393 5772 kleopatra.exe org.kde.pim.kleopatra: ReaderStatusThread: Card "D2760001240100000006154932910000" with app "piv" was added
^ the background thread completed the update of the smart cards and found three card apps
48464.811286 2024/11/06 12:43:10.393 5772 kleopatra.exe org.kde.pim.kleopatra: ReaderStatusThread[2nd]: new iteration command= "__update__" ; nullSlot= true
^ background thread starts another update of the smart cards
48464.924701 2024/11/06 12:43:10.492 5772 kleopatra.exe org.kde.pim.kleopatra: ReaderStatusThread[GUI]::learnCardsCMS()
^ learn cards is requested (and queued) -> Kleopatra shows the progress overlay
48465.796319 2024/11/06 12:43:11.291 5772 kleopatra.exe org.kde.pim.libkleo: KeyCache::RefreshKeysJob start
^ a keylisting is started (OpenPGP and S/MIME)
48467.549251 2024/11/06 12:43:12.874 5772 kleopatra.exe org.kde.pim.libkleo: sendStatusLinesCommand "SCD LEARN --force" : got ( status( "READER" ) = "SCM Microsystems Inc. SPRx32 USB Smart Card Reader 0" [...] 48467.550423 2024/11/06 12:43:12.875 5772 kleopatra.exe org.kde.pim.libkleo: sendCommand "READKEY --card --no-data -- NKS-NKS3.4531" 48467.895485 2024/11/06 12:43:13.187 5772 kleopatra.exe org.kde.pim.libkleo: sendStatusLinesCommand "READKEY --card --no-data -- NKS-NKS3.4531" : got ( ) 48467.896400 2024/11/06 12:43:13.188 5772 kleopatra.exe org.kde.pim.libkleo: sendCommand "READKEY --card --no-data -- NKS-NKS3.45B1" 48468.209551 2024/11/06 12:43:13.471 5772 kleopatra.exe org.kde.pim.libkleo: sendStatusLinesCommand "READKEY --card --no-data -- NKS-NKS3.45B1" : got ( ) 48468.209660 2024/11/06 12:43:13.471 5772 kleopatra.exe org.kde.pim.libkleo: sendCommand "READKEY --card --no-data -- NKS-NKS3.4571"
^ the background thread sends multiple commands to gpg-agent to gather information about the smart cards
^ the last READKEY command seems to hang
48468.598283 2024/11/06 12:43:13.822 5772 kleopatra.exe org.kde.pim.libkleo: Kleo::KeyCache::RefreshKeysJob(0x63ccba8) RefreshKeysJob::done
^ the keylisting is done
• ikloecker moved T6091: Kleopatra: "Cancel" in the password dialog of "Print secret key" has no effect from Backlog to WiP on the vsd33 board.
Backported for VSD 3.3
• ikloecker moved T6091: Kleopatra: "Cancel" in the password dialog of "Print secret key" has no effect from Restricted Project Column to Restricted Project Column on the Restricted Project board.
Canceling the password prompt is now handled correctly, i.e. the operation is aborted without further feedback.
• ebo closed T6073: Kleopatra: Fix issues with high contrast resp. inverted color scheme as Resolved.
ok, looks good, Gpg4win-Beta-70:
• ebo closed T6073: Kleopatra: Fix issues with high contrast resp. inverted color scheme, a subtask of T5824: Kleopatra: Full accessibility support, as Resolved.
• ebo moved T7299: Kleopatra: improve readability of highlighted text from Restricted Project Column to Restricted Project Column on the Restricted Project board.
Ok, gpg4win-Beta-70. Looks like this now:
• ikloecker changed the status of T7375: Kleopatra: Print secret key operation is not terminated correctly if an empty or wrong password is entered from Open to Testing.
• ebo moved T7320: Kleopatra: Decrypting and verifying a pgp-encrypted archive fails with "no data" from WiP to QA for next release on the gpgme board.
Nov 6 2024, 10:09 AM · gpgme (gpgme 1.24.x), vsd33 (vsd-3.3.0), kleopatra, Restricted Project, Bug Report
• ebo moved T7320: Kleopatra: Decrypting and verifying a pgp-encrypted archive fails with "no data" from Restricted Project Column to Restricted Project Column on the Restricted Project board.
This works with gpg4win-beta-70.
Nov 6 2024, 10:09 AM · gpgme (gpgme 1.24.x), vsd33 (vsd-3.3.0), kleopatra, Restricted Project, Bug Report
Nov 5 2024
Nov 5 2024
• ikloecker moved T6091: Kleopatra: "Cancel" in the password dialog of "Print secret key" has no effect from WiP to Backlog on the vsd33 board.
• ikloecker moved T6091: Kleopatra: "Cancel" in the password dialog of "Print secret key" has no effect from Restricted Project Column to Restricted Project Column on the Restricted Project board.
This has also been reported at https://bugs.kde.org/show_bug.cgi?id=477798 (although there a crash occurs). Porting the command to gpgme didn't help, but the remaining problems are in gpg and/or gpgme.
• werner added a comment to T7372: Kleopatra: Crash when unplugging smartcard while operation is in progress.
Thanks.
• ikloecker changed the status of T7372: Kleopatra: Crash when unplugging smartcard while operation is in progress from Open to Testing.
Fixed and backported for VSD 3.3
• ebo triaged T7372: Kleopatra: Crash when unplugging smartcard while operation is in progress as Normal priority.
I'm now using the name "Compliance Check" for the test if no compliance is active/has been configured. I have also checked all other usages of DeVSCompliance::name() in libkleo and kleopatra to make sure it's only used if compliance is active.
Fixed and backported for VSD 3.3
• ikloecker moved T7364: Kleopatra: Crash on Quit from Restricted Project Column to Restricted Project Column on the Restricted Project board.
• ebo moved T7320: Kleopatra: Decrypting and verifying a pgp-encrypted archive fails with "no data" from Backlog to WiP on the gpgme board.
Nov 5 2024, 11:13 AM · gpgme (gpgme 1.24.x), vsd33 (vsd-3.3.0), kleopatra, Restricted Project, Bug Report
If compliance is not active, the self-test dialog now shows the test for compliance with just "?" as the test name
• ebo moved T7311: Kleopatra: Values for ValidityPeriodInDays ignored from Restricted Project Column to Restricted Project Column on the Restricted Project board.
Tested with Gpg4win-Beta-70: works for changing expiry date as well as key creation
• ebo moved T6354: All VSD and GPD binaries need a proper product name on Windows. from Backlog to WiP on the vsd33 board.
Nov 4 2024
Nov 4 2024
Looking at the Windows "Problem reports" I saw that it lists many crashes of Kleopatra since 2024-06-19. An older Kleopatra (gpg4win-4.3.2-beta15, built on 2024-04-16) does not crash on exit. The next Kleopatra (gpg4win-4.3.2-beta23, built on 2024-07-05) does crash on exit. The reports point to the libkleo DLL.
In Gpg4win-Beta-70 it looks like this (audit log is redirected):
Tested with 4win-beta-64. In the subkey tab of the details of a secret key there is now an option "Add ADSK" in the burgher menu, iff the option default-new-key-adsk is set.
• ebo moved T6072: Kleopatra: Display "gpgconf -X" from Restricted Project Column to Restricted Project Column on the Restricted Project board.
• ikloecker added a comment to T7350: Kleopatra: Don't offer "Trust root certificate" if users are not allowed to do this.
Kleopatra shows this option in GnuPG System because gpgconf --list-options gpg-agent lists this option.
• ikloecker changed the status of T7349: Kleopatra: inconsistent behavior of "Trust root certificate" from Open to Testing.
ALright, let's go with that latest version (rKLEOPATRAab32b52a6cf8)
High priority since it affects accessibility and was mentioned as problem in the accessibility reports.
This isn't really important at the moment.
Ctrl+A + Ctrl+C to copy to clipboard and Ctrl+V do paste isn't exactly super complicated for people who know how to use the clipboard. -> Low
Applied Tobias installation patch to gpg4win master (vsd33)
• ikloecker changed the status of T7349: Kleopatra: inconsistent behavior of "Trust root certificate" from Testing to Open.
We decided that Kleopatra should behave the same way as GnuPG when the user clicks "Wrong". Kleopatra should inform the user that the certificate has been marked as not trusted because of the wrong fingerprint.