Dear colleagues,

The RIPE NCC is pleased to announce the deployment of RIPE Database software release 1.76 to the Release Candidate (RC) environment.

Detailed information about features, changes and how this release might affect your operations, are available in the release notes:

This release includes many small bug fixes and feature improvements. Notably, we have addressed the following issues:

- Issue #221: It is now possible to change the name of a PERSON or ROLE object

- Issue #256: Abuse contact information is now shown when using web lookups 

- Issue #220: Failed update notifications now include a diff of the attempted change

A number of users requested the notification of a failed update to include a diff showing what was attempted to be changed. A consequence of this change is that, if you mistype the password pseudo-attribute (eg "pasword: clear_password"), the notification will include your clear text password.

This is a good time for all maintainers of data in the RIPE Database to review to whom these notifications are sent. The "upd-to:" attribute in a MNTNER object should only include the email address of a person or team in your organisation who deals with security issues. If this team receives such a notification, they should advise the user to change their password.

We invite all users of the RIPE Database to review the new release in the RC environment:

We look forward to any questions or comments you might have.

Kind regards,

Tim Bruijnzeels