I don't so much have a problem with the change but I would like to know if this
is fairly common across other cert issuers?
Personally I'm of the opinion that email is inherently insecure which makes it
a bad mechanism to use in the course of trying to establish trust. However, my
concern at
On 11/24/15 4:24 PM, Kathleen Wilson wrote:
On 11/19/15 11:00 PM, h-k...@secom.co.jp wrote:
Dear Kathleen-san,
The updated CP for detailed descrition(the certificate subscriber
owns/controls) about domain verification for the section 3.2.7 is
attached on bugzilla.
On 11/19/15 11:00 PM, h-k...@secom.co.jp wrote:
Dear Kathleen-san,
The updated CP for detailed descrition(the certificate subscriber
owns/controls) about domain verification for the section 3.2.7 is attached on
bugzilla.
https://bugzilla.mozilla.org/attachment.cgi?id=8689921
Email address
2015年11月13日金曜日 23時27分46秒 UTC+9 Kathleen Wilson:
> On 11/13/15 5:43 AM, Peter Kurrasch wrote:
> > Kathleen, is SECOM getting special treatment? I was wondering if there was
> > some reason to move forward before a CA has everything in order? Will we be
> > seeing more of this going forward?
> >
>
On 11/13/15 5:43 AM, Peter Kurrasch wrote:
Kathleen, is SECOM getting special treatment? I was wondering if there was some
reason to move forward before a CA has everything in order? Will we be seeing
more of this going forward?
I thought everything was in order, except perhaps there might
On 11/9/15 3:54 PM, Kathleen Wilson wrote:
SECOM has applied to enable EV treatment for the "Security Communication
RootCA2" root certificate that was included in NSS via Bugzilla Bug
#527419.
SECOM is a Japanese commercial CA that provides SSL and client
certificates for e-Government and
SECOM has applied to enable EV treatment for the "Security Communication
RootCA2" root certificate that was included in NSS via Bugzilla Bug #527419.
SECOM is a Japanese commercial CA that provides SSL and client
certificates for e-Government and participates in several projects for
financial
Dear Ryan-san and public discussion members,
The updated SECOM CP for Ryan-san's comment is attached to
https://bugzilla.mozilla.org/show_bug.cgi?id=1096205
CP (English): https://bugzilla.mozilla.org/attachment.cgi?id=8679302
The addition for the section 2.2, 3.2.7 and 4.9.9 addressed with
Dear Ryan-san and public discussion members,
The updated SECOM CP for Ryan-san's comment is attached to
https://bugzilla.mozilla.org/show_bug.cgi?id=1096205
CP (English): https://bugzilla.mozilla.org/attachment.cgi?id=8679302
The addition for the section 2.2, 3.2.7 and 4.9.9 addressed with
2015年8月26日水曜日 4時29分37秒 UTC+9 Ryan Sleevi:
> On Wed, August 5, 2015 2:51 pm, Kathleen Wilson wrote:
> > SECOM has applied to enable EV treatment for the "Security Communication
> > RootCA2" root certificate that was included in NSS via Bugzilla Bug
> > #527419.
> >
> > SECOM is a Japanese
2015年8月26日水曜日 4時29分37秒 UTC+9 Ryan Sleevi:
> On Wed, August 5, 2015 2:51 pm, Kathleen Wilson wrote:
> > SECOM has applied to enable EV treatment for the "Security Communication
> > RootCA2" root certificate that was included in NSS via Bugzilla Bug
> > #527419.
> >
> > SECOM is a Japanese
SECOM has applied to enable EV treatment for the Security Communication
RootCA2 root certificate that was included in NSS via Bugzilla Bug #527419.
SECOM is a Japanese commercial CA that provides SSL and client
certificates for e-Government and participates in several projects for
financial
12 matches
Mail list logo
