Are you exchanging messages between a windows client and a linux server? if
so have you considered the difference in linebreaks? UNIX and WINDOWS
interpret the "enter to the next line" ascii code in a different way. You
might want to replace the /\r\n|\r|\n/" sequence (in regex) with "\r\n".
cheers
Meint
----- Original Message -----
From: "Chris Covell" <[EMAIL PROTECTED]>
To: <openssl-users@openssl.org>
Sent: Wednesday, May 25, 2005 3:14 PM
Subject: Re: Using OpenSSL to verify a FireFox signed form
Victor,
> $ openssl smime -verify -inform PEM -in signature.pk7 -CAfile
> development_cm.pem -content content.txt
Yes, CR/LF can be a problem. Many MTA feel free to convert eol from
CR/LF to LF and vice versa.
Yeah, but I am not using an MTA, I am signing the data in FireFox
browser and storing the resultant base64 encoded data in a database.
Try to play with -text and -crlfeol options of openssl smime.
Does not seem to make any difference.
For us there was more problems with generation of S/MIME messages which
pass
all the mail servers on the way to recipient.
Yeah, I have seen that too.
I can't believe other people have not seen this problem before, i.e.
signing on the client browser and verifying on the server using
OpenSSL !
Chris...
______________________________________________________________________
OpenSSL Project http://www.openssl.org
User Support Mailing List openssl-users@openssl.org
Automated List Manager [EMAIL PROTECTED]
______________________________________________________________________
OpenSSL Project http://www.openssl.org
User Support Mailing List openssl-users@openssl.org
Automated List Manager [EMAIL PROTECTED]
