EAP server: Initialize TLS context based on private_key
It is possible for the authentication server to be configured with a PKCS #12 file that includes a private key, a server certificate, and a CA certificate. This combination could result in server_cert and ca_cert parameters not being present and that should still result in TLS context getting initialized. Signed-hostap: Jouni Malinen <j@w1.fi>
This commit is contained in:
parent
6b417a1b77
commit
59d343858d
1 changed files with 1 additions and 1 deletions
|
@ -133,7 +133,7 @@ int authsrv_init(struct hostapd_data *hapd)
|
|||
#ifdef EAP_TLS_FUNCS
|
||||
if (hapd->conf->eap_server &&
|
||||
(hapd->conf->ca_cert || hapd->conf->server_cert ||
|
||||
hapd->conf->dh_file)) {
|
||||
hapd->conf->private_key || hapd->conf->dh_file)) {
|
||||
struct tls_connection_params params;
|
||||
|
||||
hapd->ssl_ctx = tls_init(NULL);
|
||||
|
|
Loading…
Reference in a new issue