Re: mml-secure: function doubled, passwd chache, use-my-public key

[Simon Josefsson <jas@extundo.com>]

Werner Koch <wk@gnupg.org> writes:

>> What more than setting pgg-cache-passphrase to nil do you want?
>
> No, because Gnus will ask for the passphrase and the passphrase will
> actually end up in the message if you accidently use it with enabled
> gpg-agent.

That doesn't happen here.  With pgg-c-p set to nil, Gnus won't ask me
for a passphrase, the pinentry dialog pop up instead (the first time),
and then message is signed.  No passphrase in the message either.

>> Then why isn't used automatically?  To get it working I had to start
>
> Isn't that a packaging feature?

Right.  It was just a rant.

>> the daemon manually and add 'use-agent' to ~/.gnupg/gpg.conf.
>
> Without that many people would inadvertly send the passphrase with the
> message; consider the usual invocation pog gpg:
>
>  (echo passphrase; cat message) | gpg --passphrase-fd 0 ... >out.msg
>
> so it is far safer to require a conscious decision from the user.

Ouch.  OTOH, it seem wrong in the long run.  Perhaps 'use-agent' can
be enabled in the template gpg.conf for future users.  But it will
take a while to fix all applications...  O well.

>> is hardly user friendly.  When I log on my Debian box, ssh-agent is
>> started and I didn't do anything to make it run.  Perhaps gpg-agent
>> can be started in a similar way.  And there seem to be some font bug
>> in the pinentry dialog window, presumably Unicode related.
>
> The latest release 1.9.17 may indeed be started like ssh-agent and may
> actually replace ssh-agent (except for ssh v1 keys) - you can use a
> simple wrapper script named ssh-agent and everything works. See the
> info page.

Cool!