Re: Canonical methods for digitally signing and verifying

[Lloyd Zusman <ljz@asfast.com>]

Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann) writes:

> On 15 Dec 2000, Lloyd Zusman wrote:
> 
> > (1) ... digitally sign outgoing email via gpg.
> > (2) ... digitally encrypt outgoing email via gpg.
> 
> In the message buffer, the MML menu has a Security submenu.  Just look
> up the right functions.

THank you!

Based on what I see in the buffer after selecting these functions, it
appears like the only thing which triggers signing and encryption is
the presence of one of the following tags in the buffer (I changed the
angle brackets to square brackets here, so as not to trigger any
encryption or signing of this particular message):

  [#part encrypt=pgpmime]
  [#part sign=pgpmime]

Is it true that the only thing I need to do is to put such a tag into
the buffer before sending?

> > (3) ... verify digitally signed incoming email.
> > (4) ... decrypt incoming email that was encrypted either via pgp or
> >     gpg.
> 
> Does `W s' do the trick?

Yes, indeed it does.

But there's other default behavior I'd like to change:

I'd like to know what customizations or options control the automatic
checking for encryption when I start to read a new email message.
Right now, I'm automatically asked if I want to decrypt a new message
when I start to read an encrypted message, but I'd like to not
be automatically asked this.

This is one reason that I asked for information about all the options
and customizations that control en/decryption.

Thanks again.


-- 
 Lloyd Zusman
 ljz@asfast.com