On 1 Sep 2001, at 11:05, Hugh Irvine wrote:
> There is nothing to configure.
> Radiator will handle the proxying and challenge/response automatically.
So, for example, the only way to ensure that Radiator would *not* respond to
an EAP challenge is to run a version 2.18.2 or below?
I was hoping there'd be a way to set a specific realm as capable of handling
EAP authentications and disabling that functionality in other realms via the
config file.
It'd also be nice to get an idea of what manufacturers implementations of EAP
Radiator is now compatible with - i.e. following Mike's 'open letter' about
Cisco policy on releasing specs it's for lightweight EAP, do these new
features support LEAP challenges?
Cheers,
M.
--
Mark O'Leary, Manchester Computing, UK
PGP Key and Further Details:
http://lucy.mcc.ac.uk/mark/mark.html
===
Archive at http://www.open.com.au/archives/radiator/
Announcements on [EMAIL PROTECTED]
To unsubscribe, email '[EMAIL PROTECTED]' with
'unsubscribe radiator' in the body of the message.
