This archive is retained to ensure existing URLs remain functional. It will not contain any emails sent to this mailing list after July 1, 2024. For all messages, including those sent before and after this date, please visit the new location of the archive at https://mailman.ripe.net/archives/list/routing-wg@ripe.net/
[routing-wg] RPKI vulnerable?
- Previous message (by thread): [routing-wg] RPKI vulnerable?
- Next message (by thread): [routing-wg] RPKI vulnerable?
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Maria Matejka
maria.matejka at nic.cz
Fri Feb 18 11:13:52 CET 2022
Hello! On 2/18/22 9:54 AM, Nathalie Trenaman wrote: > Hi Nick, > >> On 18 Feb 2022, at 09:53, Nick Hilliard <nick at foobar.org> wrote: >> >> Hank Nussbacher wrote on 18/02/2022 07:39: >>> We are working with large network providers and registrars on mitigating the vulnerabilities in RPKI deployments. >> >> Has anyone from the RIPE NCC been in contact with this group? >> >> Nick > > No, we haven’t. This also sparked our curiosity, so we’re trying to contact them. I also haven't known before so I'm trying to contact them as well. There is no info what part of RPKI infrastructure is affected and whether BIRD may be also vulnerable. Maria
- Previous message (by thread): [routing-wg] RPKI vulnerable?
- Next message (by thread): [routing-wg] RPKI vulnerable?
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]