Live data from Hacker News

Omarchy: Any User Process Can Escalate to Root

0xcc.io

491–500 of 590 posts

Re: Omarchy: Any User Process Can Escalate to Root

#491
post #295

Earlier quoted context omitted.

A python program isn't a word document

People write real software using Microsoft Office's scripting features. Sure, it's not "cool" the way that Python is cool, but it works. And neither Microsoft nor Python has a credible security model.

They shouldn't be able to do that, because it's a huge security hole.

Re: Omarchy: Any User Process Can Escalate to Root

#492

Ubuntu is good enough. I never got the point of tiling window managers, because the most important part of daily computing, browsing the web requires you to use the mouse. I’ve tried keyboard only browsers, none of them are as intuitive as just using a mouse and they can’t be, especially considering the prevalence of hyperlinks. I guess while coding it is nice, but I can switch between the terminal and my editor in a…

Valid, but I’m unsure if mouse use needs to be mutually exclusive with a tiling window manager, and would like to suggest that all tiling managers are not necessarily made equal.

Niri for example, tiles but additionally introduces an infinite horizontal space, where you can slide between different windows like they’re on a film strip. The slide into view works with a mouse, and you can easily setup mouse bindings to move and reset windows. I think it’s better than just a stock floating windows manager because it feels easier for me to navigate an infinitely wide left-right and up-down space as opposed to an infinitely deep space into and out of the screen.

Re: Omarchy: Any User Process Can Escalate to Root

#493

Earlier quoted context omitted.

The whole point of Omarchy is for people who want to use Arch Linux but have it configured the way DHH does. So I think it's a little different. Anybody using an opinionated respin should understand what they're getting.

> people who want to use Arch Linux but have it configured the way DHH does Then they don't actually want to use Arch Linux. The Arch Linux way is to read the excellent wiki documentation, learn about all the choices available, and then make all of those choices so the system is configured the user's way instead of some celebrity's way.

I like and use Arch daily. My "way" was just to get past the fdisk squirrel catcher. After that it was as easy as Ubuntu. I'm not bragging, I wish I'd read the manual but was too impatient for that. I suspect I'm not the only arch user that arrived at it using similar approaches. I might even be a target user for DHH's distro but the bloat (and to some extent the vibe coding) holds me back.

Re: Omarchy: Any User Process Can Escalate to Root

#496
post #336
post #213

Earlier quoted context omitted.

That remains to be seen. The whole concept is still in its infancy. An AI reviewer should have caught these issues when they were PRs. But you see, it wasn't even a PR. It was just DHH making a straight up commit on the main branch (as far as I can see). With a message "Do all the additional Docker configuration needed". Was it even AI-assisted? At least the commit message wasn't, AIs write smarter commit messages th…

Which tells me that they don't really take security seriously because everyone knows exposing the docker socket is dangerous. I would almost bet that AI would warn about that.

> I would almost bet that AI would warn about that.

Exactly. If they had a review process. Which they didn't, at least for that change.

https://xkcd.com/1200/

Re: Omarchy: Any User Process Can Escalate to Root

#497
post #111

A few days ago someone found they were flowing USB descriptors straight into the shell. https://github.com/omacom/omarchy/commit/9285b19d6a72eba3df8... Don't use vibecoded distros. It doesn't matter whether they fix this or that, or whether you care about a particular vuln. This is not sensible. It's why you switched away from Windows in the first place, remember?

the unfortunate thing - is the money pumped into omarchy + the hype around it .... a lot of sheepish followers will just follow the hype. the tech might gets fixed later.

you mean the fun and DX? lol

Re: Omarchy: Any User Process Can Escalate to Root

#498
post #329

Earlier quoted context omitted.

I just switched over to it from Ubuntu. So far the nice thing is that it gives you a fully decked out hyprland setup without any of the hassle and pretty good UX. The problem I've always had with trying out a tiling window manager like hyprland is you're going to spend a very long time trying to get everything just right. With Omarchy I get a really nice hyprland setup right out of the box.

Github is awash with people's dotfiles including fully featured DEs built on top of things like Hyprland and Noctalia, and they don't require you to use a mess of a distro to use them.

Yeah, I mean when I set up my last distro I just installed claude and told it what I wanted and in about 30 minutes it was up and running. No need to install random distros!

Re: Omarchy: Any User Process Can Escalate to Root

#499
post #453
post #96

Earlier quoted context omitted.

Homebrew is like giving a bunch of wikipedia randos remote shell access to your computer. There is no enforced code review policy. Any maintainer can make a commit under a pseudonym and merge their own code to main without review. Homebrew should not be allowed near any machine you need to be able to trust.

This isn't true at all lol, if you make a PR to the formulas it is certainly reviewed. By a real human no less. wtf are you talking about

Only honest commits by good actors are reviewed. Good for QA but useless for security.

Cryptographic signing is not enforced for commits or reviews, so an attacker that controls a single maintainer Github API key could make a PR with a burner account then "review" and merge their own PR. Time it right and bury it in a dependency of a dependency and you are likely to get away with it. Especially considering they also do not do full source bootstrapping or enforce deterministic builds so including random binary-blobs in tree is a-okay and not sus at all.

The fact everyone is not aware of this is exactly why it is going to work, or already has.

I did once propose to the Homebrew community to enforce commit and review signing but they ultimately refused, worrying that asking people to press a button when it blinks would cause too many definitely smart and useful contributors to leave the project.

So instead they chose the honor system, like NPM.

Re: Omarchy: Any User Process Can Escalate to Root

#500

Earlier quoted context omitted.

First they should try making a solution that works as well as Docker. Every time I use Podman or Podman Desktop I run into the most basic problems. Docker works out of the box everywhere.

I don't use Podman desktop but I haven't had any issues at all with basic Podman. It just seems like a better overall design. It would be great if Docker copied the rootless / daemonless approach if possible.

For me the problems are always when I pull some image (like GitLab) and try to get it to work with podman. Or the hoops you have to jump through with podman-compose (user lingering, systemd services, privileged ports (80,443) [yeah I know it's a feature]). Docker just works, Podman (I feel) still requires stuff that makes it less declarative (to get to a running infra).

Still, having a gitlab runner with a docker in docker setup that can access the host docker socket is not something you do lighty, so I am eyeballing buildah etc.

I guess what really grinds my gears is that I'd use podman a looooot more if it could nicely coexist with Docker. I'd use Docker for the big services and podman for all my own stuff. But that is just not possible (at least not afaik), so it is also difficult to switch step by step (yes VMs, bla bla, but it's all complicating).

Post reply on HN