<html><head><meta http-equiv="Content-Type" content="text/html charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">Dear colleagues,<div class=""><br class=""></div><div class="">RIPE Database software release 1.76 was deployed to the production server on Wednesday, 12 October 2014.</div><div class=""><br class=""></div><div class="">Regards</div><div class=""><br class=""></div><div class="">Ed Shryane</div><div class="">RIPE NCC</div><div class=""><br class=""><div><blockquote type="cite" class=""><div class="">On 14 Oct 2014, at 18:14, Tim Bruijnzeels <<a href="mailto:tim@ripe.net" class="">tim@ripe.net</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><meta http-equiv="Content-Type" content="text/html charset=us-ascii" class=""><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><div class=""><div class="">Dear colleagues,</div><div class=""><br class=""></div><div class="">The RIPE NCC is pleased to announce the deployment of RIPE Database software release 1.76 to the Release Candidate (RC) environment.</div><div class=""><br class=""></div><div class="">Detailed information about features, changes and how this release might affect your operations, are available in the release notes:</div><a href="https://www.ripe.net/data-tools/db/release-notes/ripe-database-release-1.76" class="">https://www.ripe.net/data-tools/db/release-notes/ripe-database-release-1.76</a><br class=""><div class=""><br class=""></div><div class="">This release includes many small bug fixes and feature improvements. Notably, we have addressed the following issues:</div><div class="">- Issue #221: It is now possible to change the name of a PERSON or ROLE object</div><div class="">- Issue #256: Abuse contact information is now shown when using web lookups </div><div class="">- Issue #220: Failed update notifications now include a diff of the attempted change<br class=""><br class="">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.</div><div class=""><br class="">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.</div><div class=""><br class=""></div><div class="">We invite all users of the RIPE Database to review the new release in the RC environment:</div><div class=""><a href="https://www.ripe.net/data-tools/db/release-notes/rc-release-candidate-environment" class="">https://www.ripe.net/data-tools/db/release-notes/rc-release-candidate-environment</a></div><div class=""><br class=""></div><div class="">We look forward to any questions or comments you might have.</div><div class=""><br class=""></div><div class="">Kind regards,</div><div class=""><br class=""></div><div class="">Tim Bruijnzeels</div></div><div class=""><br class=""></div><div class="">Assistant Manager Software Engineering</div><div class="">RIPE NCC</div></div></div></blockquote></div><br class=""></div></body></html>