this post was submitted on 19 Jul 2024
1 points (100.0% liked)
Technology
59587 readers
5279 users here now
This is a most excellent place for technology news and articles.
Our Rules
- Follow the lemmy.world rules.
- Only tech related content.
- Be excellent to each another!
- Mod approved content bots can post up to 10 articles per day.
- Threads asking for personal tech support may be deleted.
- Politics threads may be removed.
- No memes allowed as posts, OK to post as comments.
- Only approved bots from the list below, to ask if your bot can be added please contact us.
- Check for duplicates before posting, duplicates may be removed
Approved Bots
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
This is why every machine I manage has a second boot option to download a small recovery image off the Internet and phone home with a shell. And a copy of it on a cheap USB stick.
Worst case I can boot the Windows install in a VM with the real disk, do the maintenance remotely. I can reinstall the whole thing remotely. Just need the user to mash F12 during boot and select the recovery environment, possibly input WiFi credentials if not wired.
I feel like this should be standard if you have a lot of remote machines in the field.
In theory that sounds great, now just do it 1000+ times while your phone is ringing off the hook and you're working with some of the most tech illiterate people in your org.
Still better than guiding the user to safe mode with command prompt and bitlocker recovery keys themselves.
I'm pressing F and 1 and 2, but nothings happening!
Sounds like a nightmare for security, and a dream for attackers.
More companies need to do this, solid job security.
You can sign the whole thing, it's not like you have to turn off secure boot and just drop the user to a root shell. There's nothing to be gained from it, especially if you have physical access to the machine.