this post was submitted on 08 Oct 2023
788 points (98.6% liked)
Programmer Humor
32508 readers
697 users here now
Post funny things about programming here! (Or just rant about your favourite programming language.)
Rules:
- Posts must be relevant to programming, programmers, or computer science.
- No NSFW content.
- Jokes must be in good taste. No hate speech, bigotry, etc.
founded 5 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
There could in theory be an infected machine on the internal network that was previously infected, which is now acting as command and control. So if you didn't know which one it was...
Turn of the power, no need to rip anything
Use a bomb. No need to take out the lights.
Nuke it from orbit. It's the only way to be sure.
It's better to throw it away into a black hole.
That's generally a good idea, however, there can be reasons not to do it.
The device could be infected in a way that it won't turn on again.
You might have an isolated management network that allows you to monitor the device and traffic (naturally ripping all cables also disconnects the management network).
And whatnot. But generally I agree.
You two are overlooking the most important thing. It might be fun to crazily rip out the cables then make a junior guy go trace and repatch it all. The opportunity to legitimately do that doesn't come along often.
Where's your sense of drama???