On 11/10/11 05:02, Nelson B Bolyard wrote:
I'd say it's going to be difficult for the typical scripting language to do
the recommended instructions. How about putting the distrusted certs and
their trust objects in a separate file in the CVS repository?
What particularly do you think is
Wan-Teh Chang wrote:
Florian Weimer reported this issue to us.
The certdata.txt file in the NSS source tree
(http://mxr.mozilla.org/security/source/security/nss/lib/ckfw/builtins/certdata.txt)
is the master source of the NSS built-in trusted root CA list, so
people have written scripts to
Florian Weimer reported this issue to us.
The certdata.txt file in the NSS source tree
(http://mxr.mozilla.org/security/source/security/nss/lib/ckfw/builtins/certdata.txt)
is the master source of the NSS built-in trusted root CA list, so
people have written scripts to extract the trusted root CA
On 10/10/2011 12:16 PM, Wan-Teh Chang wrote:
After you match a trust object to a certificate, check the
CKA_TRUST_SERVER_AUTH, CKA_TRUST_EMAIL_PROTECTION, and
CKA_TRUST_CODE_SIGNING attributes in the trust object.
In the current version of certdata.txt, these attributes may have only
three
On 2011/10/10 12:16 PDT, Wan-Teh Chang wrote:
[...]
The certdata.txt file in the NSS source tree
(http://mxr.mozilla.org/security/source/security/nss/lib/ckfw/builtins/certdata.txt)
is the master source of the NSS built-in trusted root CA list, so
people have written scripts to extract the
5 matches
Mail list logo
