Wundergound certificate expired

63 views
Skip to first unread message

James Gray

unread,
Sep 15, 2019, 8:25:30 PM9/15/19
to weewx-user
The ever-helpful folks at IBM (Wunderground) have successfully let their certificate for uploading data expire:

>echo  | openssl s_client -showcerts -servername weatherstation.wunderground.com -connect weatherstation.wunderground.com:443 2>/dev/null | openssl x509 -text | grep -A9 -m 1 Certificate
Certificate:
    Data:
        Version: 3 (0x2)
        Serial Number:
            11:21:e6:fe:2c:40:75:75:4b:95:4a:bf:f0:86:35:80:d4:19
        Signature Algorithm: sha256WithRSAEncryption
        Issuer: C = BE, O = GlobalSign nv-sa, CN = GlobalSign Organization Validation CA - SHA256 - G2
        Validity
            Not Before: Oct 28 18:06:03 2014 GMT
            Not After : Sep 15 18:25:18 2019 GMT <-- Slow clap IBM :(
        Subject: C = US, ST = Georgia, L = Atlanta, O = The Weather Channel LLC, CN = *.wunderground.com 
 

Notice this affects both rtupdate.wunderground.com and weatherstation.wunderground.com (wildcard certificate). Any thoughts on how to ignore this without nuking the rest of the SSL certificate handling in Python? Or should we just wait until IBM/Wundergound sort their mess out?

Cheers,

James

James Gray

unread,
Sep 15, 2019, 10:21:01 PM9/15/19
to weewx-user
Logged a support case with Underground ant they have subsequently updated their certificate:

Certificate:
    Data:
        Version: 3 (0x2)
        Serial Number:
            0f:ae:6c:0b:ff:46:de:04:28:1a:60:86:2c:b4:ff:a9 <-- totally different serial
        Signature Algorithm: sha256WithRSAEncryption
        Issuer: C = US, O = DigiCert Inc, CN = DigiCert SHA2 Secure Server CA
        Validity
            Not Before: Aug 21 00:00:00 2019 GMT
            Not After : Aug 25 12:00:00 2021 GMT
        Subject: C = US, ST = Georgia, L = Atlanta, O = "The Weather Company, LLC", CN = *.wunderground.com
Reply all
Reply to author
Forward
0 new messages