I’m a talkative guy.
ArchBTW
I don’t trust that fish
- 0 Posts
- 42 Comments
ArchBTW@ani.socialOPto
Linux•KERNHELM: Intent-bound Linux authority for untrusted processes, while letting agents safely do moreEnglish
1·29 days agoYeah, I get why it reads that way at first, but I don’t think SELinux/AppArmor and KERNHELM are trying to answer the same question. SELinux/AppArmor are good broad confinement tools. They can say “this process/profile/domain is generally allowed to do X.”
KERNHELM is aimed at the standing authority problem underneath that. The issue is not just “can this process do this kind of thing.” The issue is “why does this process get to keep that authority sitting around at all?”
So instead of: “this program is allowed to delete files in this area”
KERNHELM wants: “this exact delete, against this exact target, was admitted through the trusted path for this user intent right now.” Then that authority burns/expires/revokes. It is not reusable standing permission. That’s why I don’t see it as lesser SELinux. SELinux/AppArmor can still define the broad walls. KERNHELM is more like a checkpoint at the gate: show the permit for this specific action right now, or it doesn’t happen. The thing that made this class of idea hard historically was latency. If every action has to stop and ask a model, remote service, or heavy policy engine what the user meant, it’s dead. KERNHELM’s move is to resolve intent before the hot path, convert it into narrow mechanical authority, and make the actual gate check cheap.
ArchBTW@ani.socialOPto
Linux•KERNHELM: Intent-bound Linux authority for untrusted processes, while letting agents safely do moreEnglish
12·30 days agoThe only application I see for this is AI-based bullshit, which makes this needlessly complicated.
Static scripts don’t get “confused”, and they certainly don’t get manipulated on a properly secured system. Why would you need an extra layer of security past the layers that already exist, when just properly securing the existing layers should be more than enough?
It’s not a AI application. AI is just the loudest fire right now, not the whole point. Its a new authority substrate for the whole system, intent-bound and enforced at the kernel level. A static script doesn’t get “confused,” sure. But scripts can still be wrong, overbroad or run in the wrong context or inherit more authority than they need or sit behind a supply-chain change you didn’t expect. Same with normal userland processes.
KERNHELM isn’t “because scripts have feelings.” It’s because ambient authority is just a bad default.
Existing layers are useful. I’m not saying throw them out. This is a different authority shape. Instead of “is this user, process, category usually allowed,” the question becomes “was this specific privileged effect actually admitted through the trusted path and carry the users intent”
Agents make the issue obvious because they can be steered in plain language. But the substrate is broader than AI. Anything untrusted reaching for privileged effects should have to prove authority at the effect boundary. Be it malware, an active attacker, overbroad script, compromised process or an AI agent.
ArchBTW@ani.socialOPto
Linux•KERNHELM: Intent-bound Linux authority for untrusted processes, while letting agents safely do moreEnglish
12·30 days agoFair question.
Code exists, but this repo is not the source drop yet. It’s the paper, claims, threat model, measurements. I held the implementation back because of a provisional patent side of this, but I’m probably going to publish a cleaned proof repo and the demo.
So yeah, if your bar is “show me the code,” this post does not clear that yet. Thats a fair hit.
ArchBTW@ani.socialtoHacker News@lemmy.bestiver.se•Make Trust Irrelevant: A Gamer's Take on Agentic AI SafetyEnglish
1·1 month agodeleted by creator
I think it means that stuff is always kinda bothering us and weighing us down and hasn’t been fully processed. when we lay down to sleep our brain is at rest and able to bring it forward to process it but we dont actually ever spend full conscious effort to do so. Almost holding onto it by not allowing ourselves to resolve it. At least thats just what I think I can’t know for sure. Ive started practicing writing them down and how to resolve it. Sometimes the answer is to just be content with it and let it go as a learning experience. Others ive gone to people and said I was sorry and they usually dont even remember and are like “oh no big deal” but it was to me apparently or I wouldn’t be thinking about it at 3AM cringing myself out XD spending the conscious effort though has seemed to help me come to terms with some stuff and those ones, at least, don’t come back randomly.
ArchBTW@ani.socialto
Technology•I investigated Windows 11's massive 5GB monthly .msu updates, and AI is only part of the problemEnglish
18·3 months agoThe “Any day now” just keeps holding hopeium and copeium. They dont have to deliver if any day is a phrase that keeps people putting off switching.
Side note to any power users that are planning on making the switch that I wish I knew back when I switched. (Types that really want a system thats theirs and dig in) don’t start out with a “user friendly distro” go straight to a main bloodline distro like Arch or Debian. Chances are you’ll end up on one anyway and it’ll save you time distro hopping.
Yea, reddit comments are littered with bots pushing narratives and astro turfing now.
I think trolling, AI isnt good at text. You ever see a shirt for sale with like a dumpster fire of a sentence on it? Decent example of AI generators when it comes to words. Usually there being actual words inside of images and coherent at that I take as a sign of being made by a human.
ArchBTW@ani.socialto
Gaming@lemmy.zip•Many more US states are planning or already have operating system age verification lawsEnglish
11·5 months agoOS Dev won’t be the problem. Its bull shit laws thats forced upon them in order to keep the project alive. No one wants to be the dude that has to keep up with securing the new literal front door on a distro. This shit is a security nightmare. Devs ain’t the top of this food chain the distro’s shut down and we have what? TempleOS?
Heh, this one is always a fun reminder
ArchBTW@ani.socialto
Anime@ani.social•From Old Country Bumpkin to Master Swordsman • Katainaka no Ossan, Kensei ni Naru - Episode 2 discussionEnglish
1·5 months agoAnd the blacksmith
Could always dissolve in a tiny bit of water boiled like making a simple syrup. Then add to the moo juice to make thilk. You could even flavor it however you want; it would be a 1950’s dream.
If you’re not compiling your own kernel are you really running Arch?





They are getting more bold and now people are realizing privicy nerds (I’m one myself) are, in fact, not crazy.