Re: CRLF problem when verifiying a signature signtext()

After doing some thinking, the problem is how Javascript/DOM engine interprets values in HTML documents. Simply type some lines in a HTML textarea and ask its value from Javascript. If you inspect every char code (String::charCodeAt(int)) you will see line breaks as single 0x0A byte (LF linefeed).

CRLF problem when verifiying a signature signtext()

Hi, I am having problems when verifying a signature produced with crypto.signtext() in Firefox. The data is coming inside a textarea in the HTML. It has several line breaks. When passing the to signtext(), the String reads line breaks as one byte LF (0x13 ASCII). However, the original data has CRL

newlines and signtext

Hi, I had problems with verifying signatures produced by signtext(). This is becouse newlines in string data is interpreted as in Unix. So, the following data Hi There Is interpreted as "Hi(LF)There". However, when verifying, the data is supplied as "Hi(CRLF)There". That's an extra byte DOS-like n

Signtext unicode data in javascript

Hi, I am trying to sign some data with crypto.signtext() on Firefox 1.5 passing a string as an argument, but I am having problems to verify the signature. signtext() detachs the signed data, wich makes it impossible to actually see what it is signing. So I switched to Capicom and IE to create a p