Thanks Matt.
Jayadev.
On Wed, Dec 23, 2015 at 9:34 PM, Matt Caswell wrote:
>
>
> On 23/12/15 15:54, Jayadev Kumar wrote:
> > routines:SSL3_CHECK_CERT_AND_ALGORITHM:dh key too small:s3_clnt.c:3415:
>
> Ah. The above line is the critical bit. This is as a result of the
> logjam protections that w
On 23/12/15 15:54, Jayadev Kumar wrote:
> routines:SSL3_CHECK_CERT_AND_ALGORITHM:dh key too small:s3_clnt.c:3415:
Ah. The above line is the critical bit. This is as a result of the
logjam protections that were part of 1.0.1n. See:
https://www.openssl.org/blog/blog/2015/05/20/logjam-freak-upcomin
Here is the error i got in s_client:
97 8d e5 1f ad a8 35 e9 48 cd 09 bd 69 8d 40 d5
fd 05 e2 66 7c 50 d5 41 7a 51 d0 6b 08 dd 37 2e
fd 17 32 ca be b8 c1 d5 3a f0 ad 21 32 29 ae 2c
1d ba dd 8f 18 25 94 4d dd 0a 30 35 dc a6 79 52
70 67 f4 37 72 97 c4 e8 16 e0 fd e0 3d 16 92
>>> T
On 23/12/15 15:20, Jayadev Kumar wrote:
> Hi,
>
> When i run openssl-1.0.1m server with
>
> ./openssl101m s_server -accept 443 -msg
>
> and openssl-1.0.1q client with following command
>
> ./openssl101q s_client -connect x.x.x.x:443
>
> I see server is failing with error
>
TLS 1.2 H
>But In my case replacing the client side binary built with openssl-101m this
>issue
> goes away. So wondering could this be a bug in openssl code ?
Very very doubtful.
___
openssl-users mailing list
To unsubscribe: https://mta.openssl.org/mailman/li
Thanks for responding.
But In my case replacing the client side binary built with openssl-101m
this issue
goes away. So wondering could this be a bug in openssl code ?
On Wed, Dec 23, 2015 at 8:55 PM, Salz, Rich wrote:
> Try https://groups.google.com/forum/#!topic/node-apn/H1B6iCJlZYo
>
>
>
>
Try https://groups.google.com/forum/#!topic/node-apn/H1B6iCJlZYo
___
openssl-users mailing list
To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-users
