From: Simon Josefsson <jas@extundo.com>
Cc: ding <ding@gnus.org>
Subject: Re: smime setup [was: Re: nnimap + mailcrypt]
Date: Thu, 11 Apr 2002 17:03:30 +0200 (CEST) [thread overview]
Message-ID: <Pine.LNX.4.44.0204111702290.15921-100000@yxa.extundo.com> (raw)
In-Reply-To: <vqolmbupcff.fsf@astazou.imag.fr>
On Thu, 11 Apr 2002, Nicolas Kowalski wrote:
> > two IETF standards on how PGP in mail should look like. Outlook supports
> > S/MIME correctly and natively though (and so do Gnus), so perhaps you will
> > have better luck with it. S/MIME seem to interop a magnitude or so better
> > than PGP today... a few years ago, the reverse was true.
>
> I have no luck :-(. See below. I followed the instructions from smime.el.
>
> Excerpt from my .emacs:
>
> (smime-CA-file "\"~/perso/certs/cacert.pem\"")
> (canlock-password "4de89211c1a1f5ac8dca322797c2cb38f36f2018")
> (smime-keys (quote (("Nicolas.Kowalski@imag.fr" "\"~/perso/certs/niko.pem\"" nil))))
Looks good.
> And when I try to send a smime signed message, I have (sorry for the
> long lines) :
Oops.
Index: smime.el
===================================================================
RCS file: /usr/local/cvsroot/gnus/lisp/smime.el,v
retrieving revision 6.25
diff -u -w -u -u -r6.25 smime.el
--- smime.el 2002/03/04 22:34:32 6.25
+++ smime.el 2002/04/11 15:19:15
@@ -314,10 +314,10 @@
keyfile
(smime-get-key-by-email
(completing-read
- (concat "Sign using which signature? "
+ (concat "Sign using which key? "
(if smime-keys (concat "(default " (caar smime-keys) ") ")
""))
- smime-keys nil nil nil nil (car-safe (car-safe smime-keys))))))))
+ smime-keys nil nil (car-safe (car-safe smime-keys))))))))
(defun smime-encrypt-buffer (&optional certfiles buffer)
"S/MIME encrypt BUFFER for recipients specified in CERTFILES.
@@ -438,7 +438,7 @@
(concat "Decipher using which key? "
(if smime-keys (concat "(default " (caar smime-keys) ") ")
""))
- smime-keys nil nil nil nil (car-safe (car-safe smime-keys)))))))))
+ smime-keys nil nil (car-safe (car-safe smime-keys)))))))))
;; Various operations
next prev parent reply other threads:[~2002-04-11 15:03 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-11 8:19 nnimap + mailcrypt Nicolas Kowalski
2002-04-11 12:04 ` Simon Josefsson
2002-04-11 12:13 ` Nicolas Kowalski
2002-04-11 12:24 ` Simon Josefsson
2002-04-11 12:40 ` Nicolas Kowalski
2002-04-11 13:16 ` Simon Josefsson
2002-04-11 13:55 ` smime setup [was: Re: nnimap + mailcrypt] Nicolas Kowalski
2002-04-11 15:03 ` Simon Josefsson [this message]
2002-04-11 15:13 ` Nicolas Kowalski
2002-04-11 15:42 ` Simon Josefsson
2002-04-11 15:59 ` Nicolas Kowalski
2002-04-11 19:23 ` Simon Josefsson
2002-04-11 19:27 ` Simon Josefsson
2002-04-11 20:05 ` Nicolas Kowalski
2002-04-11 20:10 ` Simon Josefsson
2002-04-11 19:56 ` Nicolas Kowalski
2002-04-11 20:25 ` Simon Josefsson
2002-04-12 7:41 ` Nicolas Kowalski
2002-04-12 10:51 ` Kai Großjohann
2002-04-12 12:45 ` [SOLVED: openssl issue] " Nicolas Kowalski
2002-04-12 20:47 ` Simon Josefsson
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=Pine.LNX.4.44.0204111702290.15921-100000@yxa.extundo.com \
--to=jas@extundo.com \
--cc=ding@gnus.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;
as well as URLs for NNTP newsgroup(s).