Bug 308235 - possibility to encrypt stuff with a x509 without having its issuer certificate installed
Summary: possibility to encrypt stuff with a x509 without having its issuer certificat...
Status: ASSIGNED
Alias: None
Product: kleopatra
Classification: Applications
Component: general (show other bugs)
Version: 2.1.0
Platform: unspecified Microsoft Windows
: NOR minor (vote)
Target Milestone: ---
Assignee: Emanuel Schütze
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-10-11 13:01 UTC by frederik.gelder
Modified: 2021-03-10 00:15 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
missingIssuer.png (64.57 KB, image/png)
2015-08-28 07:18 UTC, RH
Details

Note You need to log in before you can comment on or make changes to this bug.
Description frederik.gelder 2012-10-11 13:01:40 UTC
when i try to encrypt a file with a x509 cert i get the message "missing issuer certificate"
i dont want to install an issuer certificate (or cant because some companies dont give you their issuer certificates) please add some option, so i can encrypt files without an issuer certificate

Reproducible: Always

Steps to Reproduce:
1.encrypt file with x509 certificate while not having its issuer certificate
2.
3.
Actual Results:  
get message "missing issuer certificate"

Expected Results:  
messagebox which ask if i still want to encrypt, or something in the options where i can specify if i want to check for issuer certificates or not
Comment 1 Emanuel Schütze 2013-05-08 15:10:46 UTC
For using X.509 certificate you have to import the whole certificate chain and mark root certificate trustable (e.g. with 'allow mark trusted' option).

But I'll check it with current Kleopatra (and Gpg4win) if you want encrypt only.
Comment 2 RH 2015-08-28 07:18:04 UTC
Created attachment 94255 [details]
missingIssuer.png

it would really be great if that "full certificate path" requirement could be overridden.

The S/MIME standard does allow to encrypt also without the full chain being present
Comment 3 RH 2015-08-28 07:30:39 UTC
see also Bug 351881
Comment 4 RH 2015-08-30 20:51:29 UTC
see also bug 352033
Comment 5 RH 2015-08-30 21:24:40 UTC
see also Bug 352037
Comment 6 RH 2015-09-07 10:00:52 UTC
see also https://bugs.gnupg.org/gnupg/issue2091
Comment 7 Justin Zobel 2021-03-10 00:15:33 UTC
Thank you for the bug report.

As this report hasn't seen any changes in 5 years or more, we ask if you can please confirm that the issue still persists.

If this bug is no longer persisting or relevant please change the status to resolved.