Re: openssl smime signing and corrupt message (own code)

2005-01-24 Thread michal wodzinski
On Sat, 22 Jan 2005, Dr. Stephen Henson wrote: On Fri, Jan 21, 2005, michal wodzinski wrote: Only difference in program is that i read in stdin into a readonly BIO, and therefor am able to rewind it. Whereas the openssl smime borks on stdin, and only accepts a file. Well 0.9.7 does but

Re: openssl smime signing and corrupt message (own code)

2005-01-24 Thread Dr. Stephen Henson
On Mon, Jan 24, 2005, michal wodzinski wrote: On Sat, 22 Jan 2005, Dr. Stephen Henson wrote: On Fri, Jan 21, 2005, michal wodzinski wrote: Only difference in program is that i read in stdin into a readonly BIO, and therefor am able to rewind it. Whereas the openssl smime borks on

Re: openssl smime signing and corrupt message (own code)

2005-01-24 Thread michal wodzinski
Thanks for helping, openssl-users :) -- Regards, Michal __ OpenSSL Project http://www.openssl.org User Support Mailing Listopenssl-users@openssl.org Automated List Manager

openssl smime signing and corrupt message (own code)

2005-01-21 Thread michal wodzinski
Hi all I've written a small program that signs a message ./smime-sign newmail signedmail2 it works pretty much like openssl smime -sign -in newmail \ -signer ../certs/aba-test-cert.pem \ -inkey ../certs/aba-test-key.pem signedmail using roughly the following code: p7 =

Re: openssl smime signing and corrupt message (own code)

2005-01-21 Thread michal wodzinski
On Fri, 21 Jan 2005, Victor B. Wagner wrote: The ^@ sign is right above the second mime boundary. ^@ is an indication of the ASCII NUL (symbol with code zero), Ahh, thanks... I was really wondering what it meant :) So, anything wrong can happen if program, which treates in input as text