Ashish Yadav wrote: > I am on UNIX, and from source code I now know that it is 3.11.5, but > as the link > http://www.mozilla.org/projects/security/pki/nss/nss-3.11/nss-3.11-algorithms.html > says that ( Some technologies listed here are not currently > implemented, but are planned for implementation in an upcoming > release.)
That comment is a left-over from long ago. At this point, it should be revised to say that some listed there are obsolete and have been removed. Anything involving FORTEZZA, for example, is no longer supported. > I need a full proof way to know exactly which algorithms are > getting included. Why do you need such proof? legal proceedings? talk radio? ?? > I know that in source code "/ashiyada/sb/ff1510/mozilla/security/nss/ > lib/ssl/sslenum.c" has got all the names of algorithms, but as many of Those are SSL/TLS cipher suite names, not algorithm names. Which do you need? > it is #ifdef on NSS_ENABLE_ECC, which I am able to find a way to know > whether it is enabled or not; I still don't know which ones are > getting included. Your question (apparently) concerns how some binaries were built. If you need proof, then you will need to get it from the built binaries, not from the sources, since the sources can obviously be built several different ways. > I even tried dissecting libnss3.so but to no avail. Try *using* it instead of dissecting it. _______________________________________________ dev-tech-crypto mailing list dev-tech-crypto@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-tech-crypto
