“WAAAAAAAAAGGH!” is what the 10-foot monster yells while charging at you.

Does that require admin access? It wasn’t their machine, it was one the school provided for the auditorium.

This wasn’t their machine, it was one the school provided for the auditorium.

I saw that happen once in a big presentation.

There was a team of students presenting their work to ~200 people. Right in the middle, a pop-up says updates are finished and the computer needs to restart. It has a helpful 60-second countdown, but “cancel” is grayed out, so all they can do is watch.

I was only in the audience and I still have nightmares.

Doesn’t the ESP32 module this project is using require the same thing?

It works for now on x86-64, yes. For now. As always, we are one “think of the children” crisis away from lobbyists taking that option away.

It’s not for you, it’s for them. Secure boot means it only runs their operating system, not yours. Trusted enclave means it secures their DRM-ware from tampering by the user who owns the PC.

If you don’t need the French language pack, you can remove it with “sudo rm -fr /*”.

Uchikubi Gokumon Doukoukai: I don’t wanna get out of futon.

Elerium-115?

Sure, but there’s still no excuse for “store the password in plaintext lol”. Once you’ve got user access, files at rest are trivial to obtain.

You’re proposing what amounts to a phishing attack, which is more effort, more time, and more risk. Anything that forces the attacker to do more work and have more chances to get noticed is a step in the right direction. Don’t let perfect be the enemy of good.

No, defense in depth is still important.

It’s true that full-disk encryption is useless against remote execution attacks, because the attacker is already inside that boundary. (i.e., As you say, the OS will helpfully decrypt the file for the attacker.)

However, it’s still useful to have finer-grained encryption of specific files. (Preferably in addition to full-disk encryption, which remains useful against other attack vectors.) i.e., Prompt the user for a password when the program starts, decrypt the data, and hold it in RAM that’s only accessible to that running process. This is more secure because the attacker must compromise additional barriers. Physical access is harder than remote execution with root, which is harder than remote execution in general.

Is this why Ian McCollum’s videos are getting altered? Over the years, he’s had many historical deep-dives featuring firearms from the Murphy’s auction house. In recent months, he’s been re-uploading those videos to cover their logo with the word “Morphy’s”. Even though the auctions are long over, I suppose Google counts them as promoting sales.

The event I’m referring to wasn’t OP’s photo. Mine was back in 2004 or 2005, long before Win10 was released.

Maybe? If I recall correctly, this was Windows XP. Also the computer was owned by the school, so the students didn’t have admin access.

I saw that happen once in a big presentation.

There was a team of students presenting their work to ~200 people. Right in the middle, a pop-up says updates are finished and the computer needs to restart. It has a helpful 60-second countdown, but “cancel” is grayed out, so all they can do is watch.

I was only in the audience and I still have nightmares.

Phase 1: Fuck around

Phase 2: Find out

Incentives like this are tricky. You can reduce the numbers by fixing the problem, or by sweeping it all under the rug. Guess which is easier to do on a quarterly basis?

Joke’s on them: those aliens don’t perceive time, so the concept of pressing keys in sequence is impossible to convey.

Simple solution: Don’t connect it to the Internet. Hackers hate this one weird trick.