Frank Hecker wrote:
> Network Solutions has applied to add a new root CA certificate to the
> Mozilla root store and enable it for EV, as documented in the following
> bug:
>
> https://bugzilla.mozilla.org/show_bug.cgi?id=403915
> I have evaluated this request, as per the mozilla.org CA certi
Kick Willemse:
LS,
I think if e-mail is configured as *rfc822Name*=*email* it is
something that is included within the altname. More and more you see
certificate issuers using this field.
Oh right, so I haven't seen it a lot yet...guess because of that I
missed it...
Another option i
LS,
I think if e-mail is configured as rfc822Name=email it is something that is
included within the altname. More and more you see certificate issuers using
this field.
Another option is to include the e-mail within the subjectdname: email=. In
that case there is nothing stated about validat
Frank Hecker:
The EV guidelines reference RFC 3280 as the guiding document on matters
not addressed in the EV guidelines themselves. Section 4.2.1.7 of RFC
3280 allows (and recommends that) email addresses to be included in a
certificate using the subjectAltName extension; it also says
Bec
Frank Hecker wrote:
> Appendix C of the EV guidelines contains requirements relating to EV
> certificate extensions.
My apologies, that reference should be to Appendix B of the EV guidelines.
Frank
--
Frank Hecker
[EMAIL PROTECTED]
___
dev-tech-crypt
Eddy Nigg (StartCom Ltd.) wrote:
> Perhaps in that case email addresses MUST not be included in server
> certificates and extended key usage MUST be present and NOT include
> E-mail protection. I'm not 100% sure about any requirement in that
> respect and/or if additional key usage (such as Key/
LS,
I will post a request on this on the CABForum to see what they say about this.
I know there is a F-t_F meeting upcoming in Oslo, maybe this can be on the
agenda.
Kick
-
Kick Willemse
Product Manager
e-mail:
7 matches
Mail list logo
