Re: NumPy security roadmap proposal
Ralf Gommers via NumPy-Discussion <[email protected]>
| Newsgroups | gmane.comp.python.numeric.general |
|---|---|
| Message-ID | <CABL7CQiu9UffYut32LVnmpP-Jf6sSiv7AptBR++NHNnZgg-4zA@mail.gmail.com> |
On Fri, Jun 13, 2025 at 11:13 AM Andrew Nelson via NumPy-Discussion < [email protected]> wrote: > > On Fri, 13 Jun 2025 at 16:43, Ralf Gommers via NumPy-Discussion < > [email protected]> wrote: > >> >> For 2FA and repository/PyPI access, we'll start making changes soon. Note >> that GitHub has recently made changes to its 2FA settings that ask for >> action from many people: on https://github.com/orgs/numpy/people you can >> see that under "Two-factor authentication" the options increased; there is >> now a Secure/Insecure distinction instead of only Enabled/Disabled. If you >> want to move yourself from Insecure to Secure, you have to disable the >> SMS/mobile recovery option in your personal settings under "Password and >> authentication". A large majority of the 94 people with permissions are >> currently marked as Insecure. >> > > Having just visited this page I can't see any Two-factor authentication, > or secure/insecure properties listed. > It may only be visible to org owners then. > Remember that 2FA isn't just SMS, it could be an Authenticator app, > Physical key (yubikey), etc. > Yes indeed. The other methods are considered secure by GitHub, just SMS/mobile is not. Cheers, Ralf _______________________________________________ NumPy-Discussion mailing list -- [email protected] To unsubscribe send an email to [email protected] https://mail.python.org/mailman3//lists/numpy-discussion.python.org Member address: [email protected]