Wireless Access

last person joined: 13 hours ago 

Access network design for branch, remote, outdoor, and campus locations with HPE Aruba Networking access points and mobility controllers.
Back to discussions
Expand all | Collapse all

Is SHA1 used in aruba controller self-signed cert? How about SHA2 cert?

This thread has been viewed 1 times

  • 1.  Is SHA1 used in aruba controller self-signed cert? How about SHA2 cert?

    Posted Apr 07, 2016 10:23 PM

    Hi, is SHA1 used in current Aruba controller self-signed cert? As web browsers will use SHA2 on coming future, will be a compatible issue in the future? Please advise ,thanks



  • 2.  RE: Is SHA1 used in aruba controller self-signed cert? How about SHA2 cert?

    EMPLOYEE
    Posted Apr 07, 2016 10:25 PM
    As a best practice, you should not use the built in cert in production.

    Sent from Nine<>


  • 3.  RE: Is SHA1 used in aruba controller self-signed cert? How about SHA2 cert?
    Best Answer

    EMPLOYEE
    Posted Apr 07, 2016 10:31 PM

    There is not currently a self-signed cert within the controllers - the cert that ships by default comes from a CA.  And yes, it uses SHA-1.  If you're actually using that cert in a production network, SHA-1 is the least of your worries.  You should not use the default certificate - ever.

     

    In future versions of ArubaOS, the controller will generate a self-signed cert.  This cert will be signed using SHA-2.  On the other hand - the signature is meaningless (it is self-signed) so I don't think it particularly matters what we use.  You'll either need to a) replace that cert with something from a CA (the preferred approach) or save and pin the public key.