Re: Avoid large memory consumption when using pkcs7_sign

2006-12-29 Thread Dr. Stephen Henson
On Fri, Dec 29, 2006, Nils Larsch wrote: > Hagai Yaffe wrote: > > > > > >I am using PKCS7_sign for applying Digital Signature to files, when I am > >creating an enveloped PKCS#7 file that contains also the signed file > >content all the signed file data is being loaded to memory (this would >

Re: OpenSSL with Windows subordinates

2006-12-29 Thread Dr. Stephen Henson
On Fri, Dec 29, 2006, Aaron Barnes wrote: > Wonderful! > I redid the root CA setup using ca.pl, modified the openssl.cnf file to > CA:TRUE in the v3_ca section, and signed the subordinate request using > the previous command: > (ca -config /path/openssl.cnf -out thecertificate.pem -in > requestfil

Re: Avoid large memory consumption when using pkcs7_sign

2006-12-29 Thread Nils Larsch
Hagai Yaffe wrote: Hello, I am using PKCS7_sign for applying Digital Signature to files, when I am creating an enveloped PKCS#7 file that contains also the signed file content all the signed file data is being loaded to memory (this would be a problem with large files), I know that I can u

RE: OpenSSL with Windows subordinates

2006-12-29 Thread Aaron Barnes
Wonderful! I redid the root CA setup using ca.pl, modified the openssl.cnf file to CA:TRUE in the v3_ca section, and signed the subordinate request using the previous command: (ca -config /path/openssl.cnf -out thecertificate.pem -in requestfile.req -extensions v3_ca). I imported the the pem file

Re: BIT STRING Encoding with ECDSA-384 1 byte too long

2006-12-29 Thread Nils Larsch
Schifman, Jon wrote: I'm using OpenSSL 0.9.8d to work on generating X.509 certificates for use with ECDSA using the SECP384R1 curve. When I generate a certificate, the public key created is 97 bytes, but I know it should be 96 bytes (2 384 bit parameters for the x,y points on the curve). It show