Can you give more info on the structure of what you sign? On Thu, May 6, 2010 at 5:32 PM, Claes Westrup via RT <[email protected]> wrote:
> Hello! > > I am trying to create a S/MIME document that is sent as a base64 coded data > element to a web service. When the server side decodes the base64 and then > tries to verify the document they get an error message. > faultstring=invalid signature format in message: + content hash found in > signedattributes different > On the serverside the ues a Java package from Bouncy Castle. > > I am using openssl version 0.9.7a Feb 19 2003 on a RedHat server. This is > not the latest RedHat version. > > The command that I use is > > openssl smime -sign -in $TEMPIN -signer /usr/mumps/apo/cert/sws_sign_v3.pem > -ink > ey /usr/mumps/apo/cert/sws_sign_v3.key -certfile > /usr/mumps/apo/cert/SITHS_CA_v3 > .cer -outform SMIME -out $TEMPOUT1 > > TEMPIN is the actual document which includes the part1 header. I have > replaced all the LF linebreaks whith CRLF. > > Does anybody recognize this problem? And is there a solution to it? > > Is it worth while trying to get a later version of openssl? > > Regards > > Claes > > > Claes Westrup > Tieto Healthcare&Welfare > Tel: +46 10 48 15 411 > Mobil: +46 708 18 09 61 > > > > > Hello! > > I am trying to create a S/MIME document that is sent as a base64 coded data > element to a web service. When the server side decodes the base64 and then > tries to verify the document they get an error message. > faultstring=invalid signature format in message: + content hash found in > signedattributes different > On the serverside the ues a Java package from Bouncy Castle. > > I am using openssl version 0.9.7a Feb 19 2003 on a RedHat server. This is > not the latest RedHat version. > > The command that I use is > > openssl smime -sign -in $TEMPIN -signer /usr/mumps/apo/cert/sws_sign_v3.pem > -ink > ey /usr/mumps/apo/cert/sws_sign_v3.key -certfile > /usr/mumps/apo/cert/SITHS_CA_v3 > .cer -outform SMIME -out $TEMPOUT1 > > TEMPIN is the actual document which includes the part1 header. I have > replaced all the LF linebreaks whith CRLF. > > Does anybody recognize this problem? And is there a solution to it? > > Is it worth while trying to get a later version of openssl? > > Regards > > Claes > > > Claes Westrup > Tieto Healthcare&Welfare > Tel: +46 10 48 15 411 > Mobil: +46 708 18 09 61 > > > >
