Gnus development mailing list
 help / color / mirror / Atom feed
From: Simon Josefsson <jas@extundo.com>
Subject: Re: S/MIME support
Date: Wed, 01 Sep 2004 10:53:37 +0200	[thread overview]
Message-ID: <ilullful69a.fsf@latte.josefsson.org> (raw)
In-Reply-To: <zf.m3n00cgves.fsf@zeitform.de>

Ulf Stegemann <ulf@zeitform.de> writes:

> Regarding that, is it worth it to think about improving Gnus' S/MIME
> capabilities?  Are there plans to do so?  Or is it all a very bad idea and
> are there more important things to do?

I think it would be useful to enhance it.  However, I believe the
first step toward making the support better is to replace OpenSSL with
the S/MIME implementation in the development versions of GnuPG; gpgsm.
I don't think OpenSSL is a good idea.  I believe gpgsm can help with
the key management issues you mention as well.




  reply	other threads:[~2004-09-01  8:53 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-30 21:36 Ulf Stegemann
2004-09-01  8:53 ` Simon Josefsson [this message]
2004-09-06  7:54   ` Werner Koch
2004-09-06 12:25     ` Simon Josefsson
2004-09-07 12:46       ` Werner Koch
2004-09-09 23:56       ` Miles Bader
2004-09-10  6:17         ` Simon Josefsson
2004-09-10 12:21         ` Werner Koch

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=ilullful69a.fsf@latte.josefsson.org \
    --to=jas@extundo.com \
    /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).