> 2. 3.0.2-HEAD (without trust_router) with use_tunneled_reply = no,
> policy.d/cui modified with cui-inner.post-auth using "update
> outer.reply":
>
> pam_gss auth: Single set of MS-MPPE-*-Key + CUI
> rad_eap_test auth: Single set of MS-MPPE-*-Key + no CUI
I've been informed via the FreeRADIUS list that my rad_eap_test command was incorrect. I was testing with EAP-TTLS/MSCHAPv2, not EAP-TTLS/EAP-MSCHAPv2. The authentication mechanisms are of course different.
I should have used "EAPMSCHAPv2" with parameter -2, not just "MSCHAPV2". Now rad_eap_test has the same issue as pam_gss, and I'll crawl back into my hole now.
My apologies!
Stefan
--
This e-mail and any attachments may contain confidential, copyright and or privileged material, and are for the use of the intended addressee only. If you are not the intended addressee or an authorised recipient of the addressee please notify us of receipt by returning the e-mail and do not use, copy, retain, distribute or disclose the information in or attached to the e-mail.
Any opinions expressed within this e-mail are those of the individual and not necessarily of Diamond Light Source Ltd.
Diamond Light Source Ltd. cannot guarantee that this e-mail or any attachments are free from viruses and we cannot accept liability for any damage which you may sustain as a result of software viruses which may be transmitted in or with the message.
Diamond Light Source Limited (company no. 4375679). Registered in England and Wales with its registered office at Diamond House, Harwell Science and Innovation Campus, Didcot, Oxfordshire, OX11 0DE, United Kingdom
|