Filipe, On 10/04/2024 15.08, Felipe Victolla Silveira wrote:
Over the past few months, the RIPE NCC has been working on enhancing the security of RIPE NCC Access. In a new article on RIPE Labs, I explain the recent enhancements we've implemented and provide an overview of forthcoming developments you can anticipate from us:
https://labs.ripe.net/author/felipe_victolla_silveira/enhancing-the-security...
Thanks for this! I appreciate this sort of "under the hood" look at RIPE NCC infrastructure. I was very happy that the RIPE NCC decided to use an open source implementation rather than a proprietary service for IAM! I was less thrilled that it is deployed on AWS. This means that everything that the RIPE NCC oversees that requires authentication - including things like voting for certain RIPE roles such as the RIPE PC I think - depends on Amazon. That feels wrong for a lot of reasons, but here we are. Cheers, -- Shane