cd /news/ai-policy/restricted-boot-garrett-s-state-is-n… · home › topics › ai-policy › article
[ARTICLE · art-143076] src=techrights.org ↗ pub= topic=ai-policy verified=true sentiment=↓ negative

"Restricted Boot" Garrett's State is Now Implementing Kill Switches (Just What We've Warned About All Along)

The Free Software Foundation has published comments opposing California Governor Gavin Newsom's executive order on artificial intelligence, arguing the order advances remote "kill switch" powers over computing. The FSF post links the order to the existing UEFI "Restricted Boot" mechanism and to the proposed AI Kill Switch Act, which critics compare to the 1990s Clipper chip. The commentary contends that deployed AI systems that should have been pulled offline have not been, so any kill switch would be used for purposes other than reining in large language models.

read2 min views1 publishedOct 1, 2026

The underlying concept is hardly new. In practice, the kill switches already exist (they got implemented and deployed), now they're being legislated in the state where Garrett and his spouse live.

The Free Software Foundation has just issued "comments on Newsom's executive order on so-called artificial intelligence". This is significant (c.f. "The AI Kill Switch Act is repeating the Clipper Chips mistakes"). So they're working towards having state powers to kill things remotely - a kill switch basically. Imagine what this would mean to foreign nations.

As we said before, the GGG brigade ("Restricted Boot" G arrett, "Microsoft Plagiarism" G raveley & "G as The Jews" Lozza) was a response to things I've written since 2012 against Microsoft's "Restricted Boot", culminating in SLAPP letters in 2021.

What we're seeing here is a US state (California, where Garrett of "Restricted Boot" infamy lives and works for a slop company) working towards greater control over computing and "also one of the blogs pointed out that the LLMs are performing in such a way that they should have been pulled offline long ago already but haven't," an associate reminds us. "Thus that demonstrates already that any "kill switch" is going to be used for just about any purpose except reining in LLMs."

"It's not the slop which is relevant but the kill switch, which in the case of the existing slop, has not been used. This goes back to the Clipper chip and is germane to software freedom / freedom in general. Restricted boot and TPM also fit into that puzzle..."

"The existing slop situation shows solidly that even in circumstances where the plug should be pulled, the plug is not getting pulled. Rather the slop peddlers are fanning the flames further. So if the kill switch is not for slop, what is it really intended for? Hint: same as restricted boot, clipper, etc."

Imagine what a dumb person would say; that it's "computer security" to put kill switches that update themselves every 12 hours (you're never in control, this cannot be turned off).

Such "computer security" is promoted by people with no background in Computer Science [1, 2], just a rude Twitter account and self-curated Wikipedia page.

Of course we can trust "MAGA" to control kill switches deployed to every country, right? █

── more in #ai-policy 4 stories · sorted by recency
── more on @free software foundation 3 stories trending now
sponsored brought to you by zahid.host 4,200+ EU-deployed projects
reading about agents? ship yours in a single git push.

Run your AI side-project on zahid.host

EU-based hosting, git-push deploys, automatic HTTPS, no cold starts. Free tier with a custom domain — perfect for shipping the agent you just read about.

$git push zahid main
→ Live at https://your-agent.zahid.host ✓
Get free account → Pricing
from €0/mo · no card required
LIVE [news/restricted-boot-garr…] indexed:0 read:2min 2026-10-01 · —