←
Niels Hagoort7,134 posts
Niels Hagoort avatar

Niels Hagoort

@NHagoort

Enabling Infrastructure Modernization | #VCDX 212 | Published author | Public speaker | Petrol head | Loves all motorsports!

◷ Joined August 2009▧ 747 Photos and videos
Narayan Bharadwaj avatar
⟳ Niels Hagoort retweeted
Narayan Bharadwaj@narayanModernZ·7 Mar 2024

“No action for #VMWonAWS customers”. The fleet SDDCs are already patched for VMSA-2024-0006 advisory. The most secure VMware platform in the world blogs.vmware.com/cloud/2024/…

Anthony Spiteri avatar
⟳ Niels Hagoort retweeted
Anthony Spiteri@anthonyspiteri·1 Mar 2024

This is both amazing and scary and just representative of where technology has come in the last 30 years... Could be the craziest thing i've seen all year!!

HaxRob@haxrob28 Feb 2024

Doom is running on the actual toothbrush's CPU. 🪥 @romero

Bob Plankers avatar
⟳ Niels Hagoort retweeted
Bob Plankers@plankers·17 Jan 2024

In case you were ever wondering about recoverability of encrypted @VMwarevSphere VMs if the KMS is missing, well, I just did that to myself. And not intentionally, either. Good old fashioned lack of discipline when it came to default key providers. I have a few VMs that I care about that have vTPMs, which means they're using VM Encryption. I had a few extra key providers I was testing with, which I cleaned up yesterday. Turns out some of those VMs were using those key providers and were now "invalid" after a cluster restart for patching. Here's how I fixed it: 1. Look in the .vmx file for the VM, under encryption.keySafe. It'll have a reference to the key provider name. Mine started with "vmware:key/list/(pair/(fqid/<VMWARE-NULL>/TEST1/" so I know the key provider I need to restore is TEST1. 2. Look through all my backup Native Key Provider keys to find test1.p12. Didn't have one, so it was probably my external KMS. Which, as I think about it, makes sense. I didn't notice the problem yesterday because the hosts have the keys from a standard key provider cached in memory. However, I also patched and rebooted all the hosts, so when they came up they could not retrieve the key again, hence the "invalid VM" designation. ESXi caches the keys like that because vCenter is a dependency for access to the KMS, and if an HA event occurs it's possible that vCenter is down. If the keys are cached in memory in every host in the cluster then those hosts can restart all affected VMs. No problem. However, it does mask a screwup like mine. Could have been weeks or months before I figured out what I'd done, so people have to use discipline and keep backups when they're deleting stuff. 3. Anyhow, I'd deleted that KMS VM in my cleanup spree. Dammit. Restore from backup. 4. Re-add the KMS as a standard key provider. Had to recreate the auth certs on the KMS but no biggie. Biggest problem is that Chrome is now opinionated about TLS certs on the KMS. Used Firefox, which was cool with it if I was. 5. Click "Unlock" on the VM... done. Powered on. But wait, there's more! 6. I made my desired Native Key Provider the default key provider again. 7. I rekeyed the VM (right click, VM Policies, Re-encrypt) to the default key provider. I did this while the VM was running, no problem (it just re-encrypts the data encryption key). 8. Deleted the key provider and KMS... again. Things I didn't plan on doing this morning, but it'd been a while since I did anything like this, and it's good to know that the recovery I tell people is possible works. As long as you have the backups!

Post attachmentPost attachment
Narayan Bharadwaj avatar
⟳ Niels Hagoort retweeted
Narayan Bharadwaj@narayanModernZ·28 Nov 2023

Announcing ground breaking new #VMWonAWS innovation with disaggregated architecture and support for AI/ML workloads, via the M7.metal-24XL elastic bare metal instance. linkedin.com/posts/bharadwaj…

MotoGP™🏁 avatar
⟳ Niels Hagoort retweeted
MotoGP™🏁@MotoGP·27 Nov 2023

Music to our ears! 🎶 This is how the different bikes of the #MotoGP grid sound like! 👂 Turn the volume UP and enjoy our favourite soundtrack in the world! 🏍️ #MotoGP

0:33