I generally just delete my personal files and shut down.
"A single swap file or partition may be up to 128 MB in size. [...] [I]f you need 256 MB of swap, you can create two 128-MB swap partitions." (M. Welsh & L. Kaufman, Running Linux, 2e, 1996, p. 49)
Since I buy KVMs, I tend to just renice a DBAN on it. Any decent provider will have a snapshot of your image for awhile, anyhow. I don't care about that, I just don't want someone who takes over my allocated space getting bored after a fastwrite and getting any of my beautiful headshots.
Are you saying someone who buys a VPS can get the data dregs from the last user, instead of getting zeroed out file space? That seems like a monstrous security hole. It should never be allowed to happen.
@willie said:
Are you saying someone who buys a VPS can get the data dregs from the last user, instead of getting zeroed out file space? That seems like a monstrous security hole. It should never be allowed to happen.
Generally, no. It would require direct disk access for the most part for this to occur, but I don't trust LE* providers to wipe drives when replacing them. It was mostly intended as a funny, but it is technically possible. You'd want/need root on the hypervisor in virtually all cases or the disk to be directly raw-device-hardware-attached to your VM, at the very least..
@willie said:
Are you saying someone who buys a VPS can get the data dregs from the last user, instead of getting zeroed out file space? That seems like a monstrous security hole. It should never be allowed to happen.
Now you know why everyone posts 'iso boot supported?' on every kvm thread.
LUKS aes128xts has practically no overhead on intel Cpus after 2011
Comments
Generally, yes, or something similar. If it's an encrypted LVM, then more fun can be had.
It wisnae me! A big boy done it and ran away.
NVMe2G for life! until death (the end is nigh)
And you rely on the integrity of the service provider by trusting him/her to wipe off VM backups too :P
Edit: If they keep backups, that is.
best way is to delete your data and use sfill (from secure-delete) to fill the drive with garbage, if you have sensitive data
theres also sswap but i guess, sfill is enough if you're not into some secret government service
you can also boot from a live cd, and do
dd if=/dev/zero of=/dev/vdX
but it will take a long time
Just shutdown. (LUKS volumes mean quick and simple retirement)
I generally just delete my personal files and shut down.
"A single swap file or partition may be up to 128 MB in size. [...] [I]f you need 256 MB of swap, you can create two 128-MB swap partitions." (M. Welsh & L. Kaufman, Running Linux, 2e, 1996, p. 49)
Send it back in factory format. OS reinstall
Nexus Bytes Ryzen Powered NVMe VPS | NYC|Miami|LA|London|Netherlands| Singapore|Tokyo
Storage VPS | LiteSpeed Powered Web Hosting + SSH access | Switcher Special |
That's what I've done in the past, I just wondered how paranoid people got.
Yes, sfill for me is sufficiently secure (and for most people)
Deals and Reviews: LowEndBoxes Review | Avoid dodgy providers with The LEBRE Whitelist | Free hosting (with conditions): Evolution-Host, NanoKVM, FreeMach, ServedEZ | Get expert copyediting and copywriting help at The Write Flow
Since I buy KVMs, I tend to just renice a DBAN on it. Any decent provider will have a snapshot of your image for awhile, anyhow. I don't care about that, I just don't want someone who takes over my allocated space getting bored after a fastwrite and getting any of my beautiful headshots.
My pronouns are like/subscribe.
Are you saying someone who buys a VPS can get the data dregs from the last user, instead of getting zeroed out file space? That seems like a monstrous security hole. It should never be allowed to happen.
Generally, no. It would require direct disk access for the most part for this to occur, but I don't trust LE* providers to wipe drives when replacing them. It was mostly intended as a funny, but it is technically possible. You'd want/need root on the hypervisor in virtually all cases or the disk to be directly raw-device-hardware-attached to your VM, at the very least..
My pronouns are like/subscribe.
Now you know why everyone posts 'iso boot supported?' on every kvm thread.
LUKS aes128xts has practically no overhead on intel Cpus after 2011
Be safe my friends.