[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-07-28 01:51) wrote:

> To sum it up, I can't make these two signing strategies independent. For
now.
> So, just for now, I will assume that, although I can detect browser 
> signing, IMP is configured for server side signing anyway, so 
> IMP_SMIME_* constants are true.

That assumption is fine for now, we can sort it out later.

> One shorter question. When signing an mail for multiple recipients, 
> multiple MIMEs are created. How will we store these multiple MIMEs in 
> the HTML form? We need all of them in the page for finally re-submit 
> the form and send the messages.

Does S/MIME not support multiple recipients in one message like PGP does?
Anyway, it shouldn't make much difference whether you keep one mime type
or several in the form. It's a matter of size though.

> In the 'send_message' actionID these are stored in the array 
> $messagesToSend[], but if we split this code block in two, this array 
> is comgin from the re-submition of the form, after the browser has 
> signed each of them. How do we connect these two parts of the code 
> block now?

Not sure what you're asking here.