[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
ARO Security
- Subject: ARO Security
- From: morrowc.lists at gmail.com (Christopher Morrow)
- Date: Mon, 18 May 2015 16:50:33 -0400
- In-reply-to: <m2twv9sjoy.wl%[email protected]>
- References: <CAGALboaH-JCoShu9JZymCvkFHH308AQaz29-5kzK=M+xWNqYkw@mail.gmail.com> <CAHd7N8Ptq4=yp1L_MHFM3WSh5eejfi=tPizX5NP572QKceNfuQ@mail.gmail.com> <m2twv9sjoy.wl%[email protected]>
On Mon, May 18, 2015 at 4:40 PM, Randy Bush <randy at 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)
- References:
- ARO Security
- From: nicholas.schmidt at controlgroup.com (Nicholas Schmidt)
- ARO Security
- From: eric.oosting at gmail.com (Eric Oosting)
- ARO Security
- From: randy at psg.com (Randy Bush)