From: "Bo Ørsted Andresen" <bo.andresen@zlin.dk>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Getting to grips with S/MIME in Kmail
Date: Sun, 11 Jun 2006 19:58:13 +0200 [thread overview]
Message-ID: <200606111958.18042.bo.andresen@zlin.dk> (raw)
In-Reply-To: <358eca8f0606110944o684ffb4fxadb1403e727b7105@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1339 bytes --]
On Sunday 11 June 2006 18:44, Mick wrote:
> Same here. It shows:
> =======================
> Available backends:
>
> Gpg(ME)
> OpenPGP (gpg)
> S/MIME (gpgsm)
>
> Chiasmus
> Chiasmus (failed)
> =======================
This is identical to mine.
> OpenPGP seems to work a treat, but S/MIME complains of a missing backend.
I have no explanation for that. Mine doesn't complain about missing backend.
I do have an S/MIME certificate that my government has had issued for me. I
have imported it in KDE Control Center -> Security & Privacy -> Crypto ->
Your Certificates. In Kmail in Configure KMail -> Identities -> Modify ->
Cryptography it shows up when I select an S/MIME signing/encryption
certificate for my identity with the matching email address.
But until now I have never tried to actually use it in KMail. ;) When I try to
do so it gives me the following very informative error message:
"Signing failed: General error"
;)
[SNIP]
> PS. Your signature on this message is shown as an attachment called
> "noname" in Gmail gui. Some other sigs are shown as "signature.asc".
> How can one control this?
I use an OpenPGP signature. I have no clue how Gmail handles signatures since
I use Kmail. In KMail it shows up as a:
"Detached OpenPGP Signature"
--
Bo Andresen
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2006-06-11 18:14 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-10 22:08 [gentoo-user] Getting to grips with S/MIME in Kmail Mick
2006-06-10 22:37 ` gentuxx
2006-06-11 6:45 ` [gentoo-user] ctrl-alt-f(123456) dono worky so good Jason A. Booth
2006-06-11 6:15 ` gentuxx
2006-06-11 7:35 ` Jason A. Booth
2006-06-11 10:34 ` Hemmann, Volker Armin
2006-06-11 11:19 ` [gentoo-user] hijacking and unhijacking Benno Schulenberg
2006-06-11 11:25 ` [gentoo-user] ctrl-alt-f(123456) dono worky so good Bo Ørsted Andresen
2006-06-11 8:40 ` Justin R Findlay
2006-06-11 11:24 ` Bo Ørsted Andresen
2006-06-11 10:23 ` [gentoo-user] Getting to grips with S/MIME in Kmail Mick
2006-06-11 11:16 ` Bo Ørsted Andresen
2006-06-11 16:44 ` Mick
2006-06-11 17:46 ` gentuxx
2006-06-11 20:46 ` [gentoo-user] " Mick
2006-06-11 17:58 ` Bo Ørsted Andresen [this message]
2006-06-11 20:42 ` Mick
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200606111958.18042.bo.andresen@zlin.dk \
--to=bo.andresen@zlin.dk \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox