What is “the right way”, exactly?

What’s do you mean “properly”? Certs are supposed to expire, so that in the case of compromise the use is still limited.

That would probably depend on the hardware acceleration for video encoding and decoding on your particular system. Doing it in software, especially for low-spec devices, is going to greatly limit your resolution and quality if you want a reasonable frame rate.

So it looks like the only significant factor was that you reduced the amount of heated space.

It might be the CPU, but it might be something else. On the old CPU, update the OS, update the BIOS, and run fwupd or boot Windows temporarily to update all other firmware. Then run memtest and a cpu stress test to make sure you’re not just triggering an existing hardware issue.

If that’s all clean, put in the new CPU and run memtest and a cpu stress test to see where you get issues.

You could set the password to be the same. It’ll attempt to use all known methods when unlocking it.

You can also probably store a key on the root drive instead of using a password, but I’ve never done that.

Please no. I can’t grep that. (Nor ingest it to splunk for more powerful searching.)

What, exactly, are you running? What is it doing?

I just don’t see the advantage of shoehorning graphics backwards into text interfaces when we’ve got an entire integrated graphical desktop.

Images in the terminal? At that point you’re just reinventing the GUI.

It’s not piracy if it’s not available legally.