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] restrict usage of RIPE-NCC-RPSL-MNT
- Previous message (by thread): [db-wg] restrict usage of RIPE-NCC-RPSL-MNT
- Next message (by thread): [db-wg] restrict usage of RIPE-NCC-RPSL-MNT
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Job Snijders
job at instituut.net
Fri Nov 14 23:12:44 CET 2014
On Fri, Nov 14, 2014 at 11:00:03PM +0100, Piotr Strzyzewski wrote:
> > Would it be an idea to prevent objects from being updated/created when
> > they carry a "mnt-by: RIPE-NCC-RPSL-MNT" attribute?
>
> What about delete?
We cannot delete these objects, that would wipe out a large portion of
routing information regarding Africa. That is not acceptable. I solely
mean to reject the update/creation of an object if it contains this
line:
mnt-by: RIPE-NCC-RPSL-MNT
Because the above line is a security risk for the object, everybody
knows the password for RIPE-NCC-RPSL-MNT.
> > Secondly, should RIPE NCC proactively remove all "mnt-by:
> > RIPE-NCC-RPSL-MNT" references from the database?
>
> +1
- Previous message (by thread): [db-wg] restrict usage of RIPE-NCC-RPSL-MNT
- Next message (by thread): [db-wg] restrict usage of RIPE-NCC-RPSL-MNT
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ db-wg Archives ]