eap_example: Fix configuration by added DH parameters
The internal TLS implementation supports number of additional cipher suites that require DH parameters to be set on the server. Such a cipher suite is selected by default in the eap_example case which prevented the TLS handshake from completing successfully. Fix this by adding DH parameters to the server configuration. Signed-off-by: Jouni Malinen <jouni@qca.qualcomm.com>master
parent
1acf38f1a5
commit
897418a28d
@ -0,0 +1,5 @@
|
||||
-----BEGIN DH PARAMETERS-----
|
||||
MIGHAoGBAP3V8IHq3H2DUlYywsvjYNuS17eCdt0mJo6/os6PHqdhgkMrPxF9u4Gr
|
||||
qKXq9e6GqmZYdjta30N3FkXaV924BJ0xOqb2TntiKg4u50/l6hSUneWt6UFBaizd
|
||||
XrqjNFIme/5RXMZ7RglXliBpCepAaFLMcKhOS4ulUyYYHSy+oqRjAgEC
|
||||
-----END DH PARAMETERS-----
|
Loading…
Reference in New Issue