One should be able to edit the nss.def file to had critical functions not yet exported, and be able to rebuild NSS just fine, correct?
-- P "Wan-Teh Chang" <[EMAIL PROTECTED]> wrote in message [EMAIL PROTECTED]">news:[EMAIL PROTECTED]... > Kenneth R. Robinette wrote: > > > Wan-Teh > > > > After reading your note and thinking about it, I went back and compiled our > > application using only dll linkage. All went well except for one function, > > CERT_DecodeDERCertificate(). This is a rather common function required by > > many things, including the utilities supplied with NSS. Is there a > > replacement function I should be using that I have overlooked? > > > Bob Relyea is the best person to answer this question. Previously > he marked CERT_DecodeDERCertificate as NSS internal, which means > he thinks this function will be impossible to emulate on top of > the new NSS core API (code name Stan). > > Here is more background info. > > There are two reasons why we don't export an NSS function. > > 1. The NSS function is truly internal and simply should not > be exported. > > 2. No NSS client has asked us to export the function. > > You might be wondering about #2. This is because we have > not had time to review our public header files and make > sure that only the truly public functions are declared. > Therefore, we have been relying on the DLL export symbol > files as our last defense, to prevent NSS clients from > using the NSS internal functions. > > Wan-Teh >
