This is turning into a fun week for anyone in cybersecurity or just IT in general. Glad I'm taking sabbatical right now.

That's when you remove a model's built-in guardrails. What they are probably talking about are 'sleeper agents' (from the Hubinger paper from 2024). Basically you intentionally poison the training in such a way that the model looks normal for most requests but for very specific requests it turns malicious. This could be anything from an intentionally faulty analysis up to triggering data exfil or causing damage with external tool calls (if the model is setup for them in the first place of course). It's all academic right now but also completely plausible. And trying to audit for it would be challenging since it's part of the model's base training.

You could also do this with post-training to an existing benign model but that's going to be easier to spot if both models, or at least the untampered base model, is publicly available for comparison.

Someone jumped the gun and dropped the exploits and working code for them last night.

Sorry but that is the answer, it's what internal CAs are for. If the devices truly do not support automation, and you need certs for them (do you really need them if this is a home or small office network?) then your choice is use public certs and live with the ever-shorter expiration requirements or put up your own CA.

There's this new thing called an internal CA where you can issue your own certs with whatever expiration date you feel like.

So MoE doesn't save on RAM, it saves on compute. You still need to load the model weights into GPU memory otherwise you would cripple the model's speed since each token can be routed to a different "expert" and those weights would need to be copied from system to GPU memory when an new is expert called. Some people do it that way but they are community folks doing it for the LoLs and not anything running at the enterprise level. The trick Qwen-Flash-Next does is move their 51B N-gram embedding table into system RAM. That does save a decent amount of memory since it's 51B params you don't need to store in vRAM. That model's main weights are 125B params so it's a hefty savings to keep those additional parameters out of the GPU RAM.

OK Harry R. Truman, you do you.

I didnâ(TM)t catch that in TFS. I just clicked thre TFA then the Apple source post. Why the fuck did they break it up like that?! Almost feels intentional.

Again this is ALREADY A RESTRICTED PERMISSION AND HAS BEEN FOR QUITE A WHILE. They are just changing the flow for enabling it. You can still enable it.

How do you figure that? From the Apple post: "Going forward, we will introduce additional controls to ensure that users who genuinely wish to grant an app this extraordinary level of access can only do so with very explicit user action. "

It's already a OS controlled permission today. You will still be able to enable it for an app if you really want, they just want to make tighten the gate up to make sure you really want to and don't blind-click though. Seems like a reasonable compromise to me.

I was looking at why one of the RSS feeds on my homepage (yes, I still use one, shut up, I'm old) and when I loaded the feed URL in my browser it was being fronted by a cloudflare bot check.

In the short term. Right now the bad guys (well, non-state bad guys) don't have access to frontier models with the cyber security nanny mode disabled. However open source models are getting better every day and most don't have those guardrails, and even if they do it's not impossible to remove them when you have access to the weights. So yea, short term it's going to be an issue.

Long term, however, once this initial tsunami is worked through then hopefully more of these types of bugs will be found before new code ships, making it harder to find critical vulnerabilities in the wild.

Could be why he wants to rename it: https://techcrunch.com/2026/09...

Yea if you ever hear a F-16 pilot talk about landing with anything serious wrong with the aircraft, they usually mention booking it the hell away from the jet as soon as they can get out because of that hydrazine risk if a fire starts.

F-16's have a tank of hydrazine on board. It's used to power the emergency power unit which can provide backup electrical and hydraulic power. Whenever there is an incident with one they treat it as a hazmat situation just to be safe.