Dear Working Group, RIPE Database release 1.101 has been deployed to the Release Candidate environment. We plan to deploy to production on Thursday 1st July. This release includes the following main changes: * Switch RIPE database to UTC timezone (all timestamps will be in UTC and all timestamps specify the 'Z' timezone) * Display an error on NRTM if client is blocked by ACL limit (#812) * Added rewrite rules to embedded Jetty (#801) * RDAP nameserver queries always return Not Implemented (#811) * Updated dependencies *Additionally* some operational changes will also be made to the production environment on 1st July: * Remove support for TLS versions 1.0 and 1.1 on HTTPS connections * The IETF has formally deprecated these TLS versions, now only versions 1.2 and 1.3 are recommended. * Remove insecure TLS cipher algorithms * TLS_DHE_RSA_WITH_CAMELLIA_128_CBC_SHA * TLS_DHE_RSA_WITH_CAMELLIA_256_CBC_SHA * TLS_DHE_RSA_WITH_SEED_CBC_SHA * TLS_ECDHE_RSA_WITH_3DES_EDE_CBC_SHA * TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA * Remove HTTP redirects for whois.ripe.net and www.db.ripe.net * HTTP requests to these hosts will no longer redirect to https://apps.db.ripe.net but will return 400 Bad Request. * Remove HTTP redirects for the legacy Whois REST API * The legacy Whois REST API was retired in 2015, a temporary redirect to https://rest.db.ripe.net will be removed. * HTTP requests to the legacy API at http://apps.db.ripe.net/whois/lookup/ripe will return 400 Bad Request. Please check your Whois client in case you are affected by these changes. The release notes are on the website: https://www.ripe.net/manage-ips-and-asns/db/release-notes/ripe-database-rele... 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-candida... Please let us know if you find any issues with this release in the RC environment. Regards Ed Shryane RIPE NCC
Dear Working Group, We have now deployed Whois 1.101 to production. Regards Ed Shryane RIPE NCC
On 17 Jun 2021, at 15:42, Edward Shryane via db-wg <db-wg@ripe.net> wrote:
Dear Working Group,
RIPE Database release 1.101 has been deployed to the Release Candidate environment. We plan to deploy to production on Thursday 1st July.
This release includes the following main changes:
* Switch RIPE database to UTC timezone (all timestamps will be in UTC and all timestamps specify the 'Z' timezone) * Display an error on NRTM if client is blocked by ACL limit (#812) * Added rewrite rules to embedded Jetty (#801) * RDAP nameserver queries always return Not Implemented (#811) * Updated dependencies
*Additionally* some operational changes will also be made to the production environment on 1st July:
* Remove support for TLS versions 1.0 and 1.1 on HTTPS connections * The IETF has formally deprecated these TLS versions, now only versions 1.2 and 1.3 are recommended. * Remove insecure TLS cipher algorithms * TLS_DHE_RSA_WITH_CAMELLIA_128_CBC_SHA * TLS_DHE_RSA_WITH_CAMELLIA_256_CBC_SHA * TLS_DHE_RSA_WITH_SEED_CBC_SHA * TLS_ECDHE_RSA_WITH_3DES_EDE_CBC_SHA * TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA * Remove HTTP redirects for whois.ripe.net and www.db.ripe.net * HTTP requests to these hosts will no longer redirect to https://apps.db.ripe.net but will return 400 Bad Request. * Remove HTTP redirects for the legacy Whois REST API * The legacy Whois REST API was retired in 2015, a temporary redirect to https://rest.db.ripe.net will be removed. * HTTP requests to the legacy API at http://apps.db.ripe.net/whois/lookup/ripe will return 400 Bad Request.
Please check your Whois client in case you are affected by these changes.
The release notes are on the website: https://www.ripe.net/manage-ips-and-asns/db/release-notes/ripe-database-rele...
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-candida...
Please let us know if you find any issues with this release in the RC environment.
Regards Ed Shryane RIPE NCC
participants (1)
-
Edward Shryane