kjotte@daedalus:~$ openssl s_client -CApath /etc/ssl/certs -connect api-v1.weather.gov:443 CONNECTED(00000003) depth=0 OU = Domain Control Validated, CN = nws.noaa.gov verify error:num=20:unable to get local issuer certificate verify return:1 depth=0 OU = Domain Control Validated, CN = nws.noaa.gov verify error:num=21:unable to verify the first certificate verify return:1 --- Certificate chain 0 s:/OU=Domain Control Validated/CN=nws.noaa.gov i:/C=US/ST=Arizona/L=Scottsdale/O=GoDaddy.com, Inc./OU=http://certs.godaddy.com/repository//CN=Go Daddy Secure Certificate Authority - G2 --- Server certificate ... subject=/OU=Domain Control Validated/CN=nws.noaa.gov issuer=/C=US/ST=Arizona/L=Scottsdale/O=GoDaddy.com, Inc./OU=http://certs.godaddy.com/repository//CN=Go Daddy Secure Certificate Authority - G2 --- No client certificate CA names sent --- SSL handshake has read 2604 bytes and written 647 bytes ---
Does the i: line in that output mean the server is sending that intermediate cert or that it is expected? I want to make absolutely certain I've got this right before I go telling the federal government they've messed up. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1656054 Title: Unable to validate GoDaddy signed certs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ca-certificates/+bug/1656054/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
