Dear Working Group, the RIPE Database release 1.93 was delayed due to the Full Text Search downtime earlier this week.
We have now deployed an updated 1.93.2 release to the RC environment. The complete list of changes in this release can be found in GitHub: https://github.com/RIPE-NCC/whois/blob/master/changes.txt We now plan to deploy this release to production next Monday, 4th March. Regards Ed Shryane RIPE NCC > On 11 Feb 2019, at 15:34, Edward Shryane via db-wg <[email protected]> wrote: > > Dear Working Group, > > RIPE Database release 1.93 has been deployed to the Release Candidate > environment. If no issues are found, we plan to deploy to production on > Monday, 25th February. > > Release 1.93 includes the following main changes: > > * Improved email address validation. > * Do not allow expired public keys to authenticate updates, and expire signed > messages after 1 hour. > * Validate bogon space in route(6) creation. > * Warn the user if the resource abuse-c is identical to the organisation's > abuse-c. > * Allow use of elliptic curve algorithm in key-cert objects (updated > cryptography library). > * Fixed NRTM client parsing end of stream comment in keepalive mode. > * Filter out comment in autocomplete API (used by the DB web application) > * Only validate reserved words in primary key on create, so existing objects > can be updated. > * Database schema changes for 2017-02 Abuse-c Validation implementation. > > The complete list of changes in this release can be found in GitHub: > https://github.com/RIPE-NCC/whois/blob/master/changes.txt > > The release notes will also be published shortly: > https://www.ripe.net/manage-ips-and-asns/db/release-notes > > More information on the Release Candidate environment can be found on our > website: > https://www.ripe.net/manage-ips-and-asns/db/release-notes/rc-release-candidate-environment > > Please let us know if you find any issues with this release in the RC > environment. > > Regards > Ed Shryane > RIPE NCC > > >
