Alan, the last change you did yesterday appears to break shared secrets. commit c5967e80035e4fa2f66c22898a5cb7967e197c65 bsddev# radtest test@test.com test 127.0.0.1 1 blah Sending Access-Request of id 25 to 127.0.0.1 port 1812 ..... rad_recv: Access-Accept packet from host 127.0.0.1 port 1812, id=25, length=56 rad_verify: Received Access-Accept packet from client 127.0.0.1 port 1812 with invalid signature (err=2)! (Shared secret is incorrect.) I then recompiled with the commit just before that 72547c293eb3981747e4dc8baf3849528fb6adcd and...no problem. bsddev# radtest test@test.com test 127.0.0.1 1 blah Sending Access-Request of id 228 to 127.0.0.1 port 1812 .... rad_recv: Access-Accept packet from host 127.0.0.1 port 1812, id=228, length=56 I understand you may not be done yet with the patch...but anyway, that'll teach me for using the latest commit. -Gabe
On 14-Aug-09, at 3:44 PM, Gabriel Blanchard wrote:
the last change you did yesterday appears to break shared secrets. commit c5967e80035e4fa2f66c22898a5cb7967e197c65
Well I just submitted a patch through github. (not sure if that's the way you prefer). I also fixed a few things with my freetds module at the same time. -Gabe
Gabriel Blanchard wrote:
Well I just submitted a patch through github. (not sure if that's the way you prefer).
Yes. It makes a number of things easier.
I also fixed a few things with my freetds module at the same time.
OK. I'll see if I can pull those in before releasing 2.1.7 Alan DeKok.
participants (2)
-
Alan DeKok -
Gabriel Blanchard