[Servercert-wg] Ballot SC27: Version 3 Onion Certificates
wthayer at gmail.com
Tue Jan 28 08:15:56 MST 2020
This is version 2 of ballot SC27: Version 3 Onion Certificates. I have made
the clarifications to section 18.104.22.168 discussed in this thread, updated the
URL in Appendix C to the canonical link to the Tor spec, and reset the
discussion period to 7 days.
Purpose of Ballot:
This ballot will permit CAs to issue DV and OV certificates containing Tor
onion addresses using the newer version 3 naming format.
In ballot 144, later clarified by ballots 198/201, the Forum created rules
for issuing EV certificates containing onion addresses. A primary reason
for requiring EV level validation was that onion addresses were
cryptographically weak, relying on RSA-1024 and SHA-1. More recently a
newer "version 3" addressing scheme has removed these weaknesses. For much
the same reason that EV certificates are not always a viable option for
website operators (e.g. sites operated by individuals), many onion sites
would benefit from the availability of DV and OV certificates for version 3
The Tor Service Descriptor Hash extension required in the EV Guidelines to
contain the full hash of the keys related to the .onion address is no
longer needed as this hash is part of the version 3 address.
Older version 2 onion addresses are still in use, so this ballot does not
remove the existing EV Guidelines requirements for onion names.
Reference to discussion of EV onion certificates:
Reference to reasons we required EV in the past:
Reference to prior discussion of this topic:
The following motion has been proposed by Wayne Thayer of Mozilla and
endorsed by Roland Shoemaker of Let's Encrypt and Dimitris Zacharopoulos of
-- MOTION BEGINS --
This ballot modifies the “Baseline Requirements for the Issuance and
Management of Publicly-Trusted Certificates” as follows, based on Version
1.6.7, or based on Version 1.6.7 as modified by ballot SC25:
ADD a paragraph to section 22.214.171.124 of the Baseline Requirements as defined
in the following redline:
ADD Appendix C to the Baseline Requirements as defined in the following
This ballot modifies the "Guidelines for the Issuance and Management of
Extended Validation Certificates" as follows based on version 1.7.1:
MODIFY Appendix F as defined in the following redline:
-- MOTION ENDS --
This ballot proposes two Final Maintenance Guidelines.
The procedure for approval of this ballot is as follows:
Discussion (7+ days)
Start Time: 25-January 2020 00:00 UTC
End Time: No earlier than 04-February 2020 16:00 UTC
Vote for approval (7 days)
Start Time: TBD
End Time: TBD
On Tue, Jan 28, 2020 at 12:27 AM Tobias S. Josefowitz <tobij at opera.com>
> On Mon, 27 Jan 2020, Wayne Thayer wrote:
> > Thank you Tobias, that is a great point. My intent was not to require a
> > cert containing an onion name to contain only onion names. Does the
> > following change (in all caps) to section 126.96.36.199 fix that?
> > The CA SHALL confirm that prior to issuance, the CA has validated each
> > Fully-Qualified Domain Name (FQDN), other than a Domain Name with .onion
> > the right-most label of the Domain Name, listed in the Certificate using
> > least one of the methods listed below. In addition, when issuing a
> > Certificate that includes an FQDN with "onion" as the rightmost label,
> > CA SHALL confirm that prior to issuance, the CA has validated each FQDN
> > listed in the Certificate with "onion" as the rightmost label in
> > with Appendix C.
> I think that works, however
> s/\.onion/"onion"/ for consistency.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Servercert-wg