Hi Daniel/Dan/Yang: I did some more testing of my SecureTransport (aka curl_darwinssl) code recently, and found two things that need to be patched:
1. The code was printing a warning when SNI was set up successfully. Oops. 2. Printing the cipher number in verbose mode was something only TLS/SSL programmers might understand, so I had it print the name of the cipher, just like in the OpenSSL code. That'll be at least a little bit easier to understand. The SecureTransport API doesn't have a method of getting a string from a cipher like OpenSSL does, so I had to generate the strings manually. Here's a patch for your consideration... Nick Zitzmann <http://www.chronosnet.com/>
7-4darwinssl.patch
Description: Binary data
------------------------------------------------------------------- List admin: http://cool.haxx.se/list/listinfo/curl-library Etiquette: http://curl.haxx.se/mail/etiquette.html
