Once EAP-Identity response is received by the server, based on the
default_eap_type, the server will send a new request (MD5-Challenge
request incase of md5, TLS-START request incase of tls) to the supplicant.
- If the supplicant is rfc2284 compliant and doesnot support the
+ If the supplicant is rfc2284 compliant and does not support the
EAP-Type sent by the server then it sends EAP-Acknowledge with the
supported EAP-Type. If this EAP-Type is supported by the server then it
will send the respective EAP-request.
/*
****
- * EAP - LEAP doesnot specify code, id & length but chap specifies them,
+ * EAP - LEAP does not specify code, id & length but chap specifies them,
* for generalization purpose, complete header should be sent
* and not just value_size, value and name.
* future implementation.
/*
****
- * EAP - MD5 doesnot specify code, id & length but chap specifies them,
+ * EAP - MD5 does not specify code, id & length but chap specifies them,
* for generalization purpose, complete header should be sent
* and not just value_size, value and name.
* future implementation.