IE can not visit our HTTPS webserver while I create a self-signed certificate with a
RSA key
which size is less than 365 bits,but they works well when the RSA size is more than or
eaqual to
365.
--
__
Check out the latest SMS services @ http://www
On Mar 28, 2004, at 11:12 AM, Joseph Bruni wrote:
I feel your pain. I too have tried looking through various headers and
source files to find the definitions of things. To my dismay, I've
found that the openssl group makes heavy use of C preprocessor macros
for the definition of various functio
On Sun, Mar 28, 2004, Sue_Office wrote:
> Hi,
> I'm trying to find my way through the OpenSSL code, and have come across
> something I can't figure out - In crypto\evp\c_allc.c the routine
> OpenSSL_add_all_ciphers() calls EVP_add_cipher() for all the different
> supported cipher suites. But I can
I feel your pain. I too have tried looking through various headers and
source files to find the definitions of things. To my dismay, I've
found that the openssl group makes heavy use of C preprocessor macros
for the definition of various functions and whatnot, which makes
finding routine defini
Steven Reddie wrote:
Hi Steve,
I take it that dynamically linking the FIPS OpenSSL into an executable
means that the FIPS certification is void for that application. So as
you have stated, static linking is required. However, if I'm producing
a security library that uses OpenSSL and I stati
Hi,
I'm trying to find my way through the OpenSSL code, and have come across
something I can't figure out - In crypto\evp\c_allc.c the routine
OpenSSL_add_all_ciphers() calls EVP_add_cipher() for all the different
supported cipher suites. But I can only find the definitions of type
const EVP_CIPHER
