EAP-TLS

What is Expansion of EAP-TLS?

EAP-TLS stands for Extensible Authentication Protocol - Transport Layer Security.

What is EAP-TLS?

EAP-TLS is an authentication protocol that uses Transport Layer Security (TLS) to provide strong mutual authentication between a client and a server using digital certificates.

Why is EAP-TLS useful?

  • Provides strong security through mutual authentication.

  • Uses digital certificates to eliminate the need for passwords.

  • Widely supported and standardized.

  • Protects against man-in-the-middle attacks and replay attacks.

How it works?

  • Client and server exchange certificates during the TLS handshake.

  • Both verify each other’s certificates.

  • A secure TLS tunnel is established.

  • Session keys are generated for further encrypted communication.

Where is EAP-TLS used?

  • Enterprise Wi-Fi networks (WPA-Enterprise).

  • VPN authentication.

  • Any environment requiring strong certificate-based authentication.

Which OSI layer does this protocol belong to?

  • Application Layer (Layer 7) of the OSI model.

  • Operates within the EAP framework transported over network layers.

IS EAP-TLS windows specific?

  • No, it is platform-independent.

  • Supported on Windows through native supplicants and third-party software.

IS EAP-TLS Linux Specific?

  • No, it’s supported widely on Linux via wpa_supplicant and other tools.

Which Transport Protocol is used by EAP-TLS?

  • Runs over EAP, which is commonly encapsulated over: * EAPOL (Ethernet) * RADIUS (UDP) * Diameter (TCP/SCTP)

Which Port is used by EAP-TLS?

  • RADIUS authentication: UDP port 1812

  • Diameter (if used): TCP port 3868

Is EAP-TLS using Client server model?

  • Yes.

  • Client (supplicant) and Authentication Server (e.g., RADIUS).

Whether EAP-TLS protocol uses certificates?

  • Yes, both client and server use X.509 certificates for mutual authentication.

How many frame exchanges are seen during connection for EAP-TLS protocol?

  • Approximately 10–12 EAP message exchanges depending on TLS handshake details.

Whether EAP-TLS Protocol uses client certificates?

  • Yes, client certificates are mandatory for authentication.

Whether EAP-TLS Protocol uses Server Certificates?

  • Yes, server certificates are mandatory.

IS EAP-TLS Protocol depends on TCP?

  • Indirectly, if Diameter backend is used.

  • EAP itself is transport agnostic.

IS EAP-TLS Protocol depends on UDP?

  • Yes, typically when using RADIUS backend (UDP).

What are the roles involved when testing EAP-TLS Protocol?

  • Supplicant (client)

  • Authenticator (e.g., AP)

  • Authentication Server (e.g., FreeRADIUS)

  • Certificate Authority (CA)

Does EAP-TLS Protocol work with free radius server on Linux?

  • Yes, FreeRADIUS has robust EAP-TLS support.

Does EAP-TLS Protocol work with Internal radius server of hostapd?

  • No, hostapd’s internal radius server does not support EAP-TLS.

What is the RFC version use for EAP-TLS Protocol?

  • RFC 5216

During Connection Procedure which EPoL Packets are encrypted?

  • EAPOL packets themselves are not encrypted.

  • After key derivation, subsequent data packets are encrypted.

Can you Explain different stages of Connection Procedure for EAP-TLS Protocol?

  • Client initiates EAP identity.

  • Server requests TLS handshake.

  • Client and server exchange certificates.

  • TLS session is established and keys are generated.

  • Server sends EAP Success.

  • Session keys (MSK) are handed over to authenticator for encryption.

What is the final output of Connection Procedure?

  • Generation of Master Session Key (MSK) and Extended MSK (EMSK).

What is the format of the key generate after the connection procedure?

  • MSK: 64 bytes (512 bits)

  • EMSK: 64 bytes (512 bits)

Where the use of PMK generated by the Connection Procedure?

  • PMK (Pairwise Master Key) is derived from MSK and used in 4-way handshake for encrypting wireless data.

  • In this section, you are going to learn

  • Terminology

  • Version Info

  • rfc details

  • Run Free RADIUS

FreeRADIUS : Download latest freeradius source code

Note

  • Make sure internet is available in laptop to download freeradius package

test:~$ wget https://github.com/FreeRADIUS/freeradius-server/archive/v3.0.x.tar.gz

FreeRADIUS : Extract freeradius

test:~$ tar -zvf v3.0.x.tar.gz

FreeRADIUS : Change directory to Radius server

test:~$ cd freeradius-server-3.0/

FreeRADIUS : Check the current working directory using pwd command

Note

  • Make sure your current working directory is freeradius-server-3.0

test:~$ pwd
/home/test/freeradius-server-3.0

FreeRADIUS: Open debian/rules and add this line –without-rml_sql_iodbc above –without-rlm_eap_ikev2

test:~$ vim debian/rules
--without-rml_sql_iodbc \
--without-rlm_eap_ikev2 \

FreeRADIUS: Configure for Compilation

test:~$ ./configure

FreeRADIUS: Build the Radius server

test:~$ make

FreeRADIUS: Go to raddb folder (all radius server/client files and certificates and keys will be generated here)

test:~$ cd /usr/local/etc/raddb

FreeRADIUS: Open clients.conf file and verify localhost client is present else add your own client like below

test:~$ sudo vi clients.conf

client 192.168.56.10{
ipaddr = 192.168.56.10
secret = testing123
}  

FreeRADIUS: Open users file and uncomment below two lines or add

test:~$ sudo vi users

bob 	Cleartext-Password := "testing123"
 	Reply-Message := "Hello, %{User-Name}"

FreeRADIUS: Set default_eap_type=tls in eap file located in /usr/local/etc/raddb/mods-enabled

test:~$ sudo vi /usr/local/etc/raddb/mods-enabled/eap

default_eap_type=tls

FreeRADIUS: Start radius server

test:~$ sudo radiusd -X
  • Run AP mode operation with hostapd

AP : Download hostapd

Note

  • Make sure internet is available in laptop to download hostapd package

test:~$ wget http://w1.fi/releases/hostapd-2.9.tar.gz

AP: Install required packages

test:~$ sudo apt install libnl-genl-3-dev libnl-3-dev libdbus-glib-1-dev

AP : Extract hostapd

test:~$ tar -xzvf hostapd-2.9.tar.gz

AP : Change directory to hostapd

test:~$ cd hostapd-2.9/hostapd/

AP : Check the current working directory using pwd command

Note

  • Make sure your current working directory is hostapd

test:~$ pwd
/home/test/hostapd-2.9/hostapd

AP : Copy the contents of defconfig file to .config file

Note

  • .config file is required for make to start compilation of hostapd

test:~$ sudo cp defconfig .config

AP : Complile hostapd

Note

  • Compile hostapd by running make command

test:~$ make

AP : Check for the binaries created

Note

  • Make sure hostapd and hostapd_cli are present

test:~$ ls
hostapd
hostapd_cli

AP : Create a hostapd.conf file in /etc/hostapd folder with below content

test:~$ sudo vim /etc/hostapd/hostapd.conf

ctrl_interface=/var/run/hostapd
interface=enp0s8
driver=wired
logger_stdout=1
logger_stdout_level=1
debug=2
ieee8021x=1
eap_server=0
eap_user_file=/etc/hostapd/eap_user
eap_reauth_period=3600
use_pae_group_addr=1
auth_algs=1
auth_server_addr=127.0.0.1
auth_server_port=1812
auth_server_shared_secret=testing123
acct_server_addr=127.0.0.1
acct_server_port=1812
acct_server_shared_secret=testing123
macaddr_acl=0
ca_cert=/usr/local/etc/raddb/certs/ca.pem
server_cert=/usr/local/etc/raddb/certs/server.crt
private_key=/usr/local/etc/raddb/certs/server.p12 

AP : Create a file eap_user in /etc/hostapd/ folder with below content

test:~$ sudo vim /etc/hostapd/eap_user

AP : Run hostapd

test:~$ sudo ./hostapd /etc/hostapd/hostapd.conf
enp0s8: interface state UNINITIALIZED->ENABLED
enp0s8: AP-ENABLED

STA : Download wpa_supplicant

Note

  • Make sure internet is available in laptop to download supplicant package

test:~$ wget https://w1.fi/releases/wpa_supplicant-2.9.tar.gz

STA: Install required packages

test:~$ sudo apt install libnl-genl-3-dev libnl-3-dev libdbus-glib-1-dev

STA : Extract wpa_supplicant

test:~$ tar -xvf wpa_supplicant-2.9.tar.gz

STA : Change directory to wpa_supplicant

test:~$ cd wpa_supplicant-2.9/wpa_supplicant/

STA : Check the current working directory using pwd command

Note

  • Make sure your current working directory is wpa_supplicant

test:~$ pwd
/home/test/wpa_supplicant-2.9/wpa_supplicant

STA : Copy the contents of defconfig file to .config file

Note

  • .config file is required for make to start compilation of supplicant

test:~$ cp defconfig .config

STA : Compile wpa_supplicant

Note

  • Compile supplicant by running make command.

test:~$ make

STA: You might get errors while make regarding openssl headers in that case install the openssl headers and then do make clean and then do make again.

test:~$ sudo apt install libssl-dev
test:~$ make clean
test:~$ make

STA : Check for the binaries created

Note

  • Make sure wpa_supplicant and wpa_cli are present

test:~$ ls
wpa_supplicant
wpa_cli

STA: Copy required certificates from hostapd to wpa_supplicant

STA : Create wpa_supplicant.conf

test:~$ sudo vim wpa_supplicant.conf

ctrl_interface=/run/wpa_supplicant
update_config=1
network={
key_mgmt=WPA-EAP
eap=TLS
identity="bob"
password="testing123"
ca_cert="/home/test/ca.pem"
client_cert="/home/test/client.crt"
private_key="/home/test/client.p12"
private_key_passwd="whatever"
}

STA : Run wpa_supplicant

test:~$ sudo ./wpa_supplicant -D wired -i enp0s8 -c wpa_supplicant.conf
enp0s8: CTRL-EVENT-EAP-SUCCESS EAP authentication completed successfully

STA: Test

test:sudo ./wpa_cli -i enp0s8
> status
  • setup

  • setup

  • packet details

  • usecases

  • features

  • Reference links