Hello, My windows 10 clients does not get the "no shared cipher" error but Win7 clients gets this error. "Fri Jul 28 12:16:39 2017 : ERROR: (4) eap_ttls: Failed in __FUNCTION__ (SSL_read): ../ssl/statem/statem_srvr.c[1404]:error:1417A0C1:SSL routines:tls_post_process_client_hello:no shared cipher" I updated the win7 clients ciphers. Still get the above message. Please advise. Kind regards, On Thu, Jul 6, 2017 at 11:43 AM, Seniha S. ÖZTEMİZ TULGAR < seniha.oztemiz@gmail.com> wrote:
Hello,
When I run the freeradius I get the foloowing debug log:
(1) eap_ttls: WARNING: Total received TLS record fragments (50 bytes), does not equal indicated TLS record length (0 bytes) (1) eap_ttls: [eaptls verify] = ok (1) eap_ttls: Done initial handshake (1) eap_ttls: (other): before SSL initialization (1) eap_ttls: TLS_accept: before SSL initialization (1) eap_ttls: TLS_accept: before SSL initialization (1) eap_ttls: <<< recv TLS 1.2 [length 002d] (1) eap_ttls: >>> send TLS 1.0 Alert [length 0002], fatal handshake_failure (1) eap_ttls: ERROR: TLS Alert write:fatal:handshake failure tls: TLS_accept: Error in error (1) eap_ttls: ERROR: Failed in __FUNCTION__ (SSL_read): error:1417A0C1:SSL routines:tls_post_process_client_hello:no shared cipher (1) eap_ttls: ERROR: System call (I/O) error (-1) (1) eap_ttls: ERROR: TLS receive handshake failed during operation (1) eap_ttls: ERROR: [eaptls process] = fail (1) eap: ERROR: Failed continuing EAP TTLS (21) session. EAP sub-module failed
Have you encountered this problem? How did you solve it? What can I do?
-- Regards
Seniha
-- Selam ve sevgiler, Seniha.