The article does not talk about PEAP-MSCHAPv2. It talks about MS-CHAPv2 only.
With PEAP-MSCHAPv2 the MSCHAPv2 authentication is done inside a TLS tunnel that is encrypted. The article talks about EAP-MSCHAPv2 that does not use a TLS tunnel to encrypt the authenticatoin process. So PEAP-MSCHAPv2 is still running OK and thanks to the TLS tunnel that prevents the attackers from seeing the MSCHAPv2 messages that being exchanged. This is why a certificate is being used on the AAA server when you use PEAP-MSCHAPv2. But if you use EAP-MSCHAPv2 then the certificate is not needed on the server and the vulnerability in the article is applied.
Rating useful replies is more useful than saying "Thank you"
Transferring Crash file from standby:
Login to the Active WLC in HA.
(Cisco Controller) >transfer upload datatype crash
(Cisco Controller) >transfer upload filename <Desired filename>
(Cisco Controller) >transfer up...
This is the start of a display filter cross reference between Wireshark and OmniPeek.
The 1st installment is a table of advanced filters. More filters will be added as time allows.
It is a living doc, so check back for changes every so often
Please feel ...
I have created a Powershell script to automatically add a Wireless Guest User on Cisco WLCs. (tested on 2500 Series)
The script should be completely self explanatory.
Powershell SNMP Module (Install-Module -Name SNMP)
SNMP Write Access to...