Kostas Kalevras <[EMAIL PROTECTED]> wrote:
> > ahem... you've sent a patch? where? :)
>
> Hmm, typical :-)
> Ok included
It's probably easier just to assume the following:
- ask for default eap type, but allow the user to NAK,
and request another
- if EAP-Type is set to some value, require the user to use that
- if the user NAK's with another value, and EAP-Type is set,
then reject thm.
This makes EAP work much like PAP/CHAP/whatever. If you let the
server figure it out, it does. If you require FOO, then anything else
gets tossed.
I'll commit a fix today.
Alan DeKok.
-
List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
