I've made a table which allows anyone to work out exactly which
certificates are in their version of a Mozilla product:
http://spreadsheets.google.com/pub?key=p49SW32nNYX3LqMK-jeDzfg
I would appreciate it if people could check it out and make sure that my
methodology is correct (even if they don't want to check all the data :-).
Basically, the principle was, for a given release:
- Find the release tag
- Get client.mk on that tag
- Find the value of NSS_CO_TAG in client.mk
- Find the version of certdata.txt on that new tag
- Record the version number, and what bugs were checked in after it left
the trunk
If I am correct, then it seems that the following Firefox minor release
transitions added new certs:
Firefox 1.0.1 -> 1.0.2
Firefox 1.5.0.9 -> 1.5.0.10
Firefox 2.0.0.0 -> 2.0.0.1
I would be particularly interested if anyone can confirm that this is
true (and I haven't worked it out wrong).
Gerv
_______________________________________________
dev-tech-crypto mailing list
dev-tech-crypto@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-tech-crypto
