Live data from Hacker News

OpenClaw privilege escalation vulnerability

nvd.nist.gov

101–110 of 306 posts

Re: OpenClaw privilege escalation vulnerability

#101
post #2
post #179

[stub for offtopicness and general piling-on behavior, which we don't want on this site] [[attacking project creators when they show up to discuss their work is particularly harmful; please don't ever do that here]] [[[if you posted any of these, we'd appreciate it if you'd please review https://news.ycombinator.com/newsguidelines.html and stick to the rules from now on]]]

[flagged]

Hanlon's Razor

https://en.wikipedia.org/wiki/Hanlon%27s_razor

Re: OpenClaw privilege escalation vulnerability

#102
post #32

I don't use OpenClaw, but I still run my Claude Code and Codex as limited macOS user accounts and just have a script `become-agent [cmd ...]` that does some sudo stuff to run as the limited user so they don't have any of my environment or directory access, or really any system-level admin access at all. They can use and write to their home directories as usual, which makes things easier to configure since those CLI h…

Yes, if/since that user have no access to your apple id and keychain...

Not too much harder is using a VM:

With Apple's open-source container tool, you can spin up a linux container vm in ~100ms. (No docker root)

With Apple virtualization framework, you can run macOS in a VM (with a separate apple id).

Re: OpenClaw privilege escalation vulnerability

#103
post #80
post #179

[stub for offtopicness and general piling-on behavior, which we don't want on this site] [[attacking project creators when they show up to discuss their work is particularly harmful; please don't ever do that here]] [[[if you posted any of these, we'd appreciate it if you'd please review https://news.ycombinator.com/newsguidelines.html and stick to the rules from now on]]]

[flagged]

- "OpenClaw, read the code"

- "You're absolutely right. One should read and understand their own code. I did, and it looks great"

Re: OpenClaw privilege escalation vulnerability

#107
post #66
post #179

[stub for offtopicness and general piling-on behavior, which we don't want on this site] [[attacking project creators when they show up to discuss their work is particularly harmful; please don't ever do that here]] [[[if you posted any of these, we'd appreciate it if you'd please review https://news.ycombinator.com/newsguidelines.html and stick to the rules from now on]]]

[flagged]

What time was that and who do we get to blame for Log4j?

Re: OpenClaw privilege escalation vulnerability

#108
post #97

Earlier quoted context omitted.

What would you propose as an alternative? Anything not relying on an LLM likely means having to write bespoke scripts. That's not really worth the time, especially when you want summaries and not having to skim things yourself. Going from doing it manually on a regular basis to an autonomous agent turns a frequent 5-15 minute task into a 30 second one.

> Anything not relying on an LLM likely means having to write bespoke scripts. The very first line in your readme is "CivicClaw is a set of scripts and prompts" though? And almost the entire repo is a bunch of python scripts under a /scripts folder. I looked at one randomly chosen script (scripts/sf_rec_park.py) and it's 549 lines of Python to fetch and summarise data that is available on an RSS feed ( https://sanfra…

Parent isn't saying that bespoke scripts are bad, just that it's not worth their time to write them. The value of the bot is that it can do that for you.

Re: OpenClaw privilege escalation vulnerability

#109
post #102
post #32

I don't use OpenClaw, but I still run my Claude Code and Codex as limited macOS user accounts and just have a script `become-agent [cmd ...]` that does some sudo stuff to run as the limited user so they don't have any of my environment or directory access, or really any system-level admin access at all. They can use and write to their home directories as usual, which makes things easier to configure since those CLI h…

Yes, if/since that user have no access to your apple id and keychain... Not too much harder is using a VM: With Apple's open-source container tool, you can spin up a linux container vm in ~100ms. (No docker root) With Apple virtualization framework, you can run macOS in a VM (with a separate apple id).

> Yes, if/since that user have no access to your apple id and keychain...

Right, these are system accounts. They don't have access to anything except their own home folder and whatever I put in their .bashrc. `sudo` is a pretty easy sandbox by itself and lets me manage their home folders, shell, and environment easily just with the typical Unix-isms. No need for mounting VM disks, persisting disk images, etc.

I don't need virtualization to let Claude Code run. I just let it run as a "claude" user.

Post reply on HN