On 16/05/2017 18:10, Peter Bowen wrote:
On Tue, May 16, 2017 at 9:00 AM, Jakob Bohm via dev-security-policy
<[email protected]> wrote:
Your post above is the first response actually saying what is wrong
with the Microsoft format and the first post saying all the
restrictions are actually in the certdata.txt file, and not just in the
binary file used by the the NSS library.
What "binary file" are you referring to? NSS is distributed as source
and I'm unaware of any binary file used by the NSS library for trust
decisions.
Source code for Mozilla products presumably includes some binary files
(such as PNG files), so why not a binary database file that becomes
that data that end users can view (and partially edit) in the Mozilla
product dialogs. Existence of a file named "generate_certdata.py",
which is not easily grokked also confused me into thinking that
certdata.txt was some kind of extracted subset.
Anyway, having now looked closer at the file contents (which does look
like computer output), I have been unable to find a line that actually
expresses any of the already established "gradual trusts".
Could you please point out where in certdata.txt the following are
expressed, as I couldn't find it in a quick scan:
1. The date restrictions on WoSign-issued certificates.
2. The EV trust bit for some CAs.
Enjoy
Jakob
--
Jakob Bohm, CIO, Partner, WiseMo A/S. https://www.wisemo.com
Transformervej 29, 2860 Søborg, Denmark. Direct +45 31 13 16 10
This public discussion message is non-binding and may contain errors.
WiseMo - Remote Service Management for PCs, Phones and Embedded
_______________________________________________
dev-security-policy mailing list
[email protected]
https://lists.mozilla.org/listinfo/dev-security-policy