From: Simon Josefsson <jas@extundo.com>
Subject: Re: S/MIME support
Date: Fri, 10 Sep 2004 08:17:21 +0200 [thread overview]
Message-ID: <iluacvyzlzi.fsf@latte.josefsson.org> (raw)
In-Reply-To: <87u0u7dmjw.fsf@tc-1-100.kawasaki.gol.ne.jp>
Miles Bader <miles@gnu.org> writes:
> Simon Josefsson <jas@extundo.com> writes:
>>> 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.
>
> What would it do if you were running on a terminal?!?
Dunno. Does gpg-agent support this? If not, gpgsm.el have to supply
gpgsm with a password somehow. Or you could store the private keys
unencrypted on disk...
next prev parent reply other threads:[~2004-09-10 6:17 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
2004-09-07 12:46 ` Werner Koch
2004-09-09 23:56 ` Miles Bader
2004-09-10 6:17 ` Simon Josefsson [this message]
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=iluacvyzlzi.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).