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

List:       kdepim-users
Subject:    Re: [kdepim-users] kmail and kleopatra driving me krazy
From:       Ingo =?iso-8859-1?q?Kl=F6cker?= <kloecker () kde ! org>
Date:       2010-01-25 21:33:44
Message-ID: 201001252233.47878 () thufir ! ingo-kloecker ! de
[Download RAW message or body]

[Attachment #2 (multipart/signed)]


On Monday 25 January 2010, cl@qgenuity.com wrote:
> My email provider has created its own internal certifying authority
> for the certificates used for pop3, etc. They allow you to download
> the certificate in .crt format from their ssl-protected website
> (website certified by a typical commercial CA), and tell you to
> import it into your mail program and mark it trusted.
> 
> I installed kleopatra and imported the certificate. When I went to
> certify the certificate, the option was greyed out. After hunting
> through google,-I got the tip that I should put the fingerprint of
> the X509 key into trustlist.txt, followed by a space and the letter
> "S". That appears to have done nothing.
> 
> Is there some way that I can get kmail to trust this X509
> certificate? I have gpg and gpgsm listed as available crypto
> backends. I dont want to have to go plaintext and toss out all
> security altogether.

Kleopatra (and it's backend gpg/gpgsm) store certificates used for 
encrypted/signed mail exchange.

Server certificates are stored in KDE's central certificate storage. I 
have no idea where KDE's certificate manager has gone in KDE 4. I 
suggest you try to import the certificate with Konqueror.


Regards,
Ingo

["signature.asc" (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]