EAP-TLS with TLS 1.3

Arran Cudbard-Bell a.cudbardb at freeradius.org
Thu Mar 15 20:05:03 CET 2018

> On Mar 14, 2018, at 3:41 PM, Stefan Winter <stefan.winter at RESTENA.LU> wrote:
> Hi,
>> I guess it’d also allow you to select different certificates depending on the CA list advertised by the server, as well as different certificates for crypto agility.
> True! In RFC6614 I wrote that the CA indication is something that should
> be honoured (it's useful if your server is in multiple consortia and
> needs to have different certs) but since eduroam seems to be the only
> large dynamic discovery + Radsec consortium, this was never urgent to
> actually do. Which doesn't mean it shouldn't be done :-)

OK, finished messing around with he config files and config file format.

- certificate {} sections are now called chain {} sections to better match what we’re doing with them (building key type specific chains).

- The server at debug level 3 (-Xx) will now print out which key types it loaded chains for, and which certificates make up those chains.

Thu Mar 15 18:44:05 2018 : tls - Found 2 server certificate chain(s)
Thu Mar 15 18:44:05 2018 : tls - RSA chain
Thu Mar 15 18:44:05 2018 : tls - [0] RSA /C=FR/ST=Radius/O=Example Inc/CN=Example Server Certificate/emailAddress=admin at example.org
Thu Mar 15 18:44:05 2018 : tls - EC chain
Thu Mar 15 18:44:05 2018 : tls - [1] EC /C=FR/ST=Radius/L=Somewhere/O=Example Inc/emailAddress=admin at example.org/CN=Example Certificate Authority
Thu Mar 15 18:44:05 2018 : tls - [0] EC /C=FR/ST=Radius/O=Example Inc/CN=Example Server Certificate/emailAddress=admin at example.org

- A few extra Makefile targets have been added to generate ecc certificates.

- Certificate chain compilation functions in OpenSSL 1.0.2 have now been exposed.  This allows us to build and validate chains on startup.  This also has a performance benefit at the chains are no longer built at runtime.  The pre-compiled chains will not include certs from the top level ca_file or ca_path.

- For the pre-compiled chains to work, you must provide all certificates from the Root CA to the server certificate.

- With OpenSSL 1.0.2 and the default v4 config, the Root CA will not be sent to the supplicant as part of the chain even if you include it in the PEM certificate bundle.

If you want additional changes in the docs and/or demo EC certs to be configured by default, please send pull requests.

It’d also be nice if someone could test give this some more thorough testing.


More information about the Freeradius-Devel mailing list