age (Matt Caswell)
> 2. Using SM2 ECIES in 1.1.1 (Akira Takahashi)
> 3. Re: Using SM2 ECIES in 1.1.1 (Matt Caswell)
> 4. openssl cms encrypt recipientInfo [questions for openssl
> developers]. ( ?)
>
>
> --------------------------
>
> Mes
x27;s possible I tweaked some other things
> and didn't call them out in the comments.
>
> I suppose I should check what the CAPI engine source looks like in
> 1.1.1, merge my changes in if feasible, and submit a PR. One of
> these days...
>
> Really
> From: openssl-users [mailto:openssl-users-boun...@openssl.org] On Behalf
> Of Viktor Dukhovni
> Sent: Tuesday, October 23, 2018 10:02
>
> On Tue, Oct 23, 2018 at 01:29:27PM +0100, Matt Caswell wrote:
>
> > > So, I think client have set TLS_FALLBACK_SCSV in cipher suite list in
> > > client hello.
On Tue, Oct 23, 2018 at 01:29:27PM +0100, Matt Caswell wrote:
> > So, I think client have set TLS_FALLBACK_SCSV in cipher suite list in
> > client hello.
>
> This suggests there is a bug in the client application. This can only
> happen if the client application calls SSL_CTX_set_mode() or
> SSL_
quot;utf-8"
>
> Hi,
>
> I am facing an issue after openssl upgrade to 1.1.1.
> I have a odbc client with maximum version support up to TLSv1.2 and my
> database is running with TLSv1.2,TLsv1.3.
>
> The handhake is failing and I am getting following con
On 22/10/2018 14:56, ramakrushna mishra wrote:
> Hi,
>
> I am facing an issue after openssl upgrade to 1.1.1.
> I have a odbc client with maximum version support up to TLSv1.2 and my
> database is running with TLSv1.2,TLsv1.3.
>
> The handhake is failing and I am getting following contents o
