Aruba Mobility Controllers use X.509 certificates to protect access to the web management interface and to provide secure wireless authentication, such as TLS, TTLS, PEAP, and Aruba-specific Captive Portal. By default, the controller uses a built-in certificate that is shared by all deployed units across all customers. This is broken for the obvious reasons.
261d3b68c595e71f7f735f8311f9fdecf9422bc0b3a44e597a6e76f1396bde07
© 2024 Packet Storm. All rights reserved.
%7Cutmcsr%3D(direct)%7Cutmcmd%3D(none)){kind=small}
Follow us on Twitter
Follow us on Facebook
Subscribe to an RSS Feed