Omarchy has changed its Kitty configuration after a security issue was identified with allow_remote_control yes.

That setting allows Kitty’s remote-control protocol to accept commands from terminal output, meaning untrusted output could potentially execute commands as the current user. Kitty itself defaults this setting to no; the exposure came from Omarchy explicitly enabling it so other parts of the desktop could query the active terminal’s working directory.

The change disables remote control by default and migrates existing explicit yes settings to no. Users affected by the migration need to fully close and reopen Kitty, as existing processes remain exposed until they exit.

There is a small trade-off: Omarchy can no longer reliably determine the active Kitty tab/pane’s working directory via its socket, so new terminal or Files launches may occasionally fall back to the home directory.

The associated migration tests reportedly pass, although no live Kitty test was run in the test environment

all 9 comments

sorted by: hot top controversial new old
[–] 49 points 2 months ago (3 children)

Does anyone use this vibecoded slop OS from fascist fans unironically?

  • source
  • hideshow 3 child comments
  • [–] 26 points 2 months ago (2 children)

    Unfortunately yes. Somehow the buzz around it has resulted in a decent number of e.g. YouTube channels with dev content talking about how great they think it is, which is bad for the discourse IMO

  • source
  • parent
  • hideshow 2 child comments
  • [–] 24 points 2 months ago (1 child)

    It's definitely being pushed by influencers, but there's no way it's getting any real adoption. People already familiar with Linux aren't installing this for real use em masse, and people not familiar aren't going this route with their first distro. I think the hype is all fabricated and pushed to the forefront of the algorithm.

  • source
  • parent
  • hideshow 1 child comment
  • [–] 34 points 2 months ago

    Wait... An AI slop 'distro' has a significant, built in RCE vulnerability? No way.

  • source
  • [–] 16 points 2 months ago

    Why do you need some terminal remote control for determining the working directory of a terminal exactly? Can't you just go down the process tree until you find the shell and do realpath /proc/<pid>/cwd on it? Am I missing something?

  • source
  • [–] 21 points 2 months ago

    I would be so happy if people stopped giving this #fashtech attention and just banned any mention of it on the fediverse. Any press is good press. I'll be adding a filter to spare myself the blight.

  • source
  • [–] 5 points 2 months ago

    🤣🤣🤣 First XLibre, now this. Right-wingers have no right to use the term LIBRE.

  • source
  • [–] 1 point 2 months ago

    "Alright ai, now make me a cool linux distro. Don't add too much of that facism we talked about. Oh and to get funding from the NSA we need to slip in. Misconfiguration. Make it look accidental. "

  • source
  • 24 comments in c/linux@lemmy.ml view that post
    [–] 60 points 2 months ago

    Clearly the results of either being high on slop or a literal mass exploiter

  • source
  • [–] 42 points 2 months ago (2 children)
  • [–] 28 points 2 months ago* (last edited 2 months ago) (3 children)

    Omarchy can no longer reliably determine the active Kitty tab/pane’s working directory via its socket

    Imagine this as the reason to allow remote access without questions. I watched an interview and he is proud to fix those issues (there were a few more security issues of this stupidity class) and thinks this is totally normal. And over time after fix after fix, Omarchy will become secure. He admits Omarchy is unsecure at this time. Edit: I should probably link to the interview in question: Invidious or YouTube

    The users are just beta testers, risking getting hacked. I could not trust this project. Even if all issues are fixed, who says no new security issues will make into the project? Omarchy is worse than Ubuntu and Manjaro combined.

  • source
  • hideshow 3 child comments
  • [–] 5 points 2 months ago (2 children)

    It's different, like the cybertruck. Different doesn't mean better but it sure does help point out why things were done the way they were.

  • source
  • parent
  • hideshow 2 child comments
  • [–] 17 points 2 months ago

    This is what happens when you let someone vibe code your distro's config

  • source
  • [–] 16 points 2 months ago

    This reminds me of the Docker issue they fixed in Omarchy recently. Basically you could get root through the docker socket, because the default user groups included the docker group.

  • source
  • [–] 15 points 2 months ago

    Am I going to hear about every insignificant development with Omarchy now because DHH ingratiated himself with a bunch of tech fascists?

  • source
  • [–] 14 points 2 months ago

    Nazi Linux is going well

  • source
  • [–] 15 points 2 months ago (1 child)

    In Kitty’s defense, the docs mention the risks involved with full remote control, and there several ways to control the scope of permitted actions.

    It’s tricky though. I’d like my coding agent to be able to control the terminal, but I’ve found it harder to sandbox kitty than, say, a multiplexer like tmux/zellij. Herdr is a bit less obvious.

  • source
  • hideshow 1 child comment
  • [–] 5 points 2 months ago

    13M USD budget "distro" btw

  • source
  • [–] 5 points 2 months ago (1 child)
  • [–] 7 points 2 months ago

    I might get downvoted to hell and back for this, but can we stop talking about this piece of work distro? I don't think the project needs any more PR, period, it's what the loser who made it wants. Let the people who for some reason trust this collection of dotfiles and scripts do so in their own foolish bubble.

  • source
  • [–] 1 point 2 months ago

    The funny thing is I think windows does this. I may be wrong

  • source
  • [–] 1 point 2 months ago* (last edited 2 months ago) (4 children)

    That does not allow remote code execution. An attacker still needs a vector like an SSH session to be able to control kitty. And at that point, if they already have a shell session, they don't need kitty to do damage.

    edit: giving access to other programs is not remote execution, but obviously not a good default.

  • source
  • hideshow 4 child comments
  • [–] 8 points 2 months ago (3 children)

    It actually also allows other programs to execute code through Kitty, example if you cat a file that has escapes in it. It would allow Kitty to execute that code when you never intended it... But like why does kitty even have that as a feature? But they've since updated the config to be set to socket only instead of yes

  • source
  • parent
  • hideshow 3 child comments
  • [–] 4 points 2 months ago

    Having the feature seems pretty in line with the general Linux philosophy. Let the user decide, even if that means they screw it up. Same reason you can muck up an install by just running updates on storage that doesn’t have enough room to do so. It’s up to the end user to understand, verify, and choose to execute.

  • source
  • parent