News for hackers. Stuff that matters.

A comment on Stop Using Digital Ocean Now: The Aftermath. Parent comment

Re:Stop Using Digital Ocean Now: The Aftermath by opendais on Wednesday September 25, 2013 @06:13PM (#6447665)
So you shutdown the VM due to what appears to be a compromise. That is typical host behavior at least.

Locking the user out of their account seems...odd, tho. I've never had that happen, personally, at any host.

[ Parent | on HN ]
Re:Stop Using Digital Ocean Now: The Aftermath by csomar on Wednesday September 25, 2013 @06:20PM (#6447700)
Maybe Ben can explain what "locking" an account is actually is. If the customer did, in fact, break the TOS, I think it's logical to lock his account.
[ Parent | on HN ]
Re:Stop Using Digital Ocean Now: The Aftermath by toomuchtodo on Wednesday September 25, 2013 @06:37PM (#6447774)
Locking the account should put it in a read-only mode. No changes to your DNS, no ability to start the droplet back up, firewall rules put in place at the hypervisor/network layer that block outbound traffic, but still allows you inbound access.
[ Parent | on HN ]
Re:Stop Using Digital Ocean Now: The Aftermath by opendais on Wednesday September 25, 2013 @07:59PM (#6448105)
That would be ideal. Its sounds like it was more than preventing changes to the account information tho.
[ Parent | on HN ]