EXOS - Web Access enabled or disabled for HTTPS?


Userlevel 3
The command "show management" will show the status of the httpd service on an EXOS switch. The output would show both http and https status. It seems that with version 21 and later, this command now shows only HTTP service status regardless of the status of HTTPS.

The two questions are:

1. Is there a way in version 21+ to verify HTTPS status?
a. Extending that, to verify all access interfaces?
2. Are there any plans to allow the changing of listening port (for both HTTP and HTTPS)
from the defaults of 80 and 443?

5 replies

Userlevel 4
# show ssl

HTTPS Port Number: 443 (Disabled)

Signature Algorithm configured: sha512 With RSA Encryption

Certificate and Private key not configured

Manufacturing certificate: Not present
Userlevel 3
Matthew Helm wrote:

# show ssl

HTTPS Port Number: 443 (Disabled)

Signature Algorithm configured: sha512 With RSA Encryption

Certificate and Private key not configured

Manufacturing certificate: Not present

Thanks Matt, should have thought of that. I still think it needs to be in the show management command. Should be an easy (if very low priority) fix to put it back.
Userlevel 5
Mike,

Even from the configuration we could check the status of the http & https - "show configuration detail thttpd".


Userlevel 4
Both the outputs shared above accordingly specifying the details incorporated for Http and Https info and their status. Http(80) and Https(443) whereas SHA (512) with RSA encryption mode set.

Hence either way you can retrieve these info details.

Hope these explanation fetched you the direction which you were looking before....... If so then do let us know if we can close this ongoing discussion with the confirmation that this has clarified things moving forward.......
Userlevel 3
Tripathy, Priya Ranjan wrote:

Both the outputs shared above accordingly specifying the details incorporated for Http and Https info and their status. Http(80) and Https(443) whereas SHA (512) with RSA encryption mode set.

Hence either way you can retrieve these info details.

Hope these explanation fetched you the direction which you were looking before....... If so then do let us know if we can close this ongoing discussion with the confirmation that this has clarified things moving forward.......

Priya, See my comment to Matt. The behavior was changed and showing the config is not sufficient. If a case should be opened, please do, otherwise we'd have to file a FR. The least significant FR possible, but an FR nonetheless.

Reply