Request: How to PGP/MIME sign by default?

Request: How to PGP/MIME sign by default?

[Davide G. M. Salvetti]

Hi,

anybody knows how to sign every outgoing mail by default (with PGP and
MIME)?

I mean, automatically sign every part of a (possible) multipart MIME
message.

Thanks,

-- 
Davide Giovanni Maria Salvetti
W: http://www.linux.it/~salve/
OpenPGP (GPG) Key ID: 939686D5

Re: Request: How to PGP/MIME sign by default?

[ShengHuo ZHU]

"Davide G. M. Salvetti" <salve@debian.org> writes:

> Hi,
> 
> anybody knows how to sign every outgoing mail by default (with PGP and
> MIME)?
> 
> I mean, automatically sign every part of a (possible) multipart MIME
> message.

Check out the latest CVS Gnus, and try the following code.

(defun zsh/mml-pgp-sign-automatically ()
  (interactive)
  (message-goto-body)
  (if (save-excursion
	(re-search-forward 
	 "<#\\(/\\)?\\(multipart\\|part\\|external\\|mml\\)." nil t))
      (insert "<#multipart sign=pgpmime>\n")
    (insert "<#part sign=pgpmime>\n")))

(add-hook 'message-send-hook 'zsh/mml-pgp-sign-automatically)

ShengHuo

Re: Request: How to PGP/MIME sign by default?

[Davide G. M. Salvetti]

>>>>>  ZSH == ShengHuo ZHU [2000-11-13]

ZSH> "Davide G. M. Salvetti" <salve@debian.org> writes:

>> how to sign every outgoing mail by default

ZSH> Check out the latest CVS Gnus, and try the following code.

It's what I looked for, thanks!

Now I'd have a little wishlist: one may sign one or more parts of a
multipart message individually; could Gnus tell the user which parts of
a multipart message are actually signed, instead of just displaying a
single [[PGP Signed: OK]] for the whole message?

Thanks,

-- 
Davide Giovanni Maria Salvetti
W: http://www.linux.it/~salve/
OpenPGP (GPG) Key ID: 939686D5

Re: Request: How to PGP/MIME sign by default?

[ShengHuo ZHU]

"Davide G. M. Salvetti" <salve@debian.org> writes:

> Now I'd have a little wishlist: one may sign one or more parts of a
> multipart message individually; could Gnus tell the user which parts of
> a multipart message are actually signed, instead of just displaying a
> single [[PGP Signed: OK]] for the whole message?

It is not for the whole message, but one button for a signed part
(maybe multipart). The buttons are displayed at the beginning of the
signed (or encrypted) parts.  So, what you wish to know is just the
end positions.  Two possible solutions,

    1. display buttons like [[The End of PGP Signed]];
or
    2. a command like show-the-end-of-the-signed-part.

Any better idea?

ShengHuo

Re: Request: How to PGP/MIME sign by default?

[Kai Großjohann]

Another idea is to put the information into the normal part button.
Then the presence of said information could trigger the button of the
corresponding part to show.

But I think right now the normal part buttons don't reflect the
hierarchy of nested multiparts, right?  That would be a useful thing
to have, anyway, I guess.

kai
-- 
The arms should be held in a natural and unaffected way and never
be conspicuous. -- Revised Technique of Latin American Dancing

Re: Request: How to PGP/MIME sign by default?

[Jorge Godoy]

[-- Attachment #1.1: Type: text/plain, Size: 1295 bytes --]

On 14 Nov 2000, zsh@cs.rochester.edu wrote:
> "Davide G. M. Salvetti" <salve@debian.org> writes:
> 
>> Now I'd have a little wishlist: one may sign one or more parts of a
>> multipart message individually; could Gnus tell the user which
>> parts of a multipart message are actually signed, instead of just
>> displaying a single [[PGP Signed: OK]] for the whole message?
> 
> It is not for the whole message, but one button for a signed part
> (maybe multipart). The buttons are displayed at the beginning of the
> signed (or encrypted) parts.  So, what you wish to know is just the
> end positions.  Two possible solutions,
> 
>     1. display buttons like [[The End of PGP Signed]];
> or
>     2. a command like show-the-end-of-the-signed-part.
> 
> Any better idea?

The button is better, IMHO.

It's easier to see what's signed and what isn't. 


BTW, with the hack you've made to sign messages by default, you you
type in the key wrong and want to send the message again ('C-c C-c',
by default) you'll get a "multipart sign=pgpmime" before the "part
sign=pgpmime" you've just added. Is there any way to prevent that?
Maybe changing this part of the function

	(re-search-forward 
	 "<#\\(/\\)?\\(multipart\\|part\\|external\\|mml\\)." nil t))
      (insert "

[-- Attachment #1.2.1.1: Type: text/plain, Size: 19 bytes --]

\n")
    (insert "

[-- Attachment #1.2.1.2.1: Type: text/plain, Size: 26 bytes --]

\n")))


to not add a "

[-- Attachment #1.2.1.2.2: Type: application/pgp-signature, Size: 268 bytes --]

[-- Attachment #1.2.1.3.1.1: Type: text/plain, Size: 209 bytes --]

" if it finds a "<#part
sign=pgpmime>" indication... 



See you,
-- 
Godoy. <godoy@conectiva.com>

Departamento de Publicações       Conectiva S.A.
Publishing Department             Conectiva Inc.

[-- Attachment #1.2.1.3.2: Type: application/pgp-signature, Size: 268 bytes --]

[-- Attachment #1.2.2: Type: application/pgp-signature, Size: 268 bytes --]

[-- Attachment #2: Type: application/pgp-signature, Size: 268 bytes --]

Re: Request: How to PGP/MIME sign by default?

[Jorge Godoy]

Oops! I think I've hit a bug!

On 14 Nov 2000, godoy@conectiva.com wrote:

(SNIP)

> BTW, with the hack you've made to sign messages by default, you you
> type in the key wrong and want to send the message again ('C-c C-c',
> by default) you'll get a "multipart sign=pgpmime" before the "part
> sign=pgpmime" you've just added. Is there any way to prevent that?
> Maybe changing this part of the function
> 
> 	(re-search-forward 
> 	 "<#\\(/\\)?\\(multipart\\|part\\|external\\|mml\\)." nil t))
>       (insert "
> \n")
>     (insert "
> \n")))
> 
> 
> to not add a "
> " if it finds a "<#part
> sign=pgpmime>" indication... 

As you could see, the message was signed whenever the "part" or
"multipart" string was found. Isn't it in any RFC or other place a
definition that it should be on the beginning of the line, with no
spaces, or chars before it? If it isn't I'm proposing that this mime
signing stuff only be used with <multipart> (no # to not trigger
anything) and <part> in the beginning of the line.


See you,
-- 
Godoy. <godoy@conectiva.com>

Departamento de Publicações       Conectiva S.A.
Publishing Department             Conectiva Inc.

Re: Request: How to PGP/MIME sign by default?

[ShengHuo ZHU]

Jorge Godoy <godoy@conectiva.com> writes:

> Oops! I think I've hit a bug!
> 
> On 14 Nov 2000, godoy@conectiva.com wrote:
> 
> (SNIP)
> 
> > BTW, with the hack you've made to sign messages by default, you you
> > type in the key wrong and want to send the message again ('C-c C-c',
> > by default) you'll get a "multipart sign=pgpmime" before the "part
> > sign=pgpmime" you've just added. Is there any way to prevent that?
> > Maybe changing this part of the function
> > 
> > 	(re-search-forward 
> > 	 "<#\\(/\\)?\\(multipart\\|part\\|external\\|mml\\)." nil t))
> >       (insert "
> > \n")
> >     (insert "
> > \n")))
> > 
> > 
> > to not add a "
> > " if it finds a "<#part
> > sign=pgpmime>" indication... 
> 
> As you could see, the message was signed whenever the "part" or
> "multipart" string was found. Isn't it in any RFC or other place a
> definition that it should be on the beginning of the line, with no
> spaces, or chars before it? If it isn't I'm proposing that this mime
> signing stuff only be used with <multipart> (no # to not trigger
> anything) and <part> in the beginning of the line.

It is MML, not RFC. To send <#part, you should type <#!part; to send
<#!part, type <#!!part.

ShengHuo

Re: Request: How to PGP/MIME sign by default?

[ShengHuo ZHU]

Jorge Godoy <godoy@conectiva.com> writes:

> On 14 Nov 2000, zsh@cs.rochester.edu wrote:
> > "Davide G. M. Salvetti" <salve@debian.org> writes:
> > 
> >> Now I'd have a little wishlist: one may sign one or more parts of a
> >> multipart message individually; could Gnus tell the user which
> >> parts of a multipart message are actually signed, instead of just
> >> displaying a single [[PGP Signed: OK]] for the whole message?
> > 
> > It is not for the whole message, but one button for a signed part
> > (maybe multipart). The buttons are displayed at the beginning of the
> > signed (or encrypted) parts.  So, what you wish to know is just the
> > end positions.  Two possible solutions,
> > 
> >     1. display buttons like [[The End of PGP Signed]];
> > or
> >     2. a command like show-the-end-of-the-signed-part.
> > 
> > Any better idea?
> 
> The button is better, IMHO.
> 
> It's easier to see what's signed and what isn't. 

I just fell there would be too many buttons.

> BTW, with the hack you've made to sign messages by default, you you
> type in the key wrong and want to send the message again ('C-c C-c',
> by default) you'll get a "multipart sign=pgpmime" before the "part
> sign=pgpmime" you've just added. Is there any way to prevent that?
> Maybe changing this part of the function
> 
> 	(re-search-forward 
> 	 "<#\\(/\\)?\\(multipart\\|part\\|external\\|mml\\)." nil t))
>       (insert "
> \n")
>     (insert "
> \n")))
> 
> 
> to not add a "
> " if it finds a "<#part
> sign=pgpmime>" indication... 

You can change it as you like.  It is not a part of Gnus.

ShengHuo

Re: Request: How to PGP/MIME sign by default?

[Kai Großjohann]

On 14 Nov 2000, Jorge Godoy wrote:

> As you could see, the message was signed whenever the "part" or
> "multipart" string was found. Isn't it in any RFC or other place a
> definition that it should be on the beginning of the line, with no
> spaces, or chars before it? If it isn't I'm proposing that this mime
> signing stuff only be used with <multipart> (no # to not trigger
> anything) and <part> in the beginning of the line.

There is mml-quote-region which you can use to make <#part> not be
dangerous.

(I tried it in this msg, I hope it works.)

kai
-- 
The arms should be held in a natural and unaffected way and never
be conspicuous. -- Revised Technique of Latin American Dancing

Re: Request: How to PGP/MIME sign by default?

[Jorge Godoy]

On 14 Nov 2000, zsh@cs.rochester.edu wrote:

> I just fell there would be too many buttons.

:-)
If there are too many signed + non signed parts, I don't see any
problem with that... But it's not common to have such mixed stuff, I
think... 

> You can change it as you like.  It is not a part of Gnus.

Well... I've sent this to the list because I don't know enough elisp
to do that :-(( I wished I did, but.... :-(


Thanks,
-- 
Godoy. <godoy@conectiva.com>

Departamento de Publicações       Conectiva S.A.
Publishing Department             Conectiva Inc.

Re: Request: How to PGP/MIME sign by default?

[Florian Weimer]

ShengHuo ZHU <zsh@cs.rochester.edu> writes:

> It is not for the whole message, but one button for a signed part
> (maybe multipart). The buttons are displayed at the beginning of the
> signed (or encrypted) parts.  So, what you wish to know is just the
> end positions.  Two possible solutions,
> 
>     1. display buttons like [[The End of PGP Signed]];
> or
>     2. a command like show-the-end-of-the-signed-part.
> 
> Any better idea?

IMHO, the button stuff is not enough.  With the current scheme, you
don't know who actually made the signature with what key!  In
addition, the output/button stuff should contain a timestamp so that
you can check that it wasn't already contain in the message.