On Mon, May 18, 2015 at 4:40 PM, Randy Bush <ra...@psg.com> wrote: >> let's take the conversation off of nanog to spare the list. > > one of the purposes of this list is for us to learn from eachother. in > this case, techniques for diagnosing tls & cert issues are worth > sharing. [ sadly, folk with bugs love to redirect discussion off public > media ]
$ openssl s_client -servername www.nanog.org -connect www.nanog.org:443 CONNECTED(00000003) depth=3 C = US, O = "The Go Daddy Group, Inc.", OU = Go Daddy Class 2 Certification Authority .... stuff.... subject=/OU=Domain Control Validated/CN=*.nanog.org issuer=/C=US/ST=Arizona/L=Scottsdale/O=GoDaddy.com, Inc./OU=http://certs.godaddy.com/repository//CN=Go Daddy Secure Certificate Authority - G2 .... stuff ..... (I think you need to send along: -servername)
