Custom Query (98 matches)
Results (19 - 21 of 98)
Ticket | Resolution | Summary | Owner | Reporter |
---|---|---|---|---|
#21 | wontfix | iLO web interfaces for pc1 and pc3 claim to have the same SSL issuer and serial number | ||
Description |
When i login to the web console for the pc3 iLO (at 155.98.34.104) using firefox, i get the standard firefox "do you want to trust this certificate?" dialogue, and am able to successfully connect. If i subsequently try to connect to the pc1 iLO (at 155.98.34.103) using the same firefox instance, i get the error: Secure Connection Failed An error occurred during a connection to 155.98.34.103. You have received an invalid certificate. Please contact the server administrator or email correspondent and give them the following information: Your certificate contains the same serial number as another certificate issued by the certificate authority. Please get a new certificate containing a unique serial number. (Error code: sec_error_reused_issuer_and_serial) The page you are trying to view can not be shown because the authenticity of the received data could not be verified. Please contact the web site owners to inform them of this problem. Alternatively, use the command found in the help menu to report this broken site. If i delete the SSL information for 155.98.34.104 from my browser and clear the cache, i can subsequently browse to .103 normally (but of course get this error again when i go back to .104). From the iLO logins, i see the following SSL information for the two devices:
So those serial numbers are indeed identical. I have verified that the other three iLOs have unique serial numbers (pc2=55, pc4=53, pc5=54), and do not experience this problem. |
|||
#22 | fixed | ops.utah.geniracks.net allows remote password-based login | ||
Description |
Two prospective issues related to password-based login to ops.utah.geniracks.net:
|
|||
#24 | fixed | how can site admins find the Emulab, FreeBSD base, and package source code used to install their system? | ||
Description |
There is a rack requirement that site admins be able to figure out where the software installed on their rack came from. In looking at boss.utah.geniracks.net (performing IG-MON-1 step 1), i was able to track down most things, but have the following three caveats in terms of tracking system binaries back to source code:
|