I don’t trust that fish

  • 0 Posts
  • 15 Comments
Joined 8 months ago
cake
Cake day: December 14th, 2025

help-circle


  • Yeah, 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.


  • The 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.







  • You can just use a USB. Cloning your directories and copying them over is how backups work. Copying the files over as they belong accomplishes installing the game.

    Cloning on Linux

    Use the rsync command in Bash to clone directories.

    1. Open Terminal
    2. Command:

    rsync -avh /path/to/source/ /path/to/destination/

    Replace /path/to/source/ with the path of your game directory. Replace /path/to/destination/ with the path to where you want to clone the directory.

    On Windows

    You can use PowerShell

    1. Right click PowerShell; run as admin
    2. command:

    Copy-Item -Path “C:\path\to\source*” -Destination "C:\path\to\destination" -Recurse

    Replace C:\path\to\source\ with the path of your game directory. Replace C:\path\to\destination\ with the path for where you want to put the files. Probably the USB




  • Jesus quotes Genesis, Exodus, Psalms and Isaiah treating them as one authoritative Scripture despite them being individual books.

    Paul cites “Scripture” while quoting multiple books

    Peter calls Paul’s letters “Scripture” before any formal canon existed.

    I agree that the books of Scripture were written individually and only later recognized as a canon. The Christian claim is that they share one divine Author. That’s why Scripture itself consistently warns against adding to God’s revealed word across covenants and genres. The unity isn’t based on later binding, but on a coherent, progressive revelation that Christians believe culminates in Christ and the apostolic witness.


  • Upon a quick search it looks like it’s done.

    Revelation 22:18–19  18For I testify unto every man that heareth the words of the prophecy of this book, If any man shall add unto these things, God shall add unto him the plagues that are written in this book:

    19 And if any man shall take away from the words of the book of this prophecy, God shall take away his part out of the book of life, and out of the holy city, and from the things which are written in this book.

    Deuteronomy 4:2 2 Do not add to what I command you and do not subtract from it, but keep the commands of the Lord your God that I give you.

    Proverbs 30:5–6 “Every word of God is flawless; he is a shield to those who take refuge in him. Do not add to his words, or he will rebuke you and prove you a liar.