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/db-wg@ripe.net/
[db-wg] So what happened last night to the DB?
- Previous message (by thread): [db-wg] So what happened last night to the DB?
- Next message (by thread): [db-wg] So what happened last night to the DB?
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Shane Kerr
shane at time-travellers.org
Fri Jun 21 09:20:57 CEST 2024
Hank, On 21/06/2024 06.36, Hank Nussbacher via db-wg wrote: >> >> We are aware of an incident affecting Whois updates yesterday evening, >> which we are continuing to investigate. We will keep the DB-WG informed. >> > There is still ongoing activity with perhaps malicious whois updates. > See attached. This is `mnt-nfy:` working as intended right? You can contact the folks at IFAT group and let them know that their resources might have been hijacked, and you can contact the RIPE DBM and have them investigate. Is there some specific action that you think that the RIPE DB working group can or should do? Cheers, -- Shane -------------- next part -------------- A non-text attachment was scrubbed... Name: OpenPGP_0x3732979CF967B306.asc Type: application/pgp-keys Size: 11519 bytes Desc: OpenPGP public key URL: </ripe/mail/archives/db-wg/attachments/20240621/6db0acf1/attachment-0001.bin> -------------- next part -------------- A non-text attachment was scrubbed... Name: OpenPGP_signature.asc Type: application/pgp-signature Size: 840 bytes Desc: OpenPGP digital signature URL: </ripe/mail/archives/db-wg/attachments/20240621/6db0acf1/attachment-0001.sig>
- Previous message (by thread): [db-wg] So what happened last night to the DB?
- Next message (by thread): [db-wg] So what happened last night to the DB?
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ db-wg Archives ]