[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         | mfernandez at gva.es
 Summary            | S/MIME Sign using browser capabilities
 Queue              | IMP
 Version            | HEAD
 Type               | Enhancement
 State              | Feedback
 Priority           | 1. Low
 Owners             | Horde Developers, Michael Slusarz
-----------------------------------------------------------------------


mfernandez at gva.es (2006-08-24 01:11) wrote:

> Without AJAX:
> ~~~~~~~~~~~~~
> Brief:
> ------
> 1) Submit the form as usual.
> 2) Build a text/plain MIME for each recipient.
> 3) Marshall return values as form hidden inputs.
> 4) Render the compose page again.
> 5) Hook on onload event to sign text/plain MIMES.
> 6) ReSubmit this form.
> 7) Unmarshall submitted form hidden inputs to carry on.
> 8) Build a multipart/signed for each pair of (text/plain, signature)
> 9) Now send all as usual.

I gave it another look at this and I believe some of the un/marshalling (i
mean serializing) is unnecesary, just by changing the way I suggested to
chop the switch case. The variables for buildAndSendMessage() are taken
from the form submition. If I move up case 'submit_mime' to the top, all
the variables will be re taken.

I am working to confirm this. Maybe the re-submition strategy isn't that
painful, although I think we could do it better with Ajax later.