RE: Know Extended Key Usage

2014-10-13 Thread Dave Thompson
> From: owner-openssl-us...@openssl.org On Behalf Of Lewis Rosenthal > Sent: Wednesday, October 08, 2014 10:57 > Actually, Jakob, I think it's the second one (the first one after the > pipe) which can come out, i.e.: > Yes. > openssl s_client -showcerts -connect google.com:443 < \ > /dev/null |

Re: Know Extended Key Usage

2014-10-08 Thread Jakob Bohm
Yep, middle of 3 openssl commands in the pipeline... On 08/10/2014 16:56, Lewis Rosenthal wrote: Hi, all... Actually, Jakob, I think it's the second one (the first one after the pipe) which can come out, i.e.: openssl s_client -showcerts -connect google.com:443 < \ /dev/null | openssl x509 -

Re: Know Extended Key Usage

2014-10-08 Thread Lewis Rosenthal
Hi, all... Actually, Jakob, I think it's the second one (the first one after the pipe) which can come out, i.e.: openssl s_client -showcerts -connect google.com:443 < \ /dev/null | openssl x509 -noout -text | grep -A1 "X509v3 Extended Key Usage" which seems to produce a little less noise, but

Re: Know Extended Key Usage

2014-10-08 Thread Jakob Bohm
I think you can safely omit the middle openssl command. On 08/10/2014 09:28, Akash Jain wrote: Thanks Lewis ! I also used - openssl s_client -showcerts -connect google.com:443 < /dev/null | openssl x509 -outform PEM | openssl x509 -noout -text | grep -A1 "X509v3 Exten

Re: Know Extended Key Usage

2014-10-08 Thread Akash Jain
Thanks Lewis ! I also used - openssl s_client -showcerts -connect google.com:443 < /dev/null | openssl x509 -outform PEM | openssl x509 -noout -text | grep -A1 "X509v3 Extended Key Usage" On Tue, Oct 7, 2014 at 11:40 PM, Lewis Rosenthal < lgrosent...@2rosenthals.com> wrote: > Hi, Akash... > > O

Re: Know Extended Key Usage

2014-10-07 Thread Lewis Rosenthal
Hi, Akash... On 10/08/2014 01:40 AM, Akash Jain wrote: HI, How can I know the "Extended Key Usage" parameters of a remote SSL enabled site using OpenSSL ? Does this help: https://www.madboa.com/geek/openssl/#cert-retrieve You could modify the one script there to something like: #!/bin/sh