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]/
[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 22:35:18 CEST 2020
On 01/07/2020 19:56, Matthias Merkel via db-wg wrote: > Given the small number of objects, I don't think implementing a filter > would have any significant impact (negative or positive) and may not be > worth the effort. Perhaps as a result of my conceiving of it, there is a conceivable social engineering angle here, which could be put to use to create problems in the GRT. I would expect the minimum effort to protect against this - preventing any *new* mntners masquerading as aut-nums - as being a worthwhile investment of effort. As per Job's comment at ~18:41Z, this could be handled with a creation filter, of which there is precedent. It would certainly be worth putting a stop to the capability /before/ someone finds a way to exploit it, and we're all left looking at our feet. :) -- 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 ]