Gnus development mailing list
 help / color / mirror / Atom feed
From: beaker@iavmb.pl (Krzysztof Jędruczyk)
Subject: S/MIME + additional certificate files
Date: Mon, 23 Sep 2002 16:46:42 +0200	[thread overview]
Message-ID: <ubs6o4vcd.fsf@hot.pl> (raw)

Hello,

I've recently tried to send some S/MIME signed messages and
encountered a problem, which I believe lies in gnus' smime.el. The
problem is that even if I specify additional certificate files in
smime-keys variable - they don't get attached to signature. This
might cause with verification - depending on what certs recipient
has already installed (the certification path will be incomplete).

I've searched google for reports on this particular problem, and found
nothing. So - I looked at it myself. 

I identified the problem to be in smime-sign-buffer, which in turn
passes keyfile retrieved with smime-get-key-by-email to
smime-sign-region. The problem is that smime-get-key-by-email returns
only the key without accompanying additional certs.

Workaround that works for me is to change line 315 in smime.el from

       (smime-get-key-by-email
to
       (smime-get-key-with-certs-by-email

and add new function definition:

(defun smime-get-key-with-certs-by-email (email)
  (cdr (assoc email smime-keys)))

I believe that this is incomplete solution - I haven't reviewed if
rest of the code doesn't suffer from similar problem. I'm just
signaling a problem here since I know elisp very little.

BTW. I'm using an Oort Gnus, (AFAIR 0.08; it should be mentioned in
the headers of this message), taken from cvs about 28-aug-2002.

-- 
Best Regards,
        Krzysztof Jędruczyk




             reply	other threads:[~2002-09-23 14:46 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-09-23 14:46 Krzysztof Jędruczyk [this message]
2002-09-23 15:52 ` Simon Josefsson
2002-09-23 15:58   ` Simon Josefsson
2002-09-23 16:58     ` Krzysztof Jędruczyk

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=ubs6o4vcd.fsf@hot.pl \
    --to=beaker@iavmb.pl \
    /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).