New on LowEndTalk? Please Register and read our Community Rules.
All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
Comments
Well yes, but using multiple FDE utilities won't make that any harder. In fact, utilities that scan memory for AES keys don't actually look for the DEK, they look for the round keys which always have a certain relation to each other. So no matter what vendor you use, they'll get the keys easily. Trying to hide them would be security by obscurity.
I mean qemu-ga installs by default, including on Debian netboot, when virtualization is detected.
[D1: encrypted for vendor 1 [D2: encrypted for vendor 2] - nbd-server for D2] -> [nbd-client to mount D2 on vendor 2, optionally with dm-cache for performance]
On vendor 1, D2 is encrypted, no D2 key in memory. On vendor 2, no D1 key in memory. These vendors need to collude to decrypt disk images saved on vendor 1 offline, which is enough thwart curious admins of either vendor.
This is a debian quirk. Ubuntu server minimal doesn't do that.
Oh, by vendor you mean different hosts? I thought you meant different encryption software. What's to stop someone who hijacks the VPS from accessing data on the other VPS? Without a proper TEE, the host can do whatever you can.
Different hosts is not enough, they need to belong to different vendors for admin isolation. A persistent vendor 2 admin cannot get into a properly locked down live instance "easily" vs simply dump the memory and decrypt offline if you don't use this method. Of course, we all know properly implemented FDE (with attested key release) in TEE is a lot more secure. The nested encryption strategy works for 2+ TEE vendors for even better security.
This is amazing. Perfect thing that I've been looking for.
However, i'm stuck between if I should allow provider to change password or if I shouldn't. What if I forget password? Or lock myself out cuz fail2ban?
Don't use passwords and how badly do you need to fumble that you manage to block all ips with fail2ban? I mean, I get it, I do ban myself occasionally for tests too but either that's gonna expire or I just use mobile or one of my vpns/isps
we can probably find you an online basic system administration course if it comes to that.
If you are hosting something sensitive then you dont host it on a VM. Its as simple as that in my eyes
thanks, applied this to some of my vps
Where do you host it then?