OpenSSL 3.0.2 PKCS12_parse Failure
vchiliquinga at ups.com
vchiliquinga at ups.com
Mon Apr 4 14:03:29 UTC 2022
Hello,
Seems our email system scrubbed the response to my question because it was a link.
Could I ask the response be sent to the follow email instead, chiliquinga94 at outlook.com
Thanks!
Message: 3
Date: Fri, 1 Apr 2022 18:14:38 +0000
From: <vchiliquinga at ups.com>
To: <openssl-users at openssl.org>
Cc: <davidbowers at ups.com>
Subject: OpenSSL 3.0.2 PKCS12_parse Failure
Message-ID:
<DM8PR14MB5191DA1D2FFCB24595021B29D7E09 at DM8PR14MB5191.namprd14.prod.outlook.com>
Content-Type: text/plain; charset="us-ascii"
Hello,
Connection between a Openssl 3.0.2 server and a 1.1.1g client is proving to be unsuccessful.
According to the logs collected we seem to be having an issue with the loading of the legacy providers.
We are loading both the default and legacy providers programmatically as per the steps outlined in the Wiki for OpenSSL 3.0 - 6.2 Providers.
We are seeing the following error..
error:0308010C:digital envelope routines:inner_evp_generic_fetch:unsupported:crypto\evp\evp_fetch.c:346:Global default library context, Algorithm (RC2-40-CBC : 0), Properties ()
PKCS12_parse() failed = 183. (Using GetLastError from errhandlingapi.h, the 183 error code is obtained)
Worth mentioning that we are only seeing this issue occur when the server is a Windows 2012 server.
Thank you,
Victor C.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://urldefense.com/v3/__https://mta.openssl.org/pipermail/openssl-users/attachments/20220401/988f73e0/attachment-0001.htm__;!!AQegZw!MZ2i2Xgng7mOuuFsB5j_L60pesgQesfdJqdd6BlA-4p5w8ypqFLaNvU50ChnH_A9$ >
------------------------------
More information about the openssl-users
mailing list