3 ms·
OK, point taken. But you're assuming that Slicehost ignored the issue, rather than being bound by their own process. I simply expected more from you: as dfran
by justinsb 17y ago
OK, point taken. But you're assuming that Slicehost ignored the issue, rather than being bound by their own process.
I simply expected more from you: as dfranke said, this is your opportunity to hammer home the importance of good security practice, and instead you're talking about something basically beyond our control (Slicehost's incident response policy) rather than the root cause (a large number of fairly basic security mistakes)
- tptacek 17y agoThe fact that you are startled that I'd even be talking about Slicehost's response tells me that not enough attention is being paid to this.
- justinsb 17y agoOK - so there's another lesson I have to learn from you :-) Please, publish a blog post series on each of the mistakes made, explaining each one and how not to fall into the trap. Explain why slicehost taking 48 hours to notify a customer before shutting down their machine is a big problem if it belongs in the list. I'll upvote every post once it hits HN.