Hello Berin, Haven't heared from you for a long long time... :)
> I've been working on getting the NSS provider > stuff working on my machine and have run into > a few snags. So some questions :>. I'm really happy someone will use NSS stuff. > 1. The includes in the NSS files are of the > form "nss/....h", which means I have to put > the nss include files into such a directory - > including nspr files, which on linux systems > (or at Debian) are separated intp nspr vs. nss > directories. Would we be better just > including as (for example) <cert.h> and then > having the user set what the directories are? > (Fits better with the mozilla model I think.) I agree. Change it. > 2. I'm having no joy with > __CERT_DecodeDERCertificate? From the comments > and from looking around it's a private function > that we can't see (or at least I can't when I link). Sorry, my comments were a little bit confusing. All you have to do to be able to link is to add declaration for CERT_DecodeDERCertificate() function in nss/cert.h file. Declaration should be identical to (already existing) __CERT_DecodeDERCertificate() function delaration. In other words linker is now looking for CERT_DecodeDERCertificate() and inside nss/cert.h is (only) __CERT_DecodeDERCertificate() declared. Best regards, Milan
