From 83028b5ef1526e1bc249b8efff7c1a7b3afeebfa Mon Sep 17 00:00:00 2001 From: Dumitru Uzun Date: Thu, 29 Jun 2017 03:06:21 +0300 Subject: [PATCH] Update Gathering-weak-npm-credentials.md Use a password manager - that is a very important advice! Google gives the same advice to users. A good password manager would generate strong and unique passwords and would notify the user about weak passwords - this alone solves most of the issues described in this document. --- Gathering-weak-npm-credentials.md | 1 + 1 file changed, 1 insertion(+) diff --git a/Gathering-weak-npm-credentials.md b/Gathering-weak-npm-credentials.md index dac66ee..02ea0cc 100644 --- a/Gathering-weak-npm-credentials.md +++ b/Gathering-weak-npm-credentials.md @@ -270,6 +270,7 @@ As 2FA on the client seems to be complex and will likely take long time to imple * Don't reuse the same password on other sites. * Make sure that you are not using password-based auth in `.npmrc` — `_authToken` is good, `_auth` and `_password` are bad. * Check **all** your logins and emails on [haveibeenpwned.com](https://haveibeenpwned.com). Make sure that you don't forget about historic emails. + * Use a good password manager - this would improve your overall security online * Check if you have publish access to any popular packages on npm. _Note: some users that I talked to were not aware that they are added to some popular packages._ * If you have popular packages published on npm: * Make sure that the list of people who have the permissions to publish it is not unnecessary huge and does not include unrelated people who are not active, not going to publish that package, or otherwise don't need those permissions.