From: Simon Josefsson <jas@extundo.com>
Subject: Re: S/MIME support
Date: Mon, 06 Sep 2004 14:25:44 +0200 [thread overview]
Message-ID: <iluoekjy46v.fsf@latte.josefsson.org> (raw)
In-Reply-To: <87sm9vde7q.fsf@wheatstone.g10code.de>
Werner Koch <wk@gnupg.org> writes:
> On Wed, 01 Sep 2004 10:53:37 +0200, Simon Josefsson said:
>
>> 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.
>
> The interface of gpgsm is very similar to gpg and thus it should be no
> problem to add support for it to pgg. Note however that gpgsm does
> not take a passphrase because private keys are entirely managed by the
> gpg-agent and thus gpg-agent will pop up a pinentry dialog as needed -
> gpg also support the gpg-agent. (There is a curses based pinentry
> available).
Good. It is probably a bad idea to force all applications to do its
own password handling, so having gpg-agent handle the password instead
of Gnus sounds better anyway.
(This reminds me that generalizing gpg-agent would be good... I have
wanted to use something similar in Shishi/SASL too. And I recall
Nikos wanting to use it in GNUTLS, but I never started working on it.
Gnus' password.el could use it as well, perhaps.)
> Just ask me if you need help integrating gpgsm into Gnus; I know the
> gpgsm very well ;-).
I'm working on the integration. See my questions on gnupg-users. :-)
Thanks,
Simon
next prev parent reply other threads:[~2004-09-06 12:25 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
2004-09-06 7:54 ` Werner Koch
2004-09-06 12:25 ` Simon Josefsson [this message]
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=iluoekjy46v.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).