On Wed, Sep 10, 2008 at 2:53 AM, Ibrar Ahmed <[EMAIL PROTECTED]> wrote: > Hi, > > I am currently working on porting "ssl_client_socket" to Linux. The current > implementation of "ssl_client_socket" uses Windows Security API. I wonder > why we have not used NSS library to implement SSL socket in Windows, because > it is available to many OS. I am not very good in Windows specific API's :( > > If there is no reason of doing this, should I rewrite this class again using > NSS and remove the Windows specific implemnation. If there are reason of > doing this can someone list here?
Hi Ibrar, Thank you for your interest in porting SSLClientSocket to Linux. As Dan pointed out, we should find out if someone else is already working on this. The Linux port of SSLClientSocket should be a separate file ssl_client_socket_nss.cc. (I'll rename the current ssl_client_socket.cc to ssl_client_socket_win.cc or ssl_client_socket_schannel.cc.) The reason is that the NSS-based implementation will be entirely different from the Schannel-based implementation for Windows. The reason we're using Schannel on Windows is that we want perfect integration with the OS credential stores. Although NSS does have code that integrates the Windows system certificate stores (see http://mxr.mozilla.org/security/source/security/nss/lib/ckfw/capi/) and Mac OS X Keychain (see http://mxr.mozilla.org/security/source/security/nss/lib/ckfw/nssmkey/), it is still experimental. Wan-Teh --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Chromium-dev" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/chromium-dev?hl=en -~----------~----~----~----~------~----~------~--~---
