Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

net/freeradius - Error: It looks like the client has been updated to protect from the BlastRADIUS attack. #4250

Open
3 tasks done
ignitedPotato opened this issue Sep 24, 2024 · 0 comments

Comments

@ignitedPotato
Copy link

Important notices
Before you add a new report, we ask you kindly to acknowledge the following:

Describe the bug
FreeRadius logs the following error for every login request, even though the login itself still works:

2024-09-24T13:50:24	 	 	Auth: (0) Login OK: [xxx] (from client xxx port 0 cli xx-xx-xx-xx-xx-xx)	
2024-09-24T13:50:24	 	 	Error: !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!	
2024-09-24T13:50:24	 	 	Error: Please set "require_message_authenticator = true" for client xxx
2024-09-24T13:50:24	 	 	Error: It looks like the client has been updated to protect from the BlastRADIUS attack.	
2024-09-24T13:50:24	 	 	Error: !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!	
2024-09-24T13:50:24	 	 	Error: Setting "require_message_authenticator = true" for client xxx	
2024-09-24T13:50:24	 	 	Error: BlastRADIUS check: Received packet with Message-Authenticator.	
2024-09-24T13:50:24	 	 	Error: !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

I'm using a Unifi AP as a client which already fixed the BlastRADIUS issue.
Would it be possible to add require_message_authenticator as a field for clients?

Environment
OPNsense 24.7.4_1 (amd64).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

1 participant