This archive is retained to ensure existing URLs remain functional. It will not contain any emails sent to this mailing list after July 1, 2024. For all messages, including those sent before and after this date, please visit the new location of the archive at https://mailman.ripe.net/archives/list/[email protected]/
[ncc-services-wg] RIPE NCC Security Update
- Previous message (by thread): [ncc-services-wg] RIPE NCC Security Update
- Next message (by thread): [ncc-services-wg] RIPE NCC Security Update
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Aleksi Suhonen
ripe-ml-2024 at ssd.axu.tm
Wed Mar 20 18:09:23 CET 2024
Hi colleagues, On 3/19/24 9:59 AM, Eleonora Petridou wrote: > We have also strengthened password requirements and added a reminder > to enable 2FA when users log in to their RIPE NCC Access accounts. > This is an interim measure until mandatory 2FA is rolled out. Our > roadmaps have been updated to expedite the rollout of mandatory > two-factor authentication: The current policy does not allow for having the same OTP code on two different mobile phones at the same time, so the only way to migrate to a new phone is to turn off 2FA completely and then turn it back on again to get a QR code for the new phone. When 2FA becomes mandatory, it cannot be turned off, am I right? What is the plan to enable the moving to a new phone or other authenticator device? Best Regards, -- Aleksi Suhonen / Axu TM Oy Internetworking Consulting
- Previous message (by thread): [ncc-services-wg] RIPE NCC Security Update
- Next message (by thread): [ncc-services-wg] RIPE NCC Security Update
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]