Skip to main content
replaced http://security.stackexchange.com/ with https://security.stackexchange.com/
Source Link

What should a website operator do about the Heartbleed OpenSSL exploit? mainly talks about what people running websites should do about Heartbleed.

What should end-users of websites be doing?

Do they need to change their passwords?

If so, should they be logging into websites and changing passwords immediately? Or should they wait until their websites have changed their sites to be more secure, and then change their passwords?

(I'm http://security.stackexchange.com/users/8335/andrew-grimmhttps://security.stackexchange.com/users/8335/andrew-grimm , but posting as a guest, because I'm not already logged in, wordpress openID isn't working, and I don't want to use a password just after Heartbleed has been announced)

What should a website operator do about the Heartbleed OpenSSL exploit? mainly talks about what people running websites should do about Heartbleed.

What should end-users of websites be doing?

Do they need to change their passwords?

If so, should they be logging into websites and changing passwords immediately? Or should they wait until their websites have changed their sites to be more secure, and then change their passwords?

(I'm http://security.stackexchange.com/users/8335/andrew-grimm , but posting as a guest, because I'm not already logged in, wordpress openID isn't working, and I don't want to use a password just after Heartbleed has been announced)

What should a website operator do about the Heartbleed OpenSSL exploit? mainly talks about what people running websites should do about Heartbleed.

What should end-users of websites be doing?

Do they need to change their passwords?

If so, should they be logging into websites and changing passwords immediately? Or should they wait until their websites have changed their sites to be more secure, and then change their passwords?

(I'm https://security.stackexchange.com/users/8335/andrew-grimm , but posting as a guest, because I'm not already logged in, wordpress openID isn't working, and I don't want to use a password just after Heartbleed has been announced)

Question Protected by Adi
Tweeted twitter.com/#!/StackSecurity/status/453398218190356480
Source Link
Andrew Grimm
  • 2.1k
  • 2
  • 20
  • 27

What should end-users do about Heartbleed?

What should a website operator do about the Heartbleed OpenSSL exploit? mainly talks about what people running websites should do about Heartbleed.

What should end-users of websites be doing?

Do they need to change their passwords?

If so, should they be logging into websites and changing passwords immediately? Or should they wait until their websites have changed their sites to be more secure, and then change their passwords?

(I'm http://security.stackexchange.com/users/8335/andrew-grimm , but posting as a guest, because I'm not already logged in, wordpress openID isn't working, and I don't want to use a password just after Heartbleed has been announced)