[Tickets #2782] S/MIME Sign using browser capabilities

[bugs@bugs.horde.org]

DO NOT REPLY TO THIS MESSAGE. THIS EMAIL ADDRESS IS NOT MONITORED.

Ticket URL: http://bugs.horde.org/ticket/?id=2782
-----------------------------------------------------------------------
 Ticket             | 2782
 Updated By         | Jan Schneider <jan at horde.org>
 Summary            | S/MIME Sign using browser capabilities
 Queue              | IMP
 Version            | HEAD
 Type               | Enhancement
 State              | Feedback
 Priority           | 1. Low
 Owners             | Horde Developers, Michael Slusarz
-----------------------------------------------------------------------


Jan Schneider <jan at horde.org> (2006-08-24 09:13) wrote:

I think you misunderstand how signing works. If signing messages with
s/mime, the *complete* message is being signed, not only the text/plain
part containing the message body. It could be a multipart/alternative
message if sending html messages or a multipart/mixed message if sending
messages with attachements or a combination of both.
In any case the complete message is being signed, which means that you can
simply send the body field with ajax to the server to be signed, but you
need to send the complete form, build the complete message, send it back,
sign it, put it into a hidden form field, submit the form again, construct
a new multipart/signed message now with the signature in a separate mime
part. Sounds familar? It's exactly the same amount of work necessary to do
it with the form or with ajax, but the ajax version is a better user
experience because it happens in the background.
I think Michael can comment more on the message building process.