-
Notifications
You must be signed in to change notification settings - Fork 60
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
How to decode radius packet without secret? #10
Comments
The secret is needed to decrypt the User-Password if present, and to verify the authenticator and/or Message-Authenticator . If the packet can be decoded but the authenticator does not match, the library throws a radius.InvalidSecretError exception with the decoded packet set as the exception's "decoded" attribute.
|
Thanks for your quick answer. Would you be interested in a pull request so that If it's not going to make it into the mainline code, I'll just use the code you wrote above. |
I would prefer adding a separate method to make it clear it is unsafe since it wouldn't force the user of the library to handle un-authenticatable messages. Also, passing in a null secret could very well be the result of an application error when using the library, in which case the accept-all-packets behavior might be unexpected. |
Wireshark can decode the fields of a radius packet without a secret.
This makes me think that the secret is not needed for decoding. Why does the node-radius API require it?
I have a server with multiple secrets, and need to know the value of an attribute inside of the radius packet, in order to choose which secret to use.
How can I achieve this?
The text was updated successfully, but these errors were encountered: