Hi Vladimir,
I have inserted your code into my application between
OPENSSL_config("correct config file path");
SSL_library_init();
SSL_load_error_strings();
and
SSL_CTX_use_certificate_chain_file(ctx, CERTFILE)
The code was executed without errors but
SSL_CTX_use_certificate_chain_file
> From: owner-openssl-us...@openssl.org On Behalf Of Patrick Patterson
> Sent: Wednesday, 13 June, 2012 15:59
> To: openssl-users@openssl.org
> Subject: Re: Is Sha2 supported for signing certs?
>
> Hi Pushkar,
>
> Don't use the -md option - just use -sha256 directly.
Nope. -sha256 is correct for
>From: owner-openssl-us...@openssl.org On Behalf Of Jayant Dusane
>Sent: Tuesday, 12 June, 2012 03:24
>SO_RCVTIMEO and SO_SNDTIMEO didnt work!
>and also nothing related to certifacte, firewall, authentication.
>because it works with 0.6 ms latency and stopped working in ~100ms latency
network.
You'll need to ask whomever you got managedopenssl.dll from - that DLL is not
part of OpenSSL. It's certainly possible to build 64-bit versions of OpenSSL
for Windows, and I believe pre-built versions can be downloaded from various
places on the Web (they're not provided by the OpenSSL project).
Hi
Currently in of the application we are using libeay32.dll with a wrapper
managedopenssl.dll which is used in .net application for encryption and
decryption
It is supporting the 32 bit operating system not supporting 64 bit .
Is there any managed dll available for wrapper and libeay64.dll
Hi Pushkar,
Don't use the -md option - just use -sha256 directly.
Have fun.
Patrick.
On 2012-06-13, at 2:11 PM, Pushkar Pathak wrote:
> Hi All,
>
> I am trying to sign a certificate with SHA2. I have my own CA certificate
> and want to sign an end entity certificate with sha2. Is SHA 2 suppor
Hello Vladimir,
The difference is the policy against which the Certificate has been issued -
EVSSL Certs are issued according to a standard Certificate Policy outlined by
the CA/Browser forum, by Certificate Authorities which have been certified by
each of the major browser authors / vendors.
I made a mistake in code and it is possible not to load all engines with
ENGINE_load_builtin_engines :
What next code show you:
//testing loading GOST engine
ENGINE *e;
const char *engine_id = "gost";
ENGINE_load_openssl();
//ENGINE_load_builtin_engines();
ENGINE_load_gost();
e =
"Unsupported algorithm" error message means that GOST functions was not initialized properly. The question is: how
properly initialize engines with >>statically linked openSSL?
How you init GOST engine with statically linked openSSL?
What next code show you:
//testing loading GOST engine wi
>>Do you have following sections in you openssl.cnf file?
Yes I have these sections in my openssl.cnf, and no dynamic_path parameter.
It happens only if I use static linkage (with libssl.a and libcrypto.a) .
If I use dynamic linkage with openssl (with libssl.so and libcrypto.so)
everything work
Do you have following sections in you openssl.cnf file?
[openssl_def]
engines = engine_section
[engine_section]
gost = gost_section
[gost_section]
engine_id = gost
default_algorithms = ALL
CRYPT_PARAMS = id-Gost28147-89-CryptoPro-A-ParamSet
There should not be any dynamic_path parameter in gos
Looks like this is an unresolved bug in config where the fix is either to run
as an unprivileged user or comment out the offending code (in this case lines
793, 794, and 795 or just look for "-o /dev/null"). This post goes into
greater detail:
http://www.mail-archive.com/openssl-dev@openssl.o
I have added OpenSSL_add_all_algorithms(); function call to initialization
part but without success.
The same behavior as before.
What's more for dynamically linked version it works without
OpenSSL_add_all_algorithms() call.
On 6/14/2012 8:02 AM, Steffen DETTMER wrote:
Hi all!
Many public CAs suggest Extended Validation for certificates
of web servers. [...] I had a talk with a specialist
of technical support of Thawte [...] He also refused
to answer how browser determines what bar to display -
green or yellow?
Se
14 matches
Mail list logo
