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

Search Results: 27 of 574 [ <<First <Prev Next> Last>> ] [ Return to Search Results ]

* Your Email Address
* Spam protection	Enter the letters below: . ..__ .___..__ .__. \| \|[ __ \| [__)[__] \|__\|[_./ \| [__)\| \|
Comment	> 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.
Attachment
Watch this ticket