fake records in RIPE DB

Thanks for the warning. We will strengthen our use of 
hierarchical authorization and go after these cases straight
away. 

-- Carol
 
In message <199704070917.mn06753 at zeronull.aszi.sztaki.hu>, 
Gabor Kiss writes:

>> Dear Hostmaster,
>> 
>> FYI.
>> Last week the following fake records was created in the name of you:
>> 
>> inetnum:     194.117.120.201 - 194.117.120.201
>> netname:     SAP-HUNGAROPHARMA
>> descr:       Hungaropharma RT
>> country:     HU
>> admin-c:     VG48-RIPE
>> tech-c:      VG48-RIPE
>> status:      ASSIGNED PA
>> changed:     hostmaster at ripe.net 960702
>> source:      RIPE
>> 
>> inetnum:     194.117.120.204 - 194.117.120.204
>> netname:     SAP-FOEVAROSI
>> descr:       Foevarosi Vizmuevek Rt.
>> country:     HU
>> admin-c:     SB568-RIPE
>> tech-c:      SB568-RIPE
>> status:      ASSIGNED PA
>> changed:     hostmaster at ripe.net 960702
>> source:      RIPE
>> 
>> inetnum:     194.117.120.216 - 194.117.120.216
>> netname:     SAP-MMG
>> descr:       MMG Automatikai Muevek Rt.
>> country:     HU
>> admin-c:     TJ308-RIPE
>> tech-c:      TJ308-RIPE
>> status:      ASSIGNED PA
>> changed:     hostmaster at ripe.net 960702
>> source:      RIPE
>> 
>> inetnum:     194.117.120.231 - 194.117.120.231
>> netname:     SAP-MVM
>> descr:       MVM RT.
>> country:     HU
>> admin-c:     AK625-RIPE
>> tech-c:      AK625-RIPE
>> status:      ASSIGNED PA
>> changed:     hostmaster at ripe.net 960702
>> source:      RIPE
>> 
>> I think some stronger authentication/authorization method is necessary
>> as well as better education of local registries. :-)
>> 
>> Regards
>> 
>> Gabor
>>