Lars,
I got stuck at part-II. After the server send the first packet (Request for
Identity, after confirm with Microsoft it
is one byte of value 1) in the TLS channel, there is no response from XP client. Any
chance you might look into this in
near future such that we might team up together to work this out? or someone else
might be interested in tackling this?
Thanks.
-Paul
> Lars
>
> I am using the EAP-TLS code base and tweek it to work
> up to the point of finishing PEAP Part I. Now XP can talk to
> my prototype up to the Part I.
Cool!
> Now I am getting into the Part
> II to send EAP packet under TLS tunnel. Could you suggest
> where to add the Part II code given the EAP-TLS code base?
> and how to bootstrap EAP code assuming everything recursively
> happening again?
Sorry, I haven't had time to look closely at this. However, obviously you would like
to hook into the rlm_eap module to
be able to reuse the existing EAP machinery. I suspect you'll have to modify this
module slightly to allow this.
> (PEAP is actually EAP-TLS-EAP, am I right?)
I guess you could say that it is EAP-TLS-EAP-X, where X is any EAP method.
-
List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
