[You don't often get email from andrey@xdel.ru. Learn why this is important at
https://aka.ms/LearnAboutSenderIdentification ]
On Tue, Apr 16, 2024 at 10:30 PM Kaj Niemi <kajtzu@basen.net> wrote:
>
> Hi,
>
>
> Both RIPE and their CDN seem to use DNSSEC.
>
> Indeed, the CDN utilizes LE as the issuing CA. The LE does publish the list of issued certificates as part of Certificate Transparency, as far as I know the list is public and can be consumed by anyone.
>
> Is there some specific concern you're thinking of?
>
>
>
> Kaj
Yes, there is a simple way for circumventing the issuing procedure of
LE certificates when an actor is able to act as man-in-the-middle, see
[1] for example. Theoretical assumptions of the same kind of attack
circulated around security-related communities since beginning of LE
deployment and it's quite strange to see the org with annual budget of
tens on M$ using zero-liability CA for the primary web resource.
1.
https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Ftherecord.media%2Fjabber-ru-alleged-government-wiretap-expired-tls-certificate&data=05%7C02%7C%7Cd9f99cf886224ef283a108dc5e4db856%7Cd0b71c570f9b4acc923b81d0b26b55b3%7C0%7C0%7C638488935117222243%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C4000%7C%7C%7C&sdata=If7ZCGnKBRvSCs5t%2Faw8RuEqF53HS391HmnKe4cyMzE%3D&reserved=0