Hacker News new | past | comments | ask | show | jobs | submit login

Well handled.



Agreed. This is in sharp contrast to the Media Temple / Plesk debacle. Which affected how many thousands of sites? How long did it take them to admit it? Meanwhile, Linode reports full details of a hack affecting no more than 8 accounts the SAME day.


It's good the fast acknowledgement, but I find it lacks in detail. I'd love to know exactly what kind of measures are they going to take so the chances of this happening again are truly reduced.

I share a Linode with a friend and at work we deal with 4 so this is a concern.


Further comment is indeed warranted, but that part can come in a few days, when there's more clarity on the scope of the incident and a fully-hashed plan of attack for closing the vulnerability.


I hope so. They said they will be "reviewing our policies and procedures to prevent this from ever recurring."

That doesn't imply they will be posting a public update. As a Linode customer, I would like to know details of how this breach occurred and what actions will be taken to prevent it in the future.




Join us for AI Startup School this June 16-17 in San Francisco!

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: