Right they made this mistake with that particular URL only. I emailed a contact there. I'm sure it will be fixed shortly. All other url variants redirect to the https://www pattern which has a proper CA On Saturday, January 4, 2014, Joe St Sauver wrote:
Hi,
Jeremy noted:
#Testing in a browser (Firefox) for https://juniper.net/ results in this: # #juniper.net uses an invalid security certificate. #The certificate is not trusted because no issuer chain was provided. #(Error code: sec_error_unknown_issuer)
There are issues with more than just the cert. A more extensive analysis can be seen at:
https://www.ssllabs.com/ssltest/analyze.html?d=juniper.net
[FWIW, the SSL Labs tester is a tool I've previously recommended to folks in the higher ed community, e.g., as part of "SSL/TLS Certificiates: Giving Your Use of Server Certificates a Hard Look," http://pages.uoregon.edu/joe/hardlook/hard-look.pdf and most recently in "Networking in These Crazy Days: Stay Calm, Get Secure, Get Involved," http://pages.uoregon.edu/joe/merit-networking/merit-networking.pdf at slide 104. If you haven't checked your own site and critical sites you rely on, it can be eye opening to do so.]
Regards,
Joe _______________________________________________ Outages mailing list Outages@outages.org <javascript:;> https://puck.nether.net/mailman/listinfo/outages
-- Sent from Mobile