On 11 August 2016 at 01:39, Fernando Perez <[email protected]> wrote:
> a) basic good practices with repo security by asking for 2FA for all > committers, and But I think there's an important point here that Github 2FA, while it's definitely a good security switch to flip, is not the only thing we need. We should think about all the pieces that might be vulnerable: - Someone may try to gain access to our emails to reset passwords on other sites. This is what happened to Kenneth. Since most sites offer a password reset by email, their security can only be as strong as the security around our emails. - Someone may try to steal SSH keys, which let you push to Github bypassing 2FA. We should remove SSH keys we're no longer using from our Github accounts, and if there's any reason to think private keys may have been compromised, we should regenerate them. - Someone may try to steal PyPI credentials and upload malicious packages. PyPI does not offer 2FA (yet). If you upload packages from a machine which other people can access, check that your ~/.pypirc file is not world-readable. Try to log in to PyPI periodically so that you will notice if your password has been changed. This is still separate from (b) - this is not about designing new security measures, it's about taking care that the existing ones are not undermined by our mistakes. Thomas -- You received this message because you are subscribed to the Google Groups "Project Jupyter" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jupyter/CAOvn4qhon81M04_mF76PrH6tar99iOMouOzffa4izexYbK%2B2KQ%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
