Guarded Objects are now better protected

Dear colleagues,

A recent accident has caused us to protect the guarded objects in
the database a little better before the maintainer attribute 
is fully implemented.

Guarded objects can from now on only be updated thru the manual 
procedure which involves plausibility checking by NCC staff.
The manual procedure uses the old mailbox ripe-dbm at ripe.net.

Any updates for guarded objects sent to the auto-dbm at ripe.net
mailbox will be refused with the error message:

*ERROR*:   guarded objects cannot be updated via automatic procedure

If you get such an error, re-send the update to ripe-dbm.


Once the maintainer attribute is implemented authorisation 
will be handled automatically.

Daniel


PS: We hope to have the update procedure for guarded *attributes* 
deployed next week.