From: david.goldberg6@verizon.net (David S. Goldberg)
Subject: Re: Problem with smime-CA-directory
Date: Thu, 04 Apr 2002 10:55:42 -0500 [thread overview]
Message-ID: <m1bg02bh30h.fsf@blackbird.mitre.org> (raw)
In-Reply-To: <Pine.LNX.4.44.0204041726030.21536-100000@yxa.extundo.com> (Simon Josefsson's message of "Thu, 4 Apr 2002 17:30:21 +0200 (CEST)")
One thing I found strange in my environment at work is that following
the instructions in smime.el for creating the link (openssl verify
-noout -hash -in <file>) creates a hash that works great for verifying
a certificate file, but when verifying messages, openssl is trying to
find another hash, the generation of which I cannot figure out. I
managed to figure it out by trussing an openssl verify session. So
end up with two links to my company's root CA file, one for verifying
email messages, the other for verifying cert files. Why verify cert
files? I've added some stuff to EUDC for grabbing certs from our LDAP
server and verify them before saving (well, saving for future use :-)
since the server occasionally has a not yet valid cert on it as well
as a current cert for some users whose certs are close to expiration
and I want to make sure I grab the right one. I haven't managed to
integrate this with gnus yet but I'm working on it.
--
Dave Goldberg
david.goldberg6@verizon.net
prev parent reply other threads:[~2002-04-04 15:55 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-04 12:32 Arne Jørgensen
2002-04-04 14:34 ` Simon Josefsson
2002-04-04 15:00 ` Arne Jørgensen
2002-04-04 15:30 ` Simon Josefsson
2002-04-04 15:53 ` Arne Jørgensen
2002-04-04 18:48 ` Simon Josefsson
2002-04-04 15:55 ` David S. Goldberg [this message]
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=m1bg02bh30h.fsf@blackbird.mitre.org \
--to=david.goldberg6@verizon.net \
/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).