Is this a bug with the -subj option of the req command

Hello All,   I am using OpenSSL 0.9.8 The -subj option of the req command does not refer the openssl.cnf file to check the maximum and minimum values of each field. When creating a self signed certificate using req command we can specify the X509 name either by using -subj o

Re: certificate embedded into the executable

C L wrote: > Theoretically it's possible to embed certificates into a Windows and > Linux executables - not sure about other architectures though. I don't recall the exact invocation off the top of my head but you can create a make rule that's something like: cert.o: cert.pem ld -o $@ (fla

Re: certificate embedded into the executable

Try if below works for you: unsigned char buf[] = "- BEGIN CERTIFICATE - ... - END CERTIFICATE -"; /* copy the entire certificate file (PEM formatted) and stick it in here */ BIO *bio = NULL; X509 *x509 = NULL; bio = BIO_new_mem_buf(buf, -1); x509 = PEM_read_bio_X509(bio, NUL

RE: certificate embedded into the executable

Theoretically it's possible to embed certificates into a Windows and Linux executables - not sure about other architectures though. In my spare time I've been researching this topic as well. You can use the ImageAddCertificate() Win32 API from Imagehlp.dll to programmatically store a certific

certificate embedded into the executable

Hi, Can anyone tell me if it's possible to embed a client certificate inside my executable, and what calls I should use to tell OpenSSL to use it? I think I'll also need to do it for the CA, since we use self-signed certificates, and I want the client to verify the server's certificate too.

Re: FIPS140-2: ANSI X9.31 in openssl ???

Brendan Simon wrote: I have been using openssl-0.9.6d and using PKCS#1. I have a requirement to be compliant with FIPS140-2 and it seems that PKCS#1 is not compliant with FIPS140-2 :( It seems that I must use ANSI X9.31 to generate random numbers to be FIPS140-2 compliant. I was told that ne

FIPS140-2: ANSI X9.31 in openssl ???

I have been using openssl-0.9.6d and using PKCS#1. I have a requirement to be compliant with FIPS140-2 and it seems that PKCS#1 is not compliant with FIPS140-2 :( It seems that I must use ANSI X9.31 to generate random numbers to be FIPS140-2 compliant. I was told that newer versions of openss

Net::SSLeay

I need to direct the perl module Net::SSLeay to include OpenSSL headers from /opt/SUNWconn/crypto/include, such as with the compiler flag: -I /opt/SUNWconn/crypto/include It must also be directed to include references to the appropriate libraries. The Sun cryptographic libraries must be included a

Re: OCSP Apis

For example OCSP_CERTID_free is exported in libcrypto.so but I could not find it in the source code Look at asn1/asn1.h adn asn1/asn1t.h /r$ -- Rich Salz, Chief Security Architect DataPower Technology http://www.datapower.com XS40 XML Security Gateway http:/

cryptlib vs openssl

Hi, does anyone know about Peter Gutmann's cryptlib and how it compares to openssl? Gerd -- -- -- Gerd Schering, Email: [EMAIL PROTECTED] -- -- smime.p7s Description: S/MIME Cryptographic