If that's how they implement it, then I look forward to reading their future security advisory.
Is it just me, or is this contradictory? "Data wasn't leaked.. but if it was it was because you didn't check scrub, so it must not have been important." These are two completely different things. Even if the data was not sensitive, it could still be leaked between accounts (which is what happened here).
Kudos for committing to fixing the problem though.
If not though, then you're absolutely right that those are contradictory. If, even during disclosure, one user's data was made available to another user, that constitutes a data leak.
https://f.cloud.github.com/assets/408977/1820859/8658298e-71...
These are some of the strings I pulled off the root blockdev
- I have no such /var/deploy/chegou, or any of these files. I was
able to recover someone else's webserver logs from yesterday, as well.What is a "clean system", if not a scrubbed one? And if they're scrubbing during create, why leave the scrub option in during destroy? I have to assume that when they say "clean system" they don't mean a scrubbed one, and that worries me.
If, as they said, their reason for not scrubbing is because of customers creating and destroying a lot of volumes during the onboarding process, then it seems to me the best solution is one that I believe was suggested in the previous thread. Namely, scrub a volume always whenever it's being used by a new customer. But if the volume is being reused by the same customer, don't bother scrubbing (unless requested), as presumably there are no concerns about leaking information from a user back to the same user.