-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
[defect]: TACACS and Dynamic Clients #5270
Comments
do you have the full gdb backtrace? The output below isn't overly useful:
you can run |
|
the call to I'll see if I can test it here. |
maybe
maybe |
I've seen this too. It's easy to reproduce. Just haven't had time to look into it. Basically any time dynamic clients is used with tacacs you get this crash. |
I believe that the commit above fixes it. If not, please re-open the bug report. |
Yes, this commit solved the problem. Then other errors occur. |
Dynamic clients share common code for TACACS+, RADIUS/UDP, and RADIUS/TCP. If it works for one, it should work for all of them. If there are other errors, then please open new issues for them. Or, post the errors to the freeradius-users mailing list. |
Hmm...
I can't find section definitions for dynamic clients or I haven't understood all the source code yet. |
@levide The RADIUS modules don't have dynamic clients listed there, either. It's somewhere else. The TACACS+ dynamic clients should work. If they don't, debug mode && gdb back traces will help a lot. |
What type of defect/bug is this?
Crash or memory corruption (segv, abort, etc...)
How can the issue be reproduced?
Configuration:
Log output from the FreeRADIUS daemon
Relevant log output from client utilities
No response
Backtrace from LLDB or GDB
The text was updated successfully, but these errors were encountered: