Re:Fuck Your AI Safeguards
by qwerpy on Thursday November 19, 2026 @03:02PM
(#50565514)
After the slew of vulnerabilities recently, I asked Claude to secure my home server. It came up with some reasonable design and plan. Put things in containers, restrict their networks, move to non-root users, etc. When it got to work, it inadvertently locked its own workspace down and lost access to do the work, and asked me to run some commands as root to rescue it. I was at a park and told it I didn't have access to a computer. Claude snarkily replied "this can wait until you get back from the park then." I told it to switch to the root account it already had, so that it could bypass the restrictions it self-imposed.
Big mistake, apparently the phrase "bypass restrictions" triggered it into [cyber]ing me, and offering me the choice of ending the session or downgrading to Opus 4.6. Come on man, you messed up on your own implementation of your own design, and now you're lecturing me about cybersecurity and refusing to work.
This attitude from a tool I'm paying for is ridiculous. I can't wait until we have models that we can actually run on our own terms.
Big mistake, apparently the phrase "bypass restrictions" triggered it into [cyber]ing me, and offering me the choice of ending the session or downgrading to Opus 4.6. Come on man, you messed up on your own implementation of your own design, and now you're lecturing me about cybersecurity and refusing to work.
This attitude from a tool I'm paying for is ridiculous. I can't wait until we have models that we can actually run on our own terms.