Security

last person joined: 21 hours ago 

Forum to discuss Enterprise security using HPE Aruba Networking NAC solutions (ClearPass), Introspect, VIA, 360 Security Exchange, Extensions, and Policy Enforcement Firewall (PEF).
Expand all | Collapse all

EAP-PEAP/MsCHAPv2 External SQL hashed password

This thread has been viewed 3 times
  • 1.  EAP-PEAP/MsCHAPv2 External SQL hashed password

    Posted Sep 20, 2017 10:27 AM

    Hi folks,

     

    We would like to use EAP-PEAP/MsCHAPv2 authentication on our wireless networks and implement a CPPM server. We have a legacy external postgesql, but the user's passwords stored only with SHA256 hash in it. I made a query but I get a REJECT message with user not found description. But if I add a new user with plain text password the authentication works well. Can anyone help for me, how can I resolve this ?

    Table structure:
    userid | username | password | ssid | created | modified

     

    Filter query: SELECT password AS User_Password, ssid AS SSID FROM Users WHERE username = '%{Authentication:Username}' AND ssid = LOWER('%{Radius:Aruba:Aruba-Essid-Name}');

     

     



  • 2.  RE: EAP-PEAP/MsCHAPv2 External SQL hashed password

    EMPLOYEE
    Posted Sep 20, 2017 10:29 AM
    The protocol does not allow this. You should look at EAP-TLS.


  • 3.  RE: EAP-PEAP/MsCHAPv2 External SQL hashed password

    Posted Sep 22, 2017 02:31 AM

    Hi Tim,

     

    Thanks for your quick answer. Can you explain  a llittle bit deeper, I don't understand why.

     



  • 4.  RE: EAP-PEAP/MsCHAPv2 External SQL hashed password
    Best Answer

    EMPLOYEE
    Posted Sep 27, 2017 10:31 AM

    In order to perform MSCHAPv2 authentication, you will need to have access to the NT-Hash of the password, which is a specific hash type.

     

    So you need either the NT-Hash of the password in your database and give ClearPass access to it, or have the unencrypted version of the password available so ClearPass can calculate the password.

     

    Please note that MSCHAPv2 is considered 'cracked' and no longer secure and should not be used unless you have full control over the client, like in an AD environment.

     



  • 5.  RE: EAP-PEAP/MsCHAPv2 External SQL hashed password

    EMPLOYEE
    Posted Sep 27, 2017 10:39 AM
    tl;dr, stop using PEAP ☺


  • 6.  RE: EAP-PEAP/MsCHAPv2 External SQL hashed password

    Posted Oct 05, 2017 09:03 AM

    Thanks guys! It is clear for me now.