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

* Your Email Address
* Spam protection	Enter the letters below: ______ _______ ______ _ _ \| _ \ \ / / __ \\| ____\| \| \| \| \| \|_) \ \ / /\| \| \| \| \|__ \| \|__\| \| \| _ < \ \/ / \| \| \| \| __\| \| __ \| \| \|_) \| \ / \| \|__\| \| \|____\| \| \| \| \|____/ \/ \|_____/\|______\|_\| \|_\|
Comment	> Very well, I am submitting a patch for signing a simple text message > with Mozilla Firefox. > > Horde IMP needs to be configured for signing as if server side > signing would be performed. > > The code is far from its final version. I trust we can refactor it > little by little. > > I need help particularly for the IMP_Compose::_createMimeMessage() > method. This is where I wrap a multipart/signed MIME around the > message. > > But I know that I am doing work here that is surely being done > somewhere else. Only I don't know where. > > > > Here is the list of files returned by "cvs -n -q update": > > > > ? imp/js/src/base64.js > > M imp/compose.php > > M imp/lib/Compose.php > > M imp/lib/base.php > > M imp/templates/compose/compose.html > > M imp/templates/javascript/src/compose.js > > C imp/templates/smime/import_key.html > > > > I am not keen on cvs command line, so any help is appreciated. > > The patch was generated by issuing "cvs -q diff > patch" in horde directory. > > Theres is a flie missing in this patch, base64.js wich is marked with > "?" in the list, but I don't know what it means and why cvs diff does > not include its source code in the patch. You don't need it unless > you really want to try this patch. > > > > All comments are welcome. > > > > Mariano.
Attachment
Watch this ticket