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

[Simon Josefsson <jas@extundo.com>]

Uwe Brauer <oub@mat.ucm.es> writes:

> Hello
>
> I just started to use mml together with gnupg, so far I have used
> pgp2.6.x with mail-crypt.
> I would appreciate if somebody could clarify the following points:

Hi!  Sure.

>     - what is the difference between the following functions
>       Possible completions are:
>       mml-secure-message-sign-pgp
>       and
>       mml-secure-sign-pgp            

The first tag the entire message for signing, the second only the
current part.  It is possible to have a multipart MIME document where
only one part is signed.  For normal use, you want the first one.

>       mml-secure-message-sign-pgpauto
>       and
>       mml-secure-sign-pgpauto        
>       the documentation is not very helpful

Same here, although pgpauto picks between PGP/MIME and Inline PGP
automatically.  If the message is multipart, PGP/MIME is used,
otherwise it uses inline PGP.  This appear to not be documented in the
Emacs MIME manual.  Anyone want to add something?  Further, I wonder
if it does the right thing with non-ASCII (then PGP/MIME should be
used) or format=flowed (PGP/MIME is needed).

>     - all  the time  I  sign, encrypt or   decrypt I  am asked my
>       password,  could  that be  cached  say  for  5  min  (as in
>       mailcrypt)

(setq pgg-passphrase-cache-expiry 162222)

The default is 16 seconds.  I think it should be changed to 5 minutes,
but it was discussed before.

>     - when encrypting, could  may own public  key be used as well
>       (this way I can read that encrypted mail myself)

The simplest is to do this via GnuPG.

>     - is there  now variable  to always sign  a msg  (I could put
>       that into a hook I know.)

You could invoke mml-secure-message-sign-pgpmime from a posting style,
I think.