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] mntner with misleading primary key
- Previous message (by thread): [db-wg] mntner with misleading primary key
- Next message (by thread): [db-wg] mntner with misleading primary key
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Tom Hill
tom at ninjabadger.net
Wed Jul 1 20:34:46 CEST 2020
On 01/07/2020 18:43, Matthias Merkel via db-wg wrote: > I have looked through the database files and there seem to be exactly 26 > maintainer objects that are named as an ASN (without any prefixes or > suffixes). I think the best solution would be to just block the creation > of new objects like this and manually check through the existing ones to > find potentially fraudulent ones. If it were possible, that would solve the risk associated. I'm not sure, however, if that sort of creation filter is appropriate? Is there precedent for this? -- Tom
- Previous message (by thread): [db-wg] mntner with misleading primary key
- Next message (by thread): [db-wg] mntner with misleading primary key
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ db-wg Archives ]