[Tickets #2782] S/MIME Sign using browser capabilities
bugs@bugs.horde.org
bugs at bugs.horde.org
Mon Aug 28 23:27:13 PDT 2006
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-28 23:27) 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.
You're right, I am sorry for this text/plain confusion. I know the S/MIME
wraps around whatever type of MIME is created. I just referenced
text/plain for it is the simplest example, and the one I am testing this
changes with.
The AJAX thing was about keeping the message sending flow control,
particularly the switch case 'send_message'. My intention is to modify as
few lines as little. In fact, I was expecting not to modify a single line
of PHP code, but to extend it by subclassing and composing new objects.
Nevermind, I carry on the form resubmit strategy. As I get deeper into
this I see some of the things I wrote on the Brief list are not
nessesary.
I will submit a patch for signing a simple text/plain email the moment it
works.
Thanks again Jan.
More information about the bugs
mailing list