Modifying 'person:' objects

Dear Carsten,

My main concern here is security: If a person object is
unprotected, you can change all information in it,
except the name, currently. If we allow to change the name too,
then the identity of the person object can totally be changed
by anybody. This is probably not appropriate, since
there are many unprotected person objects referenced from
inetnums, aut-nums etc...


On Mon, 29 Jan 2001, Carsten Schiefner wrote:

> Colleagues,
>
[...]
>
> What from time to time really annoys me is the fact that you cannot
> change a person's name (necessary due to misspellings etc.) that is
> already referenced because the person's name together with the NIC
> handle is the primary key. You cannot delete and re-enter it either
> because it's already referenced. The only way to go is to send an email
> to the human db processor ;-) 'ripe-dbm at ripe.net' to get the data
> changed manually. I consider this as not very efficient.
>
[...]
>
> Where I haven't made up my mind yet is the question whether this always
> should apply or only in thoses cases when a person object is maintainer
> protected. There might be further cases I have not in mind at all at the
> moment - so...


I explained my concern above: even if we decide to allow the name
modifications, AFAIK we must exclude unprotected person objects. Even the
"protected" person objects whose "protecter" maintainers have "NONE" and
"MAIL-FROM" authorisation schemes, possibly.

Best regards,

Engin Gunduz
RIPE NCC Database Group


>
> Any comments will be appreciated.
>
> Best regards,
>
> 	-C.
>
>
>
>