[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 ]
Job Snijders
job at instituut.net
Wed Jul 1 20:41:24 CEST 2020
On Wed, Jul 1, 2020, at 20:34, Tom Hill via db-wg wrote: > 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. 26 is at the number where we can pick up the phone and ask politely > 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? Yes, creation filters have precedent. Would be a good tool here IMHO. Kind regards, Job
- 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 ]