Live data from Hacker News

Mint won't give a clear answer about Heartbleed

satisfaction.mint.com

31–33 of 33 posts

Re: Mint won't give a clear answer about Heartbleed

#31
post #5
post #3

What is unclear about the response: "As indicated, our engineers have verified Mint is not affected by "Heartbleed." Password resets and re-issuing of SSL certificates are not required at this time." It seems that they are saying either (a) they are not using OpenSSL, or (b) they were using a version of OpenSSL without the vulnerability. Is there anything wrong with assuming that given their statements?

"is not affected" being the operative wording. users want to know if their data has ever been at risk. still, surely everyone can just assume it was affected, act accordingly, and move on?

Except "is not affected" is exactly what you'd say if you were running software that wasn't, and still isn't vulnerable (because you didn't have to patch anything).

Re: Mint won't give a clear answer about Heartbleed

#32
The latest (and final) response Mint gave, 2 hours after this hit the HN front page, is: "I'm terribly sorry for the delay in circling back to this topic. I can confirm that Mint was using a version of OpenSSL that was never vulnerable to Heartbleed."

Seems cleared up. Goes to show yet again, due to the massive traffic it causes, HN continues to be useful as a customer complaint center for egregious cases...

Re: Mint won't give a clear answer about Heartbleed

#33
post #32

The latest (and final) response Mint gave, 2 hours after this hit the HN front page, is: "I'm terribly sorry for the delay in circling back to this topic. I can confirm that Mint was using a version of OpenSSL that was never vulnerable to Heartbleed." Seems cleared up. Goes to show yet again, due to the massive traffic it causes, HN continues to be useful as a customer complaint center for egregious cases...

Which is the same as their first official response to the thread further up the page too!
Post reply on HN