Un ancien physicien canadien contrôle l'authentification de 100 millions d'utilisateurs quotidiens. Alan DeKok maintient seul FreeRADIUS depuis 1999 — la moitié des connexions internet mondiales passent par son code.
da.van.ac/un-physicien-nucle…
The RADIUS conference went very well. We have agreement from operators and impementers on how to fix long-standing issues with the protocol. radiusconference.org/
Meet @AlanDekok, creator of FreeRADIUS and the person who made your network actually work (you're welcome).
Join him at RADIUS Conference 2025 for some free, real talk on auth infrastructure:
Online: March 13
Register: radiusconference.org#InfoSec#NetworkInfrastructure
Apparently some vendors are still having issues with BlastRADIUS fixes. Not sure why. Message-Authenticator has been defined for 25 years. i.e. longer than the IT career of most engineers working on the fixes.
There are still some cloud identity providers who claim that PAP is insecure. If you read the BlastRADIUS paper, the cryptographers say otherwise.
Who should you believe? Crypto experts, or a random marketing person?
You can keep using PAP. It's fine.
There are still some cloud identity providers recommending RADIUS/UDP and MS-CHAP. If you do this, then consider all your passwords to be compromised.
Don't use MS-CHAP, or MS-CHAPv2.
There is a LOT of misinformation about the BlastRADIUS issue.
If you're using RADIUS for administrator authentication to devices: upgrade. Don't switch to TACACS . Just upgrade your RADIUS server and / or RADIUS client. You will be fine.
There is a LOT of misinformation about the BlastRADIUS issue.
If you're using RADIUS for administrator authentication to devices: upgrade. Don't switch to TACACS . Don't believe anyone who says it's a viable option: they're incompetent.
There is a LOT of misinformation about the BlastRADIUS issue.
TACACS can't replace RADIUS. TACACS is used only for administrator authentication and authorization. It cannot control network access for devices.
There is a LOT of misinformation about the BlastRADIUS issue.
TACACS can't replace RADIUS. It has an unauthenticated mode, where all passwords are sent in clear-text across the wire. So it has MUCH worse security.
There is a LOT of misinformation about the BlastRADIUS issue.
TACACS can't replace RADIUS. It uses almost the same MD5-based constructs as RADIUS, so it doesn't increase security.
There is a LOT of misinformation about the BlastRADIUS issue.
Diameter isn't an option. Most common uses of Diameter have LESS security than RADIUS. And Diameter is being replaced with HTTPS3 (JSON over QUIC)
There is a LOT of misinformation about the BlastRADIUS issue. Almost all of this is covered in the paper at blastradius.fail
What doesn't work?
* Changing timeouts
* switching to Kerberos, Diameter, TACACS , IPSec