[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kdepim-users
Subject:    Re: [kdepim-users] Can't select certificate for signing in Kmail
From:       Boyan Tabakov <blade.alslayer () gmail ! com>
Date:       2006-11-13 21:01:30
Message-ID: 200611132301.45177.blade.alslayer () gmail ! com
[Download RAW message or body]

[Attachment #2 (multipart/signed)]


On 13.11.2006 21:04, Paul Kennedy wrote:
> On Wednesday 16 August 2006 14:48, Ingo Klöcker wrote:
> > On Wednesday 16 August 2006 17:52, Paul Kennedy wrote:
> > > I've imported a Thawte certificate into Kleopatra and am trying to
> > > use it to sign a message.
> > >
> > > When I try to configure Kmail to use the cert for signing, it doesn't
> > > appear in the list of certs that contain my email address. Oddly it
> > > _does_ appear in the similar list for encryption.
> > >
> > > I.e., Settings -> Configure Kmail -> Identities -> <my id> -> Modify
> > > -> Cryptography -> S/MIME Signing Certificate -> Change displays no
> > > certificates (even with the search field cleared).
> > >
> > > Going to S/MIME Encryption Certificate -> Change _does_ show the
> > > certificate I'm trying to use.
> > >
> > > The certificate is there and labelled as suitable for signing (and
> > > encryption). When I open Kleopatra and display the certificate
> > > details, it has lines like "Can be used for signing  Yes", "Can be
> > > used for encryption Yes"
> > >
> > > Importing the cert into Thunderbird produces email that appears to be
> > > properly signed.
> > >
> > > Any ideas?
> >
> > Did you follow the recent threads "KMail and certificates" and "PKCS#12
> > Certificate and KMail"? If not, then please read them in the archive.
> > In particular, make sure that your key is trusted by adding Thawte's
> > root certificate to trustlist.txt.
> >
> > Regards,
> > Ingo
>
> It took me awhile to get around to it, but I _did_ go and read the archive
> and I don't find anything that seems to apply to my situation.
>
> I have a cert (3 certs in fact) that's been imported and is marked as Valid
> by kleopatra.
>
> The same cert(s), when imported into other other MUAs, produce signed mail
> that kmail recognizes as valid.
>
> When I try to configure kmail to use one of these 3 valid certs as the
> default to sign mails, none of them appears in the list of available certs.
>
> That is to say (once again) that:
>
> 	Settings -> Configure Kmail -> Identities -> <my-id> -> Modify
> Cryptography -> S/MIME Signing Certificate -> Change
>
> Produces an empty list of certs. Removing my id from the search field
> doesn't make any additional certs visible, It's as if, in this context no
> certs are visible for selection.
>
> But:
>
> 	Settings -> Configure Kmail -> Identities -> <my-id> -> Modify
> Cryptography -> S/MIME Encryption Certificate -> Change
>
> /Does/ produce a list of the 3 certs with my name in them (as it should).
>
> The certs are all labled as suitable for use in signing (in fact that's
> pretty much all they're labeled for).
>
> Ideas?

Make sure your respective root certificate is marked as trusted. See this post 
for details:
http://cvs.gnupg.org/cgi-bin/viewcvs.cgi/trunk/doc/Notes?rev=4216 

- 
Blade hails you...

Ruling with the scythe of death you tear out philosophies apart
An ancient starwalk to merge into the stars
                                                    --Nightwish

[Attachment #5 (application/pgp-signature)]

_______________________________________________
KDE PIM users mailing list
kdepim-users@kde.org
https://mail.kde.org/mailman/listinfo/kdepim-users


[prev in list] [next in list] [prev in thread] [next in thread]