On Tue, Jan 19, 2016 at 03:43:21PM -0500, Alan DeKok wrote:
On Jan 19, 2016, at 3:39 PM, Matthew Newton <mcn4@leicester.ac.uk> wrote:
I'm probably fairly unusual in having an eap instantiation (two even) that's not called "eap".
I've done some more spelunking, and calling the "eap" module is only done when it's proxying the inner-tunnel EAP data. I've pushed fixes which convert the error into a WARNING, which won't break existing configurations.
OK thanks - I'll push that out right now to test it.
Auth-Type back_door { if ((User-Name == "bob") && (User-Password == "bob")) { accept } else { pap } }
:)
Ssshhhh! Don't put that on a public mailing list. The next question is guaranteed to be "I've just done this with eap, and it doesn't work!!!" :) Cheers, Matthew -- Matthew Newton, Ph.D. <mcn4@le.ac.uk> Systems Specialist, Infrastructure Services, I.T. Services, University of Leicester, Leicester LE1 7RH, United Kingdom For IT help contact helpdesk extn. 2253, <ithelp@le.ac.uk>