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/[email protected]/
[routing-wg] RPKI vulnerable?
- Previous message (by thread): [routing-wg] RPKI vulnerable?
- Next message (by thread): [routing-wg] misconceptions about ROV
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Nathalie Trenaman
ntrenaman at ripe.net
Fri Feb 18 14:53:12 CET 2022
Dear Hank, > On 18 Feb 2022, at 14:34, Hank Nussbacher <hank at interall.co.il> wrote: > > On 18/02/2022 10:54, 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. > > Haya posted on her Linkedin posting (3 hours ago) "RIPE NCC is on our list" in response to Ivo Dijkhuis asking "Dear Haya, we would certainly appreciate an invitation to that workshop." > > So I guess RIPE NCC needs to find out who within the NCC has been getting Haya's emails. As I stated this morning, no-one within the RIPE NCC has received Haya’s e-mails, or any e-mails from this research group regarding this research. This is why our Senior Security Officer Ivo Dijkhuis posted that message. Kind regards, Nathalie Trenaman RIPE NCC
- Previous message (by thread): [routing-wg] RPKI vulnerable?
- Next message (by thread): [routing-wg] misconceptions about ROV
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]