-policy-bounces+volkan.nergiz=turktrust.com...@lists.mozilla.org]
On Behalf Of Jesus F
Sent: Thursday, March 5, 2015 12:32 PM
To: mozilla-dev-security-pol...@lists.mozilla.org
Subject: Re: TurkTrust Root Renewal Request
Hi Volkan,
Look at RFC2560/6960 section A.1, describing the format of a request
PLEASE post messages only to the mozilla.dev.security.policy newsgroup
or only to the dev-security-policy@lists.mozilla.org but not both. Each
feeds to the other.
Also, there is no such thing as the
mozilla-dev-security-pol...@lists.mozilla.org mailing list. The only
mailing list relevant to
@lists.mozilla.org;
mozilla-dev-security-pol...@lists.mozilla.org
Subject: Re: TurkTrust Root Renewal Request
Dear All,
The issue is actually quite clear and explicitly stated in TURKTRUST CP and
CPS documents. Please see
http://dl.turktrust.com.tr/pdf/TURKTRUST-CP-v09-SSL.pdf
http://dl.turktrust.com.tr/pdf
=turktrust.com...@lists.mozilla.org]
On Behalf Of Jesus F
Sent: Tuesday, March 3, 2015 6:28 PM
To: mozilla-dev-security-pol...@lists.mozilla.org
Subject: Re: TurkTrust Root Renewal Request
Hi all,
After some quick test of the OCSP Service I detect the following issues
related to the conformity
PM
To: mozilla-dev-security-pol...@lists.mozilla.org
Subject: Re: TurkTrust Root Renewal Request
Hi all,
After some quick test of the OCSP Service I detect the following issues related
to the conformity with CA/Browser Forum Baseline Requirements for the Issuance
and Management of Publicly
[mailto:dev-security-policy-bounces+volkan.nergiz=turktrust.com...@lists.mozilla.org]
On Behalf Of Jesus F
Sent: Tuesday, March 3, 2015 6:28 PM
To: mozilla-dev-security-pol...@lists.mozilla.org
Subject: Re: TurkTrust Root Renewal Request
Hi all,
After some quick test of the OCSP Service I detect
Dear All,
The issue is actually quite clear and explicitly stated in TURKTRUST CP and
CPS documents. Please see
http://dl.turktrust.com.tr/pdf/TURKTRUST-CP-v09-SSL.pdf
http://dl.turktrust.com.tr/pdf/TURKTRUST-CP-v09-SSL.pdf and
http://dl.turktrust.com.tr/pdf/TURKTRUST-CPS-v09-SSL.pdf
Hi all,
After some quick test of the OCSP Service I detect the following issues related
to the conformity with CA/Browser Forum Baseline Requirements for the Issuance
and Management of Publicly-Trusted Certificates (hereinafter BR) as required by
section 12 of Mozilla CA Certificate Inclusion
February 2015 13:49
To: Steve Roylance
Cc: Kathleen Wilson; mozilla-dev-security-pol...@lists.mozilla.org
Subject: Re: TurkTrust Root Renewal Request
My preference is to have key separation explicitly addressed by Mozilla and
CABForum. From strictly a security perspective sharing keys
] On Behalf Of Peter
Bowen
Sent: 26 February 2015 00:00
To: Steve Roylance
Cc: fhw...@gmail.com; mozilla-dev-security-pol...@lists.mozilla.org; Kathleen
Wilson
Subject: RE: TurkTrust Root Renewal Request
Steve,
Unless Peter is a member of the forum, the public list is a black hole, as
only
[mailto:fhw...@gmail.com]
Sent: 25 February 2015 21:52
To: Steve Roylance
Cc: Kathleen Wilson; mozilla-dev-security-pol...@lists.mozilla.org
Subject: Re: TurkTrust Root Renewal Request
Thanks for putting that together, Steve. Reading through the doc it
appears that
some of my concerns
Allowing a single cert to be used for both websites and code signing is a
dangerous proposition. What is the current thinking among the community?
Original Message
From: Kathleen Wilson
Sent: Thursday, February 12, 2015 12:31 PM
To: mozilla-dev-security-pol...@lists.mozilla.org
Subject:
What do you perceive the danger to be?
On Wed, Feb 18, 2015 at 9:30 AM, Peter Kurrasch fhw...@gmail.com wrote:
Allowing a single cert to be used for both websites and code signing is a
dangerous proposition. What is the current thinking among the community?
Original Message
From:
Message-
From: dev-security-policy [mailto:dev-security-policy-
bounces+steve.roylance=globalsign@lists.mozilla.org] On Behalf Of Peter
Kurrasch
Sent: 18 February 2015 14:31
To: Kathleen Wilson; mozilla-dev-security-pol...@lists.mozilla.org
Subject: Re: TurkTrust Root Renewal Request
14 matches
Mail list logo