Requirement - Support for adding the Message-Authenticator attribute for requests

[retailnext]

Requirement - Support for adding the Message-Authenticator attribute for requests

[muirmanders]

Please try out 4986a70 and let me know if it resolves your issue.

[lirantal]

Hey,

I didn't get a chance to try this out yet, but I don't see how that's gonna work.
What is required is that node-radius actually need to build the Message-Authenticator attribute and add it to Status-Server (and also Access-Requests if you wish) packets.

[muirmanders]

Oops, didn't realize it was an attribute separate from the request authenticator (although your bug report was clear). I'll get this fixed soon. Thanks.

[lirantal]

Cool.
I've got actually got a working prototype I implemented which I can share,
just haven't got it at reach at the moment, so if you want to wait a couple
of days I'll be able to post it here.

On Fri, Feb 21, 2014 at 10:54 PM, muirmanders [email protected]:

Oops, didn't realize it was an attribute separate from the request
authenticator (although your bug report was clear). I'll get this fixed
soon. Thanks.

Reply to this email directly or view it on GitHubhttps://github.com//issues/3#issuecomment-35772536
.

Sincerely, Liran Tal

[muirmanders]

I've added support for the Message-Authenticator attribute in f4e2deb. Please verify it works for you.