curl-users
Re: insecure (-k) requires "Common Name"
From: Daniel Stenberg <daniel_at_haxx.se>
Date: Sun, 24 Aug 2003 12:38:41 +0200 (CEST)
Date: Sun, 24 Aug 2003 12:38:41 +0200 (CEST)
On Sat, 23 Aug 2003, John McGowan wrote:
> A slight bug (perhaps) in using "-k" (insecure).
>
> I was trying to get a spammer's order page.
> He had created a certificate with "" (no)
> "Common Name". Even with the "-k" (allow insecure)
> flag, curl responds:
>
> * Closing connection #0
> curl: (51) SSL: unable to obtain common name from peer certificate
This happens because curl sets CURLOPT_SSL_VERIFYHOST to 1 when -k is used,
not 0. Using 0 would prevent this failure I think.
What do other people say, should we use 0 on -k?
-- Daniel Stenberg -- curl: been grokking URLs since 1998 ------------------------------------------------------- This SF.net email is sponsored by: VM Ware With VMware you can run multiple operating systems on a single machine. WITHOUT REBOOTING! Mix Linux / Windows / Novell virtual machines at the same time. Free trial click here:http://www.vmware.com/wl/offer/358/0Received on 2003-08-24