RE: RPSL authentication mechanisms

["Lu, Ping" <]

[snip]
> > 
> >>One easy way may be to translate/filter the query output to 
> mask the hash
> >>string with '*'
> >>based on where the query coming from. If the address is 
> authorized then pass
> >>the query output
> >>without filtering.
> >>
> > 
> > That's how I implemented it.
> 
> 
> The problem here is that you either need to map the address to a 
> particular mntner (or group of mntners), or to to allow all 
> authorised 
> users to see all the data uncensored. To say nothing about 
> maintaining 
> an acl of 7000 plus entries (# of mntners in the RIPE DB).
> 

That will be a full implementation, I am thinking more of a "admin only"
check like dbupdate be able to check the hash string from localhost.
Only some admin hosts can see all the hash strings but the regular users
won't
see any even for their own maintainer.


Ping Lu
Cable & Wireless USA
Network Tools and Analysis Group
W: +1-703-292-2359
E: plu@localhost