On Thu, 22 Aug 2002, Daniel Stenberg wrote:

(uh, talking to myself again)

> The tool curl would then set CURLOPT_SSL_UNSAFE to TRUE by default (and
> show the warning text as discussed), and those who author bindings for
> libcurl would have to do the same to allow this kind of stunt.

I'm sometimes writing out things before I think.

Of course curl doesn't know what protocol(s) that will be used so this info
about "this is an unsecure SSL connection" is not really possible to do in
client code without some dirty checks.

I guess other libcurl-using applications will have a similar situation, so
this forces us to make any "warning text" get written by the library, and not
by the library-user.

I'll need to think this over one more lap. Comments are welcome.

-- 
 Daniel Stenberg -- curl related mails on curl related mailing lists please
-------------------------------------------------------
This sf.net email is sponsored by: OSDN - Tired of that same old
cell phone?  Get a new here for FREE!
https://www.inphonic.com/r.asp?r=sourceforge1&refcode1=vs3390