-
Notifications
You must be signed in to change notification settings - Fork 308
change all passwords post-Heartbleed #2275
Comments
Including API keys. |
Has this all been done? |
We have some passwords in LastPass and some not in LastPass. When did we sign up for LastPass? Was that before or after Heartbleed? That would at least take care of those. |
First LastPass payment was on May 1, 2014. Heartbleed was April 7. |
All passwords in LastPass were changed in October at the earliest. Is that after each vendor fixed heartbleed?
|
Gah. Worthless UX. 😞 |
Alright, so I guess the threat here is that a site we were using was compromised before they fixed Heartbleed, and our password was potentially stolen. We need to have changed the password after they fixed Heartbleed on any domains we login on. We can look at announcements from these services, but really we want to test the websites themselves that we provide our credentials to, and really not just the ones we provide credentials to, but any provided by the vendor (e.g., |
Really this should turn into an exercise in collecting all of the services we use and changing the password for all of them, a manual take on gratipay/inside.gratipay.com#159. |
Steps:
|
Change all passwords that are in LastPass:
|
For example, what about individual user accounts for services like GitHub or Sentry? Are we going to require them to change their passwords on those services? Is that even possible for us? |
Not in LastPassProduction
Financial
|
User ModelSingle User
Multiple Users (bold = we actually have multiple users)
|
I believe I changed our WordPress.com account, but now signing in to Gravatar is broken: https://twitter.com/whit537/status/581231371080900608 :-( |
I believe I was able to change the Gravatar/WordPress password after all. I was able to access Gravatar and I changed the password (again?), which happens on WordPress.com. I'm now stuck in the same login loop as before. Maybe it's a cookie expiry issue or something? |
Yeah, I can access Gravatar. |
What should we do about accounts that have multiple users? We don't have control. For example, we can't force everyone who is a collaborator or owner on GitHub to change their GitHub passwords. Should we make an effort to get everyone to do that? |
+1 We should at least try |
Reticketing from #2259.
Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.
The text was updated successfully, but these errors were encountered: