In the branches 1.0.0, 1.0.1 and 1.0.2 of OpenSSL, some command line commands
which accepts cipher argument (at least enc, cms and smime) delays
engine initialization until all the command-line options are parsed.
Thus, if user specifies cipher, which is available only from engine,
such as
I've just pushed a partial fix for this issue. The TLS tests should now
pass for you in the latest master version in git. The new TLS test proxy
we are using does not support compression, but was failing to switch it
off if OpenSSL is configured for it.
However, this one is a different problem:
Hi,
There are several standards which define padding for block ciphers.
OpenSSL currently implements only PKCS#7 padding mode.
For some reasons I need to use ISO/IEC 7816-4 padding, and hope to get
this patch accepted into OpenSSL.
Now we have EVP_CIPHER_CTX_set_padding function which accepts
Ping?
- Kim
On Tue, Aug 18, 2015 at 4:16 PM, The default queue via RT
wrote:
>
> Greetings,
>
> This message has been automatically generated in response to the
> creation of a trouble ticket regarding:
> "[PATCH] Fix #include order in rand.h for Windows",
> a summary
On Tue Sep 15 14:33:33 2015, cber...@us.ibm.com wrote:
> Hi,
>
> I'm trying to build the FIPS-140 compliant OpenSSL software on my
> Windows 7
> system using the Visual Studio 2015 compiler. I am using OpenSSL-FIPS-
> 2.0.10
> and OpenSSL-1.0.2d. I'm getting the following build error when trying
>