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

Request verification for accounting request is fixed. #99

Closed
wants to merge 1 commit into from
Closed

Request verification for accounting request is fixed. #99

wants to merge 1 commit into from

Conversation

pvragov
Copy link

@pvragov pvragov commented Oct 4, 2018

From https://tools.ietf.org/html/rfc2866

 3.  Packet Format
  .... 
 Request Authenticator
  In Accounting-Request Packets, the Authenticator value is a 16
  octet MD5 [5] checksum, called the Request Authenticator.

  The NAS and RADIUS accounting server share a secret.  The Request
  Authenticator field in Accounting-Request packets contains a one-
  way MD5 hash calculated over a stream of octets consisting of the
  Code + Identifier + Length + 16 zero octets + request attributes +
  shared secret (where + indicates concatenation).  The 16 octet MD5
  hash value is stored in the Authenticator field of the
  Accounting-Request packet.

  Note that the Request Authenticator of an Accounting-Request can
  not be done the same way as the Request Authenticator of a RADIUS
  Access-Request, because there is no User-Password attribute in an
  Accounting-Request.

@geaaru
Copy link
Contributor

geaaru commented Dec 10, 2018

Hi, take a look to my open pr... i fix a lot of things: #86

@pvragov
Copy link
Author

pvragov commented Oct 3, 2019

Hi! It seems that you've fixed this problem. Thanks for your answer.

@pvragov pvragov closed this Oct 3, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants