Uploaded image for project: 'Data Management'
  1. Data Management
  2. DM-11436

update status.lsst.codes TLS cert for 2017

    Details

      Attachments

        Issue Links

          Activity

          Hide
          jhoblitt Joshua Hoblitt added a comment -

          Note that status.lsst.codes is responding with a different tls cert if the servername isn't part of the HTTP request:

          $ openssl s_client -connect status.lsst.codes:443 -servername status.lsst.codes 2>/dev/null  | openssl x509 -noout -dates 
          notBefore=Jul 28 21:07:28 2017 GMT
          notAfter=Sep  7 16:38:00 2018 GMT
          ^C
          $ openssl s_client -connect status.lsst.codes:443 2>/dev/null  | openssl x509 -noout -dates 
          notBefore=Nov 17 22:27:17 2016 GMT
          notAfter=Nov 17 22:27:17 2017 GMT
          

          Show
          jhoblitt Joshua Hoblitt added a comment - Note that status.lsst.codes is responding with a different tls cert if the servername isn't part of the HTTP request: $ openssl s_client -connect status.lsst.codes: 443 -servername status.lsst.codes 2 >/dev/ null | openssl x509 -noout -dates notBefore=Jul 28 21 : 07 : 28 2017 GMT notAfter=Sep 7 16 : 38 : 00 2018 GMT ^C $ openssl s_client -connect status.lsst.codes: 443 2 >/dev/ null | openssl x509 -noout -dates notBefore=Nov 17 22 : 27 : 17 2016 GMT notAfter=Nov 17 22 : 27 : 17 2017 GMT

            People

            • Assignee:
              athornton Adam Thornton
              Reporter:
              jhoblitt Joshua Hoblitt
              Reviewers:
              Joshua Hoblitt
              Watchers:
              Joshua Hoblitt
            • Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Summary Panel