Not really, but once you've patched the driver, run dkms status and dkms build <id from status> (e.g. dkms build nvidia/580.76.05) to rebuild the driver for your current kernel.
When you get it working, it'll be a good idea to write a little guide here for other people to follow.
What's the URL you using to access it without Cloudflare?
Edit: Also that curl tells me it's not listening on that IP/port.
I never mentioned vulnerabilities, I just wanted to point out that, RDP doesn't really work without a graphical session, Windows Server Core gets around this by being a graphical session (although very basic).
Also I'm not sure, but I don't think Windows handles RDP on the kernel level, it's just nicely tied in with DWM and doesn't have to deal with the multitude of window managers on Linux.
Handling RDP on the kernel level does sound like a bad idea security wise, but there should be a better way.
I'm pretty sure schools must already have lockdown alarms in Australia (and drills every few years), so it's surprising that this isn't already a thing in America, especially with its issues.
Just to freak you out, I've played around with the EC on my Framework, and it really wouldn't be hard for someone to create a modified firmware with a key logger built in or something. But AFAIK the EC doesn't have internet access or a way to screw with the OS, so it would be mildly pointless without accompanying software.
Modifying the BIOS seems slightly more difficult, although I think some Frameworks are still vulnerable to LogoFAIL.
I wouldn't worry about extra chips, they'd either be quite noticeable that they shouldn't be there, or too expensive to be wasted on a stranger.
So the chances are, unless you've got some proper enemies, it's fine. I'd definitely update the BIOS (which also updates the EC), and fresh install Windows/Linux, but that's as far as I'd go.
I don't know anything that can do an in-place ext4 conversation, but there's ntfs2btrfs which is already in the Debian repos if you're okay with BTRFS.
Of course, backup anything important, ntfs2btrfs should create a backup snapshot if you need to revert back to NTFS, but I wouldn't count on it.
Nah, auto MDIX should've figured it out.
Also I'm not sure the 2.5G spec supports crossover cables anyway.
Here's the link for the curious: https://www.inaturalist.org/guide_taxa/292192
I probably wouldn't describe it as similar, but virt-manager is fairly simple but powerful at the same time (like it will let you expose more advanced KVM/QEMU features like PCIe passthrough and similar).
But like the other guy said, gnome boxes is very straight forward and probably more similar in it's simplicity.
They both use QEMU + KVM, so you can have both virt-manager and boxes installed at once, and I believe virt-manager (probably boxes too) easily let you use existing VirtualBox .vdi files, if you've got an existing VM you want to run. Also like I said before, KVM is already mainlined into the Linux kernel, so you don't have to install sketchy kernel modules and stuff.
I've only used VirtualBox once though, so I can't really compare them.
Nah the EFI partition only holds the data required to tell the BIOS/UEFI how to boot the operating system.
All the data on operating the SSD is stored as firmware in it's controller, it's not something you can accidentally erase.
You can use Cloudflare Tunnels too, so that you don't even need to port forward.
Maybe look into using the pstore, it can store kernel panics in ACPI or UEFI variables to be read by the next boot. Usually this is accessible at
/sys/fs/pstore, but if systemd-pstore is installed then it should be in the journal, but it can also be here:/var/lib/systemd/pstore.