Hi Bastian, Again - you're talking about Entrust systems, not Sectigo. We did not acquire any Entrust systems - Entrust still own and operate those. As previously stated, Entrust are operating as a reseller of both Sectigo and SSL.com today, via their own platforms.
Regarding CAA - I specifically mentioned our CPS. The latest version can be found on sectigo.com/legal (as 'TLS Certification Practice Statement', currently version 6.0.1), and you'll need to look at section 4.2.4. Thanks, Nick On Monday, February 3, 2025 at 3:12:35 PM UTC Bastian Blank wrote: > On Mon, Feb 03, 2025 at 12:17:27AM -0800, 'Nick France' via > [email protected] wrote: > > Sectigo has nothing to do with the brand or assets of Entrust. They > remain > > with Entrust and were not part of this acquisition, as previously stated. > > However you clearly re-use some of the systems. From the Sectigo page, > it is clear that the Entrust management frontend is still in use: > > | Once the integration is in place later this year, you will be able to > | order Sectigo certificates directly from Entrust, and Sectigo will issue > | the certificates directly to you through Entrust Certificate Services > | (ECS). > > > Sectigo also have permission to use Entrust domains for CAA, and this > was > > added to our CPS last year. Sectigo have no current timeline to retire > this. > > Actually the section about CAA was completely removed from the latest > version (1.3.5). Could you please point us to it? > > https://www.sectigo.com/uploads/files/Sectigo_WebPKI_CP_v1_3_5.pdf > > The previsous version does not list "entrust.com" as valid. > > https://www.sectigo.com/uploads/files/Sectigo_WebPKI_CP_v1_3_4.pdf > > Bastian > > -- > ... bacteriological warfare ... hard to believe we were once foolish > enough to play around with that. > -- McCoy, "The Omega Glory", stardate unknown > -- You received this message because you are subscribed to the Google Groups "[email protected]" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion visit https://groups.google.com/a/mozilla.org/d/msgid/dev-security-policy/c0c25709-d475-4245-a901-3a542481650an%40mozilla.org.
