January 2025 - db-wg - mailman.ripe.net

Using API Keys in the RIPE Database
by Edward Shryane 31 Jan '25

31 Jan '25

Dear colleagues, We have now enabled API keys for authenticating updates in the RIPE database. We have written a RIPE Labs article including a video on how to use this feature: https://labs.ripe.net/author/ed_shryane/using-api-keys-in-the-ripe-database/ Please let me know if you have any comments. Regards Ed Shryane RIPE NCC

2 2

Chicken and egg in regards to inverse
by Hank Nussbacher 30 Jan '25

30 Jan '25

We have a customer with an inverse object (in-addr.arpa) whereby the 3 nameservers listed are long extinct and need to be replaced. So the customer went to Cloudflare and paid to use their 2 nameservers (specifically harley.ns.cloudflare.com and teagan.ns.cloudflare.com) Yet, when I go to RIPE to update their inverse record I get many standard errors that the nameservers do not exist yet to serve this inverse domain. The customer tried to create the zone in cloudflare, but CF asks them to change the DNS in the RIPE object, but to change the RIPE object they need first to have an active DNS zone…. So what is one to do in such a case? Thanks, Hank

3 3

Updated Migration Plan to Remove MD5 Hashed Passwords from the RIPE Database
by Edward Shryane 30 Jan '25

30 Jan '25

Dear colleagues, You will find below an updated draft of the migration plan to remove MD5 hashed passwords from the RIPE Database in 2025. The original migration plan was announced last September to the DB-WG and at RIPE 89 in October: https://mailman.ripe.net/archives/list/db-wg@ripe.net/thread/FTOPBPOGWIQFQP… Thank you all for your valuable feedback, which we have taken into consideration, and in summary we now plan to deploy support for OAuth 2.0 in mid-2025, and we will delay the phase-out of MD5 hashed passwords completely to the end of 2025. The updated migration plan is as follows: * 30 January: Introduced support for API keys in the RIPE Database. * Q2 2025: Remove all MD5 hashed passwords that have not been used for authentication in the past year. This new step reduces the risk of having so many MD5 hashes in the database in case of a data breach, while minimising inconvenience for maintainers that are actively using passwords. This step will affect about 14,000 maintainers which have an alternative method of authentication (out of 62,000 total maintainers), and about 2,000 maintainers with no alternative method of authentication other than passwords. We will communicate this in advance to the DB-WG and to affected maintainers, and encourage them to switch to an alternative authentication method. * Q3 2025: Introduce support for OAuth 2.0 authentication, which will provide automation, including key rollover. * Q3 2025: Communicate to the DB-WG and affected maintainers that we plan to remove support for MD5 hashed passwords before the end of 2025. * Q3 2025: Select batches of maintainers to migrate away from passwords. * Warn that we will remove their MD5 hashed passwords in one month * Assist anyone who asks for help to switch to an alternative * Remove MD5 hashed passwords in batches * Q4 2025: Remove support for MD5 hashed passwords altogether. After that, any maintainers without an alternative authentication method must follow the “Forgot Maintainer Password” process, or contact the RIPE Database support directly. Please let us know if you have any comments on the details and timing. Regards Ed Shryane RIPE NCC

1 0

Whois Release 1.115
by Edward Shryane 30 Jan '25

30 Jan '25

Dear colleagues, RIPE Database release 1.115 has been deployed to the Release Candidate environment for testing. We plan to deploy to production on Thursday 30th January. The 1.115 release has the following main changes: * API key authentication for queries and updates * Use relative path in NRTMv4 update notification file * Add JWS Support To Fix Race Condition in NRTMv4 * NRTMv4 client implementation * Add MNTNER to RDAP Entities Search * Import ARIN and LACNIC IRR database dumps into mirror * Syncupdates will return an error in future if used over HTTP * Mailupdates will return an error in future if a password is used * Include password authentication type in Whois Update notifications * Extend Maximum Length of an Email Address * Allow blocking by source address on Port 43 Queries * Generate mail Message-ID including angle brackets. * Change Database Schema from Latin-1 to UTF-8 The full list of changes is available in the source repository: https://github.com/RIPE-NCC/whois/compare/15434524...930e4aba?expand=1 Please note that because API key functionality in RIPE NCC Access is not available yet, it will not be enabled in the Release Candidate environment for now. The release notes are on the website: https://docs.db.ripe.net/Release-Notes/#ripe-database-release-1-115 More information on the Release Candidate environment can be found on our website: https://apps.db.ripe.net/docs/Release-Notes/ The data in the RC environment is a dummified copy of production from 13th January. Please let us know if you find any issues with this release in the RC environment. Regards Ed Shryane RIPE NCC

1 1

Identifying IX space in the database
by Ben Cartwright-Cox 23 Jan '25

23 Jan '25

Hey everybody! I was wondering if it was possible to tell if an inetnum or inet6num was assigned for the purpose of an internet exchange. Looking at the inetnum objects for 185.1.0.0/16 (that seems to now be depleted) it does not seem there is anything different between a IX allocation and a regular allocation, in either the delegate file or the actual DB. Anyone know any better? Ben

3 2