I've seen the TRIM recommendation pop up a few times, and never with a reply from DO - is this probably how they're going to handle this, or is there a possible reason for not using TRIM?
TRIM is equivalent to 'mark as free'. there's no guarantee it will zero the data, and whether it is zero'd depends on the manufacturer/model of the drive.
If that's how they implement it, then I look forward to reading their future security advisory.
Ah yes, I'm not super familiar with the terminology, a sibling comment to yours specifies that you'd need to use zdat (zero after TRIM) for what I'm talking about to be effective.
its more about zero after trim support (dzat), and sounds like they maybe use ssd's that don't support it, and are handling it by zeroing the block device on create instead of wipe. At least that's how I read it. I suppose easy enough to check by seeing if new droplets take longer to create after this is deployed.
Comments
I've seen the TRIM recommendation pop up a few times, and never with a reply from DO - is this probably how they're going to handle this, or is there a possible reason for not using TRIM?
TRIM is equivalent to 'mark as free'. there's no guarantee it will zero the data, and whether it is zero'd depends on the manufacturer/model of the drive.
If that's how they implement it, then I look forward to reading their future security advisory.
Ah yes, I'm not super familiar with the terminology, a sibling comment to yours specifies that you'd need to use zdat (zero after TRIM) for what I'm talking about to be effective.
its more about zero after trim support (dzat), and sounds like they maybe use ssd's that don't support it, and are handling it by zeroing the block device on create instead of wipe. At least that's how I read it. I suppose easy enough to check by seeing if new droplets take longer to create after this is deployed.