"Dave Thompson" wrote:
He could just do a:
echo foo | openssl s_client -connect "uri.com:443" > cert.txt
This executes in 1 sec here.
What openssl build on what Windows?
The one from the Msys package [1]. Running on Win-XP SP3.
It has a special dependency as shown here:
cygcheck g:\Mi
> From: owner-openssl-us...@openssl.org On Behalf Of Gisle Vanem
> Sent: Saturday, 06 July, 2013 07:16
> He could just do a:
> echo foo | openssl s_client -connect "uri.com:443" > cert.txt
>
> This executes in 1 sec here.
>
What openssl build on what Windows?
On my three Windows (XP SP3, Vi
echo foo | openssl s_client -connect "uri.com:443" > cert.txt
Or perhaps simpler
openssl s_client -connect "uri.com:443" > cert.txt http://www.openssl.org
User Support Mailing Listopenssl-users@openssl.org
Automated List Manager majord...@openssl
"Dave Thompson" wrote:
I don't see a simple fix. What you could do is write
a simple program that connects to the desired host, if
successful gets the peer cert and writes it out, and
(always immediately) closes and exits -- or just exits
and lets the OS-level TCP disconnect force a close.
> From: owner-openssl-us...@openssl.org On Behalf Of Graham, Dave
> Sent: Friday, 05 July, 2013 10:47
> I have a need to periodically extract a certificate from
> another automated process and not being a Windows programmer
> (I work in a different programming discipline) I find that a
> comman
