Re: [Ejbca-develop] Incorrect organization referenced in "Keep Expired Certificates on CRL" documentation

[Tomas G. <to...@pr...>]

Hi Jaime,

The requirements were developed within CAB Forum, and CABF now has taken
over/back the code signing certificate minimum requirements document (in
addition to the EV guidelines currently in CABF). A ballot (see link) in
the Code Signing WG in CABF was just completed adopting the "old"
version, so they can start working on a new version. New updated
versions of the code signing certificate minimum requirements will be
released by CAB Forum.

Therefore I will leave the text as is. I believe the ballot has passed
now so it is actually a CAB Forum document now, albeit originally
published in CA Security Council.

https://cabforum.org/pipermail/cscwg-public/2019-April/000009.html

Regards,
Tomas


On 2019-07-22 01:17, Jaime Hablutzel wrote:
> The following from 
> https://download.primekey.com/docs/EJBCA-Enterprise/6_15_2/CA_Fields.html#src-23859254_id-.CAFieldsv6.15.0-KeepExpiredCertificatesonCRLKeep_Expired_Certificates_on_CRL:
> 
>     For example *CABForum* specifies this in their 'Minimum Requirements
>     for the Issuance and Management of Publicly-Trusted Code Signing
>     Certificates', version 1.1, section 13.2.1.
> 
> 
> Should be modified to:
> 
>     For example, *the CA Security Council* specifies this in their
>     'Minimum Requirements for the Issuance and Management of
>     Publicly-Trusted Code Signing Certificates', version 1.1, section
>     13.2.1.
> 
> 
> -- 
> Jaime Hablutzel -  +51 994690880
> 
> 
> _______________________________________________
> Ejbca-develop mailing list
> Ejb...@li...
> https://lists.sourceforge.net/lists/listinfo/ejbca-develop
>