From: Andrei N. B. <and...@ra...> - 2006-08-05 21:25:38
|
Hello Hoa. You wrote Friday, August 4, 2006, 4:20:10 PM: > 1. I was rather interested by something without callback. > However, if you think that's the only way or the best way to go > through this, > we'll go for this. > 4. The current API seems not to give explicit access to some > certificates, we only access to SSL context that are specific to > OpenSSL. Maybe we could give access directly to some certificate > data so that the user of API don't have to know anything about > certificates ? I think that callback is single good solution. If contain server sertificates, client sertificate etc in struct, user for example can want to set own callback in SSL_CTX. If send all SSL_CTX, user should know about version ssl/tls (ssl2/3, tls1) when create SSL_CTX. We need functionality allow change SSL_CTX after create it. Callback get this functionality. It is possible to give user functions to set sertificates in SSL_CTX for using in callback function. > 2. Do you have something that works with GnuTLS API ? (if you > are able to use GnuTLS in Window s environment) Unfortunately I know nothing about GnuTLS API. > 3. Try to avoid breakage of current API by introducing new > function names instead of > changing the prototype of current ones. > 5. Can you send the new patch as unified diff for readability > purpose ? I have corrected API using in this patch. I hope this patch is more readability. And I didn't find way to create mailstream(and create ssl_stream too) using mailsession_driver API. It need for mailsession_connect_stream function. How I should create mailstream? -- Best Regards, Andrei mailto:and...@ra... |