Thanks for your reply. We wanted to use JSS API in our Applet code to do digital signing. For this, we are planning to do auto install the DLLs needed such as jss3.dll, libnspr4.dll, libplc4.dll, libplsds4.dll, nss3.dll, ssl3.dll on the clients machines and use the APIs to access the clients nestcape default repository cert7.db and key3.db for the keys and certificate.
So, we are not going to modify the code of NSS/JSS Libraries. We are going to use it as is. For this, is it enough if we just simply say we are using JSS in our documentation or do we have to download the source code of nss and jss into our site and point to the url in a about dialog box or a link in our html pages. In MPL License document, under section 3.4 "Intellectual Property Matters" (a) Third party claims says about the LEGAL file, should we need to create a LEGAL file. If so, is there any specific information need to go there. Can we get a sample LEGAL file. These are the main questions, we have. Thanks Krish. Daniel Veditz wrote: > Krishnan Chellakarai wrote: > > Hi, > > > > We are planning to use NSS for Java libraries to achieve digital signing of > > HTML Form Fields. Can some one point me out, what are the steps we need to > > take care off, inorder for us to re-distribute those libraries. I read > > something about LEGAL file, do I need to worry about these. If so, can > > someone send me a sample of the LEGAL file. > > > > Thanks > > Krish. > > We tend to think the license itself spells out the steps you need to do. Any > attempt by us to paraphrase it colloquially here would be incomplete and > probably legally inaccurate by omission. As a non-lawyer I'd like not to be > sued for dispensing bad legal advice. > > If there are specific points of the license you have questions on I'm sure > several of us here will happily chime in with how we've interpreted those > points in our own projects. > > -Dan Veditz > (speaking as a fellow Mozilla hacker, not on my employer's behalf)
smime.p7s
Description: S/MIME Cryptographic Signature
