Re: [cabfpub] Requirements language cleanup
I would potentially like to fix "Application Software Suppliers", and replace it with a better term, if others are interested. One possibility is to use Certificate Consumers, to more closely align with the Bylaws. -Tim From: Public On Behalf Of Dean Coclin via Public Sent: Friday, August 7, 2020 3:06 PM To: CABforum1 Subject: [cabfpub] Requirements language cleanup As mentioned on today's call, our team went through the CA/B Forum Baseline Requirements, EV Guidelines and Code Signing Guidelines to review for names which are being deprecated by the industry. The number found were very minor: In the EV Guidelines, the following text was found: "Denied Lists and Other Legal Black Lists" in Pg. iii Table of Contents 11.12.2 Black Lists; Pg. 30 11.12.2. Suggest changing to "Block Lists". In the EV Code Signing Guidelines, the following text was found: "In addition to checking revocation status, where practical, platforms should consult blacklists of suspect software". Suggest changing to "blocklist". This can be taken up by the code signing WG. In the TLS Baseline Requirements, there is reference to standard email addresses (page 19) used to contact parties for domain validation (i.e. webmaster, hostmaster, postmaster). However, I'm assuming these cannot be changed. I know there are some cleanup ballots either planned or underway and perhaps these can be included there. Dean Coclin DigiCert smime.p7s Description: S/MIME cryptographic signature ___ Public mailing list Public@cabforum.org https://lists.cabforum.org/mailman/listinfo/public
Re: [cabfpub] Requirements language cleanup
I think you can only add one of them to the cleanup ballot because the other is for EV Codesigning. From: Ryan Sleevi Sent: Friday, August 7, 2020 7:03 PM To: Dean Coclin ; CABforum1 Subject: Re: [cabfpub] Requirements language cleanup On Fri, Aug 7, 2020 at 3:05 PM Dean Coclin via Public mailto:public@cabforum.org> > wrote: As mentioned on today’s call, our team went through the CA/B Forum Baseline Requirements, EV Guidelines and Code Signing Guidelines to review for names which are being deprecated by the industry. The number found were very minor: In the EV Guidelines, the following text was found: “Denied Lists and Other Legal Black Lists” in Pg. iii Table of Contents 11.12.2 Black Lists; Pg. 30 11.12.2. Suggest changing to “Block Lists”. In the EV Code Signing Guidelines, the following text was found: “In addition to checking revocation status, where practical, platforms should consult blacklists of suspect software”. Suggest changing to “blocklist”. This can be taken up by the code signing WG. I can add both of these to the cleanups & clarifications ballot, now that I have endorsers, assuming they're OK with a last minute addition. In the TLS Baseline Requirements, there is reference to standard email addresses (page 19) used to contact parties for domain validation (i.e. webmaster, hostmaster, postmaster). However, I’m assuming these cannot be changed. Yes, these are from RFC 2142 I know there are some cleanup ballots either planned or underway and perhaps these can be included there. Dean Coclin DigiCert ___ Public mailing list Public@cabforum.org <mailto:Public@cabforum.org> https://lists.cabforum.org/mailman/listinfo/public smime.p7s Description: S/MIME cryptographic signature ___ Public mailing list Public@cabforum.org https://lists.cabforum.org/mailman/listinfo/public
Re: [cabfpub] Requirements language cleanup
On Fri, Aug 7, 2020 at 3:05 PM Dean Coclin via Public wrote: > As mentioned on today’s call, our team went through the CA/B Forum > Baseline Requirements, EV Guidelines and Code Signing Guidelines to review > for names which are being deprecated by the industry. The number found were > very minor: > > > > In the EV Guidelines, the following text was found: “Denied Lists and > Other Legal Black Lists” in Pg. iii Table of Contents 11.12.2 Black Lists; > Pg. 30 11.12.2. Suggest changing to “Block Lists”. > > > > In the EV Code Signing Guidelines, the following text was found: “In > addition to checking revocation status, where practical, platforms should > consult blacklists of suspect software”. Suggest changing to “blocklist”. > This can be taken up by the code signing WG. > I can add both of these to the cleanups & clarifications ballot, now that I have endorsers, assuming they're OK with a last minute addition. > > > In the TLS Baseline Requirements, there is reference to standard email > addresses (page 19) used to contact parties for domain validation (i.e. > webmaster, hostmaster, postmaster). However, I’m assuming these cannot be > changed. > Yes, these are from RFC 2142 > > > I know there are some cleanup ballots either planned or underway and > perhaps these can be included there. > > > > Dean Coclin > > DigiCert > > > ___ > Public mailing list > Public@cabforum.org > https://lists.cabforum.org/mailman/listinfo/public > ___ Public mailing list Public@cabforum.org https://lists.cabforum.org/mailman/listinfo/public
[cabfpub] Requirements language cleanup
As mentioned on today's call, our team went through the CA/B Forum Baseline Requirements, EV Guidelines and Code Signing Guidelines to review for names which are being deprecated by the industry. The number found were very minor: In the EV Guidelines, the following text was found: "Denied Lists and Other Legal Black Lists" in Pg. iii Table of Contents 11.12.2 Black Lists; Pg. 30 11.12.2. Suggest changing to "Block Lists". In the EV Code Signing Guidelines, the following text was found: "In addition to checking revocation status, where practical, platforms should consult blacklists of suspect software". Suggest changing to "blocklist". This can be taken up by the code signing WG. In the TLS Baseline Requirements, there is reference to standard email addresses (page 19) used to contact parties for domain validation (i.e. webmaster, hostmaster, postmaster). However, I'm assuming these cannot be changed. I know there are some cleanup ballots either planned or underway and perhaps these can be included there. Dean Coclin DigiCert smime.p7s Description: S/MIME cryptographic signature ___ Public mailing list Public@cabforum.org https://lists.cabforum.org/mailman/listinfo/public
