Re: Unretrievable CPS documents listed in CCADB

2019-05-04 Thread Matt Palmer via dev-security-policy
On Sat, May 04, 2019 at 11:11:43AM +, Man Ho via dev-security-policy wrote:
> I could be wrong, but some browsers (IE/Chrome) seems to cache 
> downloaded PDF file and display the cache file if the filename is the 
> same. If it's true, end user may be actually reading an outdated PDF file.

If a browser is caching content retrieved from the target of a 307 Temporary
Redirect under the initial URI which issued the redirect, I'm *pretty* sure
that's a bug, and should be reported as such.

- Matt

___
dev-security-policy mailing list
dev-security-policy@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-security-policy


Re: Unretrievable CPS documents listed in CCADB

2019-05-04 Thread Man Ho via dev-security-policy
I could be wrong, but some browsers (IE/Chrome) seems to cache 
downloaded PDF file and display the cache file if the filename is the 
same. If it's true, end user may be actually reading an outdated PDF file.

- Man Ho

On 04-May-19 3:18 AM, Wayne Thayer via dev-security-policy wrote:
> A relatively simple solution to this problem is to create a "permanent
> link" to the current version of these docs (e.g.
> https://digicert.com/repository/current_cp.pdf), then modify or redirect
> the document that the link returns each time the document is updated as
> part of the publishing process. Under this scheme, the CA should never need
> to worry about updating CCADB.
___
dev-security-policy mailing list
dev-security-policy@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-security-policy


RE: Unretrievable CPS documents listed in CCADB

2019-05-03 Thread Ben Wilson via dev-security-policy
That approach could work.

 

From: Wayne Thayer  
Sent: Friday, May 3, 2019 1:19 PM
To: Ben Wilson 
Cc: Andrew Ayer ; Corey Bonnell ; 
mozilla-dev-security-pol...@lists.mozilla.org
Subject: Re: Unretrievable CPS documents listed in CCADB

 

On Fri, May 3, 2019 at 8:36 AM Ben Wilson via dev-security-policy 
mailto:dev-security-policy@lists.mozilla.org> > wrote:

I'm against having to continually update the exact URL of the CP and CPS in the 
CCADB.

 

 

A relatively simple solution to this problem is to create a "permanent link" to 
the current version of these docs (e.g. 
https://digicert.com/repository/current_cp.pdf), then modify or redirect the 
document that the link returns each time the document is updated as part of the 
publishing process. Under this scheme, the CA should never need to worry about 
updating CCADB.

 

  It's pretty easy to find the current CP and CPS from a legal repository.

 

 

But not as easy as getting it from a CCADB report, especially when the 
repository page doesn't clearly map a policy to a CA certificate.

 

  Plus, if we point to an exact one in the CCADB, it might not be the one that 
is applicable to a given certificate that was issued prior to the most current 
CPS.  In other words, you should look at when the certificate was issued and 
then figure out which CPS is applicable.  

 

I'm almost always looking for the current policy rather than trying to identify 
the version applicable to a specific certificate.

 

-Original Message-
From: dev-security-policy mailto:dev-security-policy-boun...@lists.mozilla.org> > On Behalf Of Andrew 
Ayer via dev-security-policy
Sent: Thursday, May 2, 2019 8:16 PM
To: mozilla-dev-security-pol...@lists.mozilla.org 
<mailto:mozilla-dev-security-pol...@lists.mozilla.org> 
Subject: Re: Unretrievable CPS documents listed in CCADB

On Thu, 2 May 2019 18:53:39 -0700 (PDT)
Corey Bonnell via dev-security-policy
mailto:dev-security-policy@lists.mozilla.org> > wrote:

> As an aside, I noticed that several URLs listed in CCADB are “Legal 
> Repository” web page URLs that contain a list of many CP/CPS 
> documents. My recommendation is to slightly amend CCADB Policy to 
> require CAs to provide URLs to the specific document in question 
> rather than a general “Legal Repository” page, where it is left up to 
> the reader to decide which hyperlink on the page is the correct 
> document.

+1.  It's often a real hassle to find the CP/CPS for a CA.  Linking
directly to the document would help a lot.



smime.p7s
Description: S/MIME cryptographic signature
___
dev-security-policy mailing list
dev-security-policy@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-security-policy


Re: Unretrievable CPS documents listed in CCADB

2019-05-03 Thread Wayne Thayer via dev-security-policy
On Fri, May 3, 2019 at 8:36 AM Ben Wilson via dev-security-policy <
dev-security-policy@lists.mozilla.org> wrote:

> I'm against having to continually update the exact URL of the CP and CPS
> in the CCADB.



A relatively simple solution to this problem is to create a "permanent
link" to the current version of these docs (e.g.
https://digicert.com/repository/current_cp.pdf), then modify or redirect
the document that the link returns each time the document is updated as
part of the publishing process. Under this scheme, the CA should never need
to worry about updating CCADB.


>   It's pretty easy to find the current CP and CPS from a legal repository.



But not as easy as getting it from a CCADB report, especially when the
repository page doesn't clearly map a policy to a CA certificate.

  Plus, if we point to an exact one in the CCADB, it might not be the one
> that is applicable to a given certificate that was issued prior to the most
> current CPS.  In other words, you should look at when the certificate was
> issued and then figure out which CPS is applicable.
>
>
I'm almost always looking for the current policy rather than trying to
identify the version applicable to a specific certificate.


> -Original Message-
> From: dev-security-policy 
> On Behalf Of Andrew Ayer via dev-security-policy
> Sent: Thursday, May 2, 2019 8:16 PM
> To: mozilla-dev-security-pol...@lists.mozilla.org
> Subject: Re: Unretrievable CPS documents listed in CCADB
>
> On Thu, 2 May 2019 18:53:39 -0700 (PDT)
> Corey Bonnell via dev-security-policy
>  wrote:
>
> > As an aside, I noticed that several URLs listed in CCADB are “Legal
> > Repository” web page URLs that contain a list of many CP/CPS
> > documents. My recommendation is to slightly amend CCADB Policy to
> > require CAs to provide URLs to the specific document in question
> > rather than a general “Legal Repository” page, where it is left up to
> > the reader to decide which hyperlink on the page is the correct
> > document.
>
> +1.  It's often a real hassle to find the CP/CPS for a CA.  Linking
> directly to the document would help a lot.
>
>
___
dev-security-policy mailing list
dev-security-policy@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-security-policy


Re: Unretrievable CPS documents listed in CCADB

2019-05-03 Thread Jakob Bohm via dev-security-policy
hat is applicable to a given certificate that was issued prior to the 
most current CPS.  In other words, you should look at when the certificate was 
issued and then figure out which CPS is applicable.

-Original Message-
From: dev-security-policy  On 
Behalf Of Andrew Ayer via dev-security-policy
Sent: Thursday, May 2, 2019 8:16 PM
To: mozilla-dev-security-pol...@lists.mozilla.org
Subject: Re: Unretrievable CPS documents listed in CCADB

On Thu, 2 May 2019 18:53:39 -0700 (PDT)
Corey Bonnell via dev-security-policy
 wrote:


As an aside, I noticed that several URLs listed in CCADB are “Legal
Repository” web page URLs that contain a list of many CP/CPS
documents. My recommendation is to slightly amend CCADB Policy to
require CAs to provide URLs to the specific document in question
rather than a general “Legal Repository” page, where it is left up to
the reader to decide which hyperlink on the page is the correct
document.


+1.  It's often a real hassle to find the CP/CPS for a CA.  Linking
directly to the document would help a lot.



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
dev-security-policy@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-security-policy


RE: Unretrievable CPS documents listed in CCADB

2019-05-03 Thread Ben Wilson via dev-security-policy
I'm against having to continually update the exact URL of the CP and CPS in the 
CCADB.  It's pretty easy to find the current CP and CPS from a legal 
repository.  Plus, if we point to an exact one in the CCADB, it might not be 
the one that is applicable to a given certificate that was issued prior to the 
most current CPS.  In other words, you should look at when the certificate was 
issued and then figure out which CPS is applicable.  

-Original Message-
From: dev-security-policy  On 
Behalf Of Andrew Ayer via dev-security-policy
Sent: Thursday, May 2, 2019 8:16 PM
To: mozilla-dev-security-pol...@lists.mozilla.org
Subject: Re: Unretrievable CPS documents listed in CCADB

On Thu, 2 May 2019 18:53:39 -0700 (PDT)
Corey Bonnell via dev-security-policy
 wrote:

> As an aside, I noticed that several URLs listed in CCADB are “Legal 
> Repository” web page URLs that contain a list of many CP/CPS 
> documents. My recommendation is to slightly amend CCADB Policy to 
> require CAs to provide URLs to the specific document in question 
> rather than a general “Legal Repository” page, where it is left up to 
> the reader to decide which hyperlink on the page is the correct 
> document.

+1.  It's often a real hassle to find the CP/CPS for a CA.  Linking
directly to the document would help a lot.
___
dev-security-policy mailing list
dev-security-policy@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-security-policy


smime.p7s
Description: S/MIME cryptographic signature
___
dev-security-policy mailing list
dev-security-policy@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-security-policy


Re: Unretrievable CPS documents listed in CCADB

2019-05-03 Thread Sándor dr . Szőke via dev-security-policy
2019. május 3., péntek 3:53:49 UTC+2 időpontban Corey Bonnell a következőt írta:
> 3209, "Microsec Ltd.", "e-Szigno Class2 CA 2017", 
> https://static.e-szigno.hu/docs/szsz--fok--sea--EN--v2.8.pdf, 404
> 3211, "Microsec Ltd.", "e-Szigno Class3 CA 2017", 
> https://static.e-szigno.hu/docs/szsz--fok--sig--EN--v2.8.pdf, 404
> 3216, "Microsec Ltd.", "e-Szigno Qualified CA 2017", 
> https://static.e-szigno.hu/docs/szsz--min--sig--EN--v2.8.pdf, 404
> 3217, "Microsec Ltd.", "e-Szigno Qualified Organization CA 2017", 
> https://static.e-szigno.hu/docs/szsz--min--sea--EN--v2.8.pdf, 404

The filenames werw incorrect in the CCADB.

I have corrected and checked all url-s.

Sorry for causing problems.

Sándor Szőke   
Microsec
___
dev-security-policy mailing list
dev-security-policy@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-security-policy


Re: Unretrievable CPS documents listed in CCADB

2019-05-02 Thread Andrew Ayer via dev-security-policy
On Thu, 2 May 2019 18:53:39 -0700 (PDT)
Corey Bonnell via dev-security-policy
 wrote:

> As an aside, I noticed that several URLs listed in CCADB are “Legal
> Repository” web page URLs that contain a list of many CP/CPS
> documents. My recommendation is to slightly amend CCADB Policy to
> require CAs to provide URLs to the specific document in question
> rather than a general “Legal Repository” page, where it is left up to
> the reader to decide which hyperlink on the page is the correct
> document.

+1.  It's often a real hassle to find the CP/CPS for a CA.  Linking
directly to the document would help a lot.
___
dev-security-policy mailing list
dev-security-policy@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-security-policy