> I would not build a scheme based on NSS because NSS is not a prerequisite > unless you force people to use Firefox. We arent forcing. We already support Microsoft, OSX and Google browsers, and (trying) Firefox too.
> Hooking Mozilla/NSS into native APIs like CryptoAPI is a much more important > task. IIUC...will someday Mozilla hook NSS with System (Windows or OSX)? >> Quoting bsmedberg (https://bugzilla.mozilla.org/show_bug.cgi?id=654939#c19): >> "No, writing enterprise apps which poke into the Firefox certificate store >> is not a desired use-case" Is that the official Mozilla position? >> I'll ask another way: Is there any argument against compiling NSS with >> @loader_path instead of current @executable_path? >> (https://bugzilla.mozilla.org/show_bug.cgi?id=578751) Will patches be accepted (if correct), or "some people" want @executable_path, rather than @loader_path ? -- dev-tech-crypto mailing list dev-tech-crypto@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-tech-crypto
