From: Simon Josefsson <simon@josefsson.org>
Cc: ding@gnus.org
Subject: Re: Problem with smime-CA-directory
Date: Thu, 4 Apr 2002 20:48:05 +0200 [thread overview]
Message-ID: <200204042048.05524.simon@josefsson.org> (raw)
In-Reply-To: <yii8z83lat8.fsf@vertigo.daimi.au.dk>
On Thursday 04 April 2002 17:53, Arne Jørgensen wrote:
> > Yes. The OpenSSL manual should include it,
>
> Yes. I was just reading through the openssl man pages. It actually
> sounds like a bug in openssl? Or is it just an unexplained "feature".
Probably, OpenSSL documentation is not perfect.
> > but I guess we could add it to the S/MIME step-by-step stuff in the
> > Message manual as well.
>
> Good idea. I think the manual misses more about how to get S/MIME up
> and running in the first place. I've been looking through both the
> Gnus and Message manuals and smime.el to learn what I know today.
>
> What I'm preparing at the moment is a chapter for a danish tutorial on
> how to get Gnus working with the danish CA Kommunedata. Maybe I could
> easily turn this into a more general description for the manual or a
> howto -- althogh my spare time is limited.
Feel free to rewrite the current section completely, currently the
documentation is scattered throughout the MML, Message and Gnus manual.
> > Ideally we should use the Aegypten S/MIME stuff instead, once it
> > matures.
>
> Never heard of it. Maybe I'll take a look at it some other day.
There isn't a elisp interface to it, yet, but it looks like it could provide a
GNU S/MIME library. The OpenSSL license isn't very good.
next prev parent reply other threads:[~2002-04-04 18:48 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 [this message]
2002-04-04 15:55 ` David S. Goldberg
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=200204042048.05524.simon@josefsson.org \
--to=simon@josefsson.org \
--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).