Bug 493000 - Impossible to delete a certificate due to a *CMS backend: Ambiguous name* error
Summary: Impossible to delete a certificate due to a *CMS backend: Ambiguous name* error
Status: RESOLVED WORKSFORME
Alias: None
Product: kleopatra
Classification: Applications
Component: general (other bugs)
Version First Reported In: 3.2.0.240502
Platform: Manjaro Linux
: NOR minor
Target Milestone: ---
Assignee: Andre Heinecke
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2024-09-12 05:10 UTC by GaspartameK
Modified: 2024-10-16 20:27 UTC (History)
4 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments
The error with it's dialog box (113.53 KB, image/png)
2024-09-12 05:10 UTC, GaspartameK
Details

Note You need to log in before you can comment on or make changes to this bug.
Description GaspartameK 2024-09-12 05:10:00 UTC
Created attachment 173572 [details]
The error with it's dialog box

SUMMARY


STEPS TO REPRODUCE
1. On my plasma manjaro computer, I went in /etc/ssl/certs and I opened /etc/ssl/certs/Go_Daddy_Root_Certificate_Authority_-_G2.pem (with kleopatra as default).
2. It asked me if I trusted the certificate, I realised it was going to add it to kleopatra while I just wanted to know what was in it, so I clicked on cancel. Several times.
3. Seeing the certificate nevertheless in kleopatra, I tried to delete it with right-click, delete

OBSERVED RESULT

The certificate was added, and now it won't delete (from kleopatra I mean, I hope it shouldn't delete the file without warning against it).

EXPECTED RESULT

1. When I clicked on cancel, the certificate maybe shoudn't have been added. (I didn't expected it, but maybe it is wanted behaviour)
2. The key should be deleted from Kleopatra when asked.

SOFTWARE/OS VERSIONS
Windows: 
macOS: 
(available in the Info Center app, or by running `kinfo` in a terminal window)
Linux/KDE Plasma: 6.6.47-1-MANJARO (64-bit)
KDE Plasma Version: 6.0.5
KDE Frameworks Version: 6.5.0
Qt Version: 6.7.2

ADDITIONAL INFORMATION
Comment 1 Ingo Klöcker 2024-10-14 20:49:14 UTC
There is no confirmation for the import. The import has already happened when you are asked whether you trust the certificate.

I tried to reproduce the problem using Kleopatra 3.2.0.240802 (with GnuPG 2.4.5 on openSUSE Tumbleweed), but I could delete the certificate without problems after importing /etc/ssl/certs/Go_Daddy_Root_Certificate_Authority_-_G2.pem.

What version of GnuPG is Kleopatra using? (see Help -> About Kleopatra)
Comment 2 GaspartameK 2024-10-15 21:00:16 UTC
(In reply to Ingo Klöcker from comment #1)
> There is no confirmation for the import. The import has already happened
> when you are asked whether you trust the certificate.
> 
> I tried to reproduce the problem using Kleopatra 3.2.0.240802 (with GnuPG
> 2.4.5 on openSUSE Tumbleweed), but I could delete the certificate without
> problems after importing
> /etc/ssl/certs/Go_Daddy_Root_Certificate_Authority_-_G2.pem.
> 
> What version of GnuPG is Kleopatra using? (see Help -> About Kleopatra)

I'm using Kleopatra 3.2.0.240801 (24.08.1)
In the about tab :
  Uses:
    - GnuPG 2.4.5
    - Libcrypt 1.11.0-unknown
In the Components tab :
  KDE Frameworks
    Version 6.6.0
  Qt
    Version 6.7.2 (built against 6.7.2)
  The xcb windowing system
Comment 3 GaspartameK 2024-10-15 21:03:51 UTC
In fact, after closing completely Kleopatra and restarting it, the certificate is not there anymore. And then after reimporting it, when I try to delete it the error doesn't show, and the certificate disappear again only after I press F5.
Comment 4 Ingo Klöcker 2024-10-16 20:27:28 UTC
(In reply to GaspartameK from comment #3)
> In fact, after closing completely Kleopatra and restarting it, the
> certificate is not there anymore. And then after reimporting it, when I try
> to delete it the error doesn't show, and the certificate disappear again
> only after I press F5.

That one needs to press F5 to make a deleted S/MIME certificate disappear has been fixed recently (https://dev.gnupg.org/T7318). The fix will be in 3.2.0.240803 (24.08.3).

Since you cannot reproduce the original bug anymore, I'll close this report. Reopen it when the bug occurs again. Thanks for taking the time to report the issue!