Timeline for Is it possible for an 802.1x network (PEAP/MSCHAPv2) to have no certificate?
Current License: CC BY-SA 3.0
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Apr 27, 2022 at 17:20 | comment | added | YLearn | The supplicant can still check the validity of the certificate, which is why providing as much of the configuration for the certificate is important if the device supports it. If you have configured the specific hostname and the CA that signed the certificate, it can be difficult to provide a falsified certificate. If you configure the supplicant to not validate the certificate at all, then it doesn't even need to be a falsified certificate (as any will do). | |
| Jan 5, 2022 at 18:04 | comment | added | retriever123 | Thanks for the details on the handshake. If the client can't reach out to the Root CA to validate the server certificate, what prevents a malicious AP from presenting a falsified certificate? This may be naive, as I I don't understand certificates well, so I'm just hoping for someone to point me to a resource | |
| Mar 31, 2018 at 9:49 | vote | accept | voices | ||
| Mar 31, 2018 at 8:13 | history | edited | YLearn | CC BY-SA 3.0 |
added 2 characters in body
|
| Mar 31, 2018 at 7:48 | comment | added | YLearn | @tjt263, the EAP supplicant is the software that performs the 802.1X authentictaion to the RADIUS server. Is it not a service as it doesn't run in the background, rather it is called when an 802.1X authentication is needed. Once the authentication is done, it is no longer needed, so there is no reason for it to continue running. | |
| Mar 30, 2018 at 20:22 | history | answered | YLearn | CC BY-SA 3.0 |