[db-wg] Locking unmaintained PERSON and ROLE objects in the RIPE Database

On Tue, Apr 12, 2016 at 12:52:30AM +0200, denis wrote:

Denis

> So how do they claim to be the owner? They change the details in the PERSON 
> object, including the PERSON name, and maybe add their own MNTNER to it. 
> But the key element here is the name. In the past you could not change the 
> PERSON object name. This is a change that was implemented a couple of years 
> ago and has led to this current issue. ONLY by changing the name of the 
> PERSON object can you claim to be the 'owner' of this address space. If you 
> can't change the name and you can't produce any ID to show you are the 
> named person, then you have no claim over the address space. Hijacking in 
> this way is not possible. So if you had rolled back that change to allow 
> changes to the PERSON object name you would have fixed this problem.

Leaving aside rest of your email, this is plain wishful thinking.

It is not a problem to find and pay/bribe someone with the same name to
be a mere front man. Or change a name at some jurisdictions. Or marry
someone and then change the name.
This has been "invented" years ago.

For those who understand a bit of polish, a cut from the well known
polish commedy from 1980 with the same idea:
https://youtu.be/ApLfbr89ssk?t=1m18s

Piotr

-- 
gucio -> Piotr Strzyżewski
E-mail: Piotr.Strzyzewski at polsl.pl