> surely CUI only needs to be present in the Access-Accept packet? (for
> answer) and only in Access-Request for the CUI request?
Yes, I know that, that's why I'm concerned about the interactions here. I would expect that one set of keys, and the CUI generated either on the inner reply, or on the outer reply, survives.
I have two scenarios and two items in Access-Accept that need to be there, CUI and the MS-MPPE-*-Key attributes
1. FR 3.0.1 with use_tunneled_reply = yes
- auth with pam_gss: CUI present, multiple sets of MS-MPPE-*-Key present. (boo)
- auth with rad_eap_test: CUI present, one set of MS-MPPE-*-Key present. (hooray)
2. FR 3.0.1 with use_tunneled_reply = no
- auth with pam_gss: CUI present, one set of MS-MPPE-*-Key present. (hooray)
- auth with rad_eap_test: NO CUI present, one set of MS-MPPE-*-Key present. (boo)
The same occurs with the trust_router version (which is where I first spotted this).
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
|