mirror of
https://github.com/strongswan/strongswan.git
synced 2025-10-03 00:00:24 -04:00
8aa13a1797
Before TLS 1.3, the server sent the last handshake message and had the option to piggyback the EAP-Identity request directly onto the packet with the TLS Finished message, or wait for the empty message by the client that acknowledges the completion of the handshake. With TLS 1.3, the client finishes the handshake after the server. So this option is irrelevant there and we immediately start with Phase 2.
22 lines
778 B
Plaintext
22 lines
778 B
Plaintext
charon.plugins.eap-peap.fragment_size = 1024
|
|
Maximum size of an EAP-PEAP packet.
|
|
|
|
charon.plugins.eap-peap.max_message_count = 32
|
|
Maximum number of processed EAP-PEAP packets (0 = no limit).
|
|
|
|
charon.plugins.eap-peap.include_length = no
|
|
Include length in non-fragmented EAP-PEAP packets.
|
|
|
|
charon.plugins.eap-peap.phase2_method = mschapv2
|
|
Phase2 EAP client authentication method.
|
|
|
|
charon.plugins.eap-peap.phase2_piggyback = no
|
|
Phase2 EAP Identity request piggybacked by server onto TLS Finished message,
|
|
relevant only if TLS 1.2 or earlier is negotiated.
|
|
|
|
charon.plugins.eap-peap.phase2_tnc = no
|
|
Start phase2 EAP TNC protocol after successful client authentication.
|
|
|
|
charon.plugins.eap-peap.request_peer_auth = no
|
|
Request peer authentication based on a client certificate.
|