Hopefully fixed for good.
Feed All Stories
Nov 15 2023
Nov 15 2023
• ikloecker changed the status of T6584: Kleopatra / Gpgtar: Cancel on encrypt leaves a broken archive behind from Open to Testing.
• ikloecker committed rM618fea9e2006: qt: On Windows, use UTF-8 when logging the error text (authored by • ikloecker).
qt: On Windows, use UTF-8 when logging the error text
• ikloecker committed rM278f92b189ec: qt: Remove left-over partial files more persistently (authored by • ikloecker).
qt: Remove left-over partial files more persistently
• aheinecke moved T4066: Kleopatra, performance: Use icons as a resource from Backlog to QA on the vsd32 board.
We decided that this is an invalid issue most likely related to the test cert / test card. We have tests done with real world Signature cards with brainpool and they worked.
• aheinecke changed the status of T6344: Kleopatra, GPG: AboutData ctor on Windows takes too long from Testing to Open.
Welcomewidget is broken now: Welcome to Kleopatra: [Kleopatra] instead of showing the version.
• aheinecke changed the status of T6344: Kleopatra, GPG: AboutData ctor on Windows takes too long, a subtask of T6259: Kleopatra: Improve startup performance , from Testing to Open.
• ebo moved T6676: GgpOL: Signed Mails from Filesystem are modified when opened from Restricted Project Column to Restricted Project Column on the Restricted Project board.
• ebo moved T6604: GpgOL: MIME parameters provided with "*=" instead of just "=" are not parsed - Resulting in hidden attachments from Restricted Project Column to Restricted Project Column on the Restricted Project board.
• ebo moved T6332: GPG: Extend / rework "is_file_compressed" from Restricted Project Column to Restricted Project Column on the Restricted Project board.
• aheinecke added a comment to T6820: SCD: Invalid ID when decrypting with brainpool key .
Screenshot with details about the key in question. It might be a weird one since it does not have usage flags set. But this is the only brainpool key on my test card and it shows up for encryption in Kleopatra.
• ebo moved T6261: Kleopatra / QGPGME: Use --no-auto-check-trustdb for initial keylisting from Restricted Project Column to Restricted Project Column on the Restricted Project board.
• ebo moved T6201: Kleopatra: Disable unusable actions in certificate details for remote keys from Restricted Project Column to Restricted Project Column on the Restricted Project board.
• werner added a comment to T6820: SCD: Invalid ID when decrypting with brainpool key .
You can't decrypt using the Esign application on such a card. Please provide more information off-tracker.
• ebo moved T6790: GpgOL: Missing icons in keyresolver from Restricted Project Column to Restricted Project Column on the Restricted Project board.
• ebo moved T6277: Kleopatra: Support NetKey v15 from Restricted Project Column to Restricted Project Column on the Restricted Project board.
I set the pin on my card, so this still works in kleo :)
When I had not set the pin, pinentry informed me correctly that the pin was not yet set and I got as an error "Nutzungsvorraussetzungen nicht erfüllt" so this works nicely.
With faked system time I was able to sign with a vs-nfd compliant brainpool key.
• ebo moved T6344: Kleopatra, GPG: AboutData ctor on Windows takes too long from Backlog to QA on the vsd32 board.
This is already in 3.1.26. I only wasn't sure if I should make another ticket for remaining issues before closing that is the only reason why it is still open
• ebo moved T6721: QGpgME: Create archive as .part and rename on successful creation from QA to WiP on the vsd32 board.
Nov 15 2023, 10:36 AM · gnupg24 (gnupg-2.4.4), gnupg22 (gnupg-2.2.42), vsd32 (vsd-3.2.0), S/MIME, Restricted Project
• ebo moved T6754: Kleopatra: wrong success message for changing validity in case of not available card key from Backlog to QA on the vsd32 board.
• ebo added a comment to T6277: Kleopatra: Support NetKey v15.
Well, the above mentioned cards are all with expired certificates and I did not use the cards. I could only check if some info about the certificates on the card is displayed in the smart card tab.
Is this is all necessary for the test if Kleopatra "accepts" those cards? That their contends are displayed? In that case you might count the ticket as resolved.
But I'm lacking a representative sample of testcards and don't feel comfortable declaring that all Netkey v15 cards are accepted on such cursory tests.
• aheinecke moved T6480: Kleopatra: Change visibility of advanced options in the certification dialog from Backlog to QA on the vsd32 board.
So the last thing to do here would be an NTBTLS release? Then we should make sure not to forget to do that?
This would of course all be also in vsd32
So if you tested this with the signature cards this can be resolved? My signature card still has the nullpin. I should probably set that to test it myself but if you have one and tested this why not resolved?
• aheinecke added a comment to T4066: Kleopatra, performance: Use icons as a resource.
The whole part with colorschemes and high contrast mode and dark mode I have already tested.
• aheinecke changed the status of T4066: Kleopatra, performance: Use icons as a resource, a subtask of T6259: Kleopatra: Improve startup performance , from Open to Testing.
• aheinecke changed the status of T4066: Kleopatra, performance: Use icons as a resource from Open to Testing.
For testing I would take procmon, filter for Kleopatra start Kleopatra from an older version. Save the log, take the current beta277 kleopatra and do the same and compare the number of lines in the log.
• aheinecke changed the status of T6259: Kleopatra: Improve startup performance from Open to Testing.
Same as with T6344 this is already in beta-277
• aheinecke changed the status of T6344: Kleopatra, GPG: AboutData ctor on Windows takes too long, a subtask of T6259: Kleopatra: Improve startup performance , from Open to Testing.
• aheinecke changed the status of T6344: Kleopatra, GPG: AboutData ctor on Windows takes too long from Open to Testing.
This is in vsd32. But I am not sure what to test here. You could take a previous beta and look at the startup timining debug output which says "mainwindow shown" and compare that to beta-277? The mainwindow shown timing debug output is not part of 3.1.26
• aheinecke added a project to T6480: Kleopatra: Change visibility of advanced options in the certification dialog: vsd32.
This is in VSD32-beta277
• werner moved T6802: Trying to sign with a brainpool X509 key results in non-compliance error from QA to gnupg-2.4.4 on the gnupg24 board.
• werner added a comment to T6802: Trying to sign with a brainpool X509 key results in non-compliance error.
Testing in 2.4 will not be easy because it requires code modification just for testing. However, de-vs is not supported by 2.4 and the greater plan is to get 2.6 approved for de-vs.
yes, see it in VS-Desktop-3.1.90.277-Beta
• ebo moved T6802: Trying to sign with a brainpool X509 key results in non-compliance error from QA to gnupg-2.2.42 on the gnupg22 board.
• ebo removed a project from T6802: Trying to sign with a brainpool X509 key results in non-compliance error: vsd32.
works in VS-Desktop-3.1.90.277-Beta
doc: Fix for e.g. and i.e.
mlaurent committed rLIBKLEOfd7d96f92ec9: GIT_SILENT: Use new .gitlab.yml format (authored by mlaurent).
GIT_SILENT: Use new .gitlab.yml format
• gniibe committed rEe31d65345bcb: yat2m: Implement @item handling with @table item specification. (authored by • gniibe).
yat2m: Implement @item handling with @table item specification.
• gniibe committed rEcfb1871240c4: yat2m: Also handle @file treating '-' as minus. (authored by • gniibe).
yat2m: Also handle @file treating '-' as minus.
• gniibe changed the status of T6674: doc: U+2010 HYPHEN vs. U+002D HYPHEN-MINUS for man pages from Open to Testing.
@item handling with @table has been pushed.
l10n daemon script <scripty@kde.org> committed rLIBKLEO2b2f6c5f9920: GIT_SILENT Sync po/docbooks with svn (authored by l10n daemon script <scripty@kde.org>).
GIT_SILENT Sync po/docbooks with svn
l10n daemon script <scripty@kde.org> committed rKLEOPATRA4d6dc6c93486: GIT_SILENT Sync po/docbooks with svn (authored by l10n daemon script <scripty@kde.org>).
GIT_SILENT Sync po/docbooks with svn
l10n daemon script <scripty@kde.org> committed rKLEOPATRA92318653eea1: GIT_SILENT Sync po/docbooks with svn (authored by l10n daemon script <scripty@kde.org>).
GIT_SILENT Sync po/docbooks with svn
l10n daemon script <scripty@kde.org> committed rLIBKLEO04cfbd051fb1: GIT_SILENT Sync po/docbooks with svn (authored by l10n daemon script <scripty@kde.org>).
GIT_SILENT Sync po/docbooks with svn
RSA improvement is not that worth now.
OK. When we will need and do, I will open new one.
• gniibe closed T3269: (Constant-time) modular reduction, a subtask of T3264: Possible RSA improvement, as Resolved.
• gniibe closed T6539: The digest&sign/verify API with SHAKE-class digests does not work as Resolved.
The fix is in 1.10.3.
Fix is in 1.10.3.
Nov 14 2023
Nov 14 2023
GIT_SILENT: Use new .gitlab.yml format
• werner added a comment to T6818: GPGME: Finding gpgme-w32-spawn.exe should be optional.
I'd prefer to not use the spawn helper at all. All currrent Windows versions allow to decide which handles are to be inherited and thus there is no more need for the helper.
• ebo moved T6742: Kleopatra: Encryption to group with expired key fails with unexpected message from QA to vsd-3.2.0 on the vsd32 board.
• ebo closed T6742: Kleopatra: Encryption to group with expired key fails with unexpected message as Resolved.
ok, opened T6819 for the separate button.
The rest is ok, I think. As long as we display keypairs in a single entry, it can not be helped that they may appear valid in the certificate list but are invalid for signing or encryption subkeys.
We display that here correct for the respective contexts.
Therefore closing,
• ebo moved T6788: Kleopatra: Signing with expired signing subkey shouldn't be possible from QA to vsd-3.2.0 on the vsd32 board.
• ebo closed T6788: Kleopatra: Signing with expired signing subkey shouldn't be possible as Resolved.
works as advertised, VS-Desktop-3.1.90.277-Beta
• aheinecke triaged T6818: GPGME: Finding gpgme-w32-spawn.exe should be optional as Normal priority.
• werner changed the status of T6654: gpgsm: p12 passphrase visible in debug output from Open to Testing.
Nov 14 2023, 3:10 PM · gnupg24 (gnupg-2.4.4), gnupg22 (gnupg-2.2.42), vsd32 (vsd-3.2.0), S/MIME, Restricted Project
• werner committed rGdef8f5f3d28b: gpg,gpgsm: Hide password in debug output also for asked passwords. (authored by • werner).
gpg,gpgsm: Hide password in debug output also for asked passwords.
• werner committed rGcdc28c59fe5d: gpg,gpgsm: Hide password in debug output also for asked passwords. (authored by • werner).
gpg,gpgsm: Hide password in debug output also for asked passwords.
swdb: Libgcrypt 1.10.3
• werner changed the status of T6654: gpgsm: p12 passphrase visible in debug output from Testing to Open.
Nov 14 2023, 2:38 PM · gnupg24 (gnupg-2.4.4), gnupg22 (gnupg-2.2.42), vsd32 (vsd-3.2.0), S/MIME, Restricted Project
• aheinecke updated subscribers of T6654: gpgsm: p12 passphrase visible in debug output.
Sorry @ebo tested this on Windows with 2.2. I myself should have tested it since the test is trivial and only took me about 30 seconds to type. Similar to T6701 this should have never reached the QA stage. I am including myself now that we have someone for QA that I test my own changes less. We need to talk / think about that in our whole team. We developers should test more before sending an issue into QA.
Nov 14 2023, 2:32 PM · gnupg24 (gnupg-2.4.4), gnupg22 (gnupg-2.2.42), vsd32 (vsd-3.2.0), S/MIME, Restricted Project
svuorela committed rGPGPASSb3277fcfbb4c: We shouldn't do native paths; forward slashes all the way (authored by svuorela).
We shouldn't do native paths; forward slashes all the way
Try add CI
• ikloecker added a comment to T6742: Kleopatra: Encryption to group with expired key fails with unexpected message.
What about the second part of https://dev.gnupg.org/T6742#176528? Should I make a separate a11y ticket for that with low prio?
• ikloecker committed rM77e982579cca: core: Preserve more specific existing failure code (authored by • ikloecker).
core: Preserve more specific existing failure code
• aheinecke committed rO48fee63649d7: Do not delete input after sign & encrypt (authored by • aheinecke).
Do not delete input after sign & encrypt
• ikloecker changed the status of T6575: gpgtar: General Error is emitted instead of more specific error codes from Open to Testing.
• ikloecker renamed T6575: gpgtar: General Error is emitted instead of more specific error codes from gpgtar: General Error is emitted instead of more specific error codes when only signing to gpgtar: General Error is emitted instead of more specific error codes.
• aheinecke changed the status of T6701: GpgOL: Use GPGME_ENCRYPT_ALWAYS_TRUST from Open to Testing.
Since I did not have a valid signing cert on that dev keyring I only tested with encrypt,...
Auto delete files on windows
• werner moved T3269: (Constant-time) modular reduction from For 1.10 to Backlog on the libgcrypt board.
@gniibe: This is a pretty old bug; given all the changes of the last year, should we close it now?
• werner closed T4873: Enable AES GCM in FIPS mode, a subtask of T5870: libgcrypt: AEAD API for FIPS 140 (in future), as Resolved.
• ikloecker moved T6575: gpgtar: General Error is emitted instead of more specific error codes from Backlog to WiP on the vsd32 board.
• ikloecker moved T6575: gpgtar: General Error is emitted instead of more specific error codes from Backlog to WiP on the gpgme board.
• ikloecker moved T6575: gpgtar: General Error is emitted instead of more specific error codes from Restricted Project Column to Restricted Project Column on the Restricted Project board.
• werner moved T6217: sha3: wrong results for large inputs from Backlog to For 1.10 on the libgcrypt board.
Auto delete files on windows
Auto delete files on windows
Auto delete files on windows
Auto delete files on windows
Auto delete files on windows