On Jan 6, 6:56 am, Brian Smith <bsm...@mozilla.com> wrote: > Ashok Subash wrote: > > We'll go with your suggestion of using NSS after size reduction for > > this project for our security requirements. But right now we cannot > > upgrade to latest firefox due to the current schedule and resources > > we have for this project. We will follow the guidelines listed in > > the 611781 as well your other suggestions in the mail. It will be > > great if you can support us if we hit a roadblock. > > The best way to get such support is to attach ask questions and to post your > patches in bugs in our bugzilla database. Try to write patches in a way that > is beneficial to the overall NSS and Gecko (Firefox) projects, so that we can > incorporate those patches into the mainline Gecko and/or NSS source code. If > you identify new ways to shrink NSS besides the ways listed in those bugs, > then please file new bugs and document your findings in them (And please CC > me in the bug report). It is likely that any such reductions in the size of > NSS that you make for Firefox 3.6 will be applicable to Firefox 12+ as our > usage of NSS hasn't changed much between 3.6 and 12. Whenever I get around to > working on bug 611781, the improvements I make will probably benefit your > project as well (possibly requiring some small modifications.) > > - Brian
Hi Brian, We have made some progress. We could statically build nss and link on our platform. Till now NSS Initialization has happened after redirect for URL http://mail.google.com through a proxy. From the logs i found that HTTP connect is sent to proxy successfully and 200 OK response successfully but after that we are not seeing the SSL handshake happening. We see connection refused error page being displayed. From the code perspective for some reason nsSSLIOLayerPoll is not being called. From what i understand TCP Socket Pair that is created for https sites helps is notifying necko whenever SSL thread IO (send/ recv) is completed. Is that understanding right? Currently for us the Connect of this local TCP socket pair is failing but we are able to go ahead as HTTP Connect happens successfully as mentioned earlier Is there any other porting points i've missed? Your inputs/suggestions will help us to solve this faster. Regards Ashok -- dev-tech-crypto mailing list dev-tech-crypto@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-tech-crypto
