Re: Signed Certificates and Revoking the Certs with CRLs

Well, here's the overview: The CRL is a mechanism used by the attesting entity (the CA) to change the validity status of a previously-issued certificate (digitally-provable statement of authority by a particular named entity, i.e. the CA). The certificate, which is best viewed as a record of the

RE: Problem to verify a signed file.

> From: owner-openssl-us...@openssl.org On Behalf Of Josÿe9 Fernÿe1ndez > Sent: Friday, 24 September, 2010 05:04 (It appears your mailer, or perhaps a relay, mangled your name. Sorry.) > We are signing files with openssl. We use this command (UNIX machine): > openssl smi

Re: where is the memory being held

On 9/24/2010 11:05 AM, zhu qun-ying wrote: I think I should clarify something here. The app is running > in a small device that does not have virtual memory (no swap space) and the memory is limited (256/512 M). > In peek connections, it may use up to 90% of the system memory, > and when con

Signed Certificates and Revoking the Certs with CRLs

Hi All, Would anyone kindly point me to literature that CLEARLY explains exactly how: Certificates and CRLs may be used in conjunction such that certificate CSRs are generated, signed by an authority, then signed certs downloaded and being used on a system. At a later time, the certificate is r

FIPS PowerOn self test

Hi, What are the conditions when power-on self tests may fail. We have an application using OpenSSL in FIPS mode and the power on self test has always succeeded. However, today on one of the virtual machines the test failed. What could have possibly lead to this failure? Any ideas? Thanks, Vivek

Re: where is the memory being held

On Fri September 24 2010, zhu qun-ying wrote: > Hi, > > I think I should clarify something here. The app is running in a small > device that does not have virtual memory (no swap space) and the memory is > limited (256/512 M). In peek connections, it may use up to 90% of the system > memory,

Re: where is the memory being held

Hi, I think I should clarify something here. The app is running in a small device that does not have virtual memory (no swap space) and the memory is limited (256/512 M). In peek connections, it may use up to 90% of the system memory, and when connection goes down, memory usage is not coming

Re: Problem with rsa_keygen

I think I know what's the problem. If you return 1 in rsa_keygen, OpenSSL expects a correct RSA key. I find out muy PKCKS#11 device don't work ok and the keys was wrong so OpenSSL didn't recive a correct RSA key and when I returned 1 withouh generate an RSA key was the same problem, OpenSSL hadn't

Problem to verify a signed file.

Hello, We are signing files with openssl. We use this command (UNIX machine):    openssl smime -sign -binary -outform PEM -in myfile.dat -out myfile.dat.sig -signer cert.pem -inkey keyfile.pem To verify the signed file, we use this other command (PC with Windows):    openssl smime -verif

Re: regarding binary size in OpenSSL 1.0.0a

Jakob Bohm wrote: On 23-09-2010 07:53, Madhu Gowda wrote: Hi All, We are using OpenSSL (binaries built as static version) in our application. We are using the version 0.9.8i and the size of libeay32.lib (built in 32 bit windows) is 3.392 MB. We are thinking of updating to latest version of Ope

Re: regarding binary size in OpenSSL 1.0.0a

On 23-09-2010 07:53, Madhu Gowda wrote: Hi All, We are using OpenSSL (binaries built as static version) in our application. We are using the version 0.9.8i and the size of libeay32.lib (built in 32 bit windows) is 3.392 MB. We are thinking of updating to latest version of OpenSSL 1.0.0a. When we

Re: Problem with rsa_keygen

I have the engine in a dynamic library and there's not relevant part of the code. If I overwrite rsa_keygen function and if I do something or nothing but return 1 I get "segmentation fault" but it's not my function, my function ends ok and invokes the return instruction. The example code I wrote is