David Stutzman wrote:
We're using NSS/NSPR and JSS in different products we are currently developing.While attribution is nice, it's not required under any of the NSS licenses. When you ship NSS, you choose which license you ship under (MPL/GPL or LGPL... or the tri-license itself ). For the requirements of these licenses see http://www.mozilla.org/MPL/We're not making any proprietary/private changes to NSS/NSPR or JSS. We're strictly using the "libraries". In the case of NSS/NSPR what we plan on distributing are the shared libraries compiled by us (un-modified) and in the case of JSS, the JSS jar, .dll and/or .so directly from the mirrors.What type of attribution is needed? I was assuming something in the "About" box but I'd like to get an official response. I looked through the JSS pages, the NSS FAQ, the Mozilla Crypto FAQ, etc and I haven't seen something that says "If you are using NSS/NSPR/JSS in your application...do this:".
bob
Thanks, Dave _______________________________________________ dev-tech-crypto mailing list dev-tech-crypto@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-tech-crypto
smime.p7s
Description: S/MIME Cryptographic Signature
_______________________________________________ dev-tech-crypto mailing list dev-tech-crypto@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-tech-crypto
