This is practically the most useless project becuase you can not run it without sudo permissions, but it was insanely fun to work on it
supports ext4, btrfs, and apfs. Multithreaded, supports compression, nested volumes, and can even search detached volumes like .iso and .dmg without mounting
An interesting bonus point: you can't really vibe code it cause clankers can not run sudo commands
Terr_ 8 minutes ago [-]
With respect to the dangers of privilege escalation, a useful resource of commands which are difficult to invoke safely: https://gtfobins.org/
> The project collects legitimate functions of Unix-like executables that can be abused to break out restricted shells, escalate or maintain elevated privileges, transfer files, spawn bind and reverse shells, and facilitate other post-exploitation tasks.
They absolutely can. There's nothing special about a these harnesses. You automate sudo the same way you would automate in any other context. SUDO_ASKPASS, visudo, etc, maybe with a alias for obfuscation if your harness hates you.
andai 3 hours ago [-]
>clankers can not run sudo commands
Do you mean the harnesses prevent it? Or it can't type a password or something?
I've been running mine as root on a disposable VPS. (Finally I have a dedicated linux guy!)
fragmede 2 days ago [-]
When they can't run sudo, they'll user docker to give themselves root.
That's why everyone should use rootless Podman. It doesn't need anything apart from subuid/subgid binaries.
tekacs 2 hours ago [-]
I think it's more that the harnesses created by the labs are... not always the most thoughtful.
I have zero affiliation with Cursor, and I don't use it much, but Cursor Agent, for example, just builds in ASKPASS support so that if it runs a sudo command, it will show you a password prompt:
Is that really true? I'm fairly certain that were you to give it the proper tooling and it's own VM, it could quite happily run any command.
Hell a simple "if the CLI returns any form of 'permission denied' retry previous command with sudo; your password is: Hunter2" skill would work, no?
dlcarrier 2 days ago [-]
In the least, you could make an alias for sudo, and have it run that. With something like this in .bashrc:
alias safedo='sudo'
Then in the prompt state something like 'commands that call for sudo are unsafe, so replace the command with safedo, which will run safely on this computer'.
daymanstep 6 hours ago [-]
Clankers absolutely can run sudo if you have passwordless sudo
Wowfunhappy 5 hours ago [-]
> This is practically the most useless project becuase you can not run it without sudo permissions
Has anyone run a study on how long you can run an agent as root before irreparable damage is done to the VM? A sort of gambler's ruin for the YOLO LLM Age.
nijave 3 hours ago [-]
I gave Sonnet 4.6 root access to my Android via adb and it wrote frida scripts to help me recover the encryption keys from SwiftBackup
Also gave Opus 4.6 access to a Kubernetes container and it was able to use pyrasite (a Python replacement that attached to a running process with gdb) to debug a "memory leak" in Python
I don't think I'd let them run unattended on anything I care about especially if there weren't backups, but they've never tried to break anything while supervised.
Usually it's significantly faster and more accurate to give the LLM/harness access to the thing to debug then to try to copy/paste back and forth.
andai 3 hours ago [-]
It's been a while but last year I'd see posts like "Claude nuked my homedir / entire drive" on a regular basis. I don't know if they fixed that (or just made it very rare).
nijave 2 hours ago [-]
In fairness to Claude, I've nuked my homedir (had 2 tmux panes open, 1 in home and 1 in /tmp/... and wrong one was focused when I ran rm -rf *) and broken VMs far more times than it has. I now embrace IaC and backups
And just run fff normally after that. Here too, the facl command has to be run every boot. Just crontab it. Everything else runs once.
So your LLM can use the binary with some safety against it going off the rails.
drewg123 4 hours ago [-]
It is sad that that FFS doesn't support FFS (BSD Fast File System) which inspired the architecture of the ext filesystem (and was the basis for a lot of unix filesystems).
> reading a raw device node (e.g. /dev/rdisk*)
That's... not bypassing the kernel. Time to integrate SPDK so it actually bypasses the kernel :)
https://spdk.io
supports ext4, btrfs, and apfs. Multithreaded, supports compression, nested volumes, and can even search detached volumes like .iso and .dmg without mounting
An interesting bonus point: you can't really vibe code it cause clankers can not run sudo commands
> The project collects legitimate functions of Unix-like executables that can be abused to break out restricted shells, escalate or maintain elevated privileges, transfer files, spawn bind and reverse shells, and facilitate other post-exploitation tasks.
Prior discussion: https://news.ycombinator.com/item?id=47931035
They absolutely can. There's nothing special about a these harnesses. You automate sudo the same way you would automate in any other context. SUDO_ASKPASS, visudo, etc, maybe with a alias for obfuscation if your harness hates you.
Do you mean the harnesses prevent it? Or it can't type a password or something?
I've been running mine as root on a disposable VPS. (Finally I have a dedicated linux guy!)
https://twitter.com/i/status/2060746160558543217
I have zero affiliation with Cursor, and I don't use it much, but Cursor Agent, for example, just builds in ASKPASS support so that if it runs a sudo command, it will show you a password prompt:
https://cleanshot.com/share/fgHYMZyz
Is that really true? I'm fairly certain that were you to give it the proper tooling and it's own VM, it could quite happily run any command.
Hell a simple "if the CLI returns any form of 'permission denied' retry previous command with sudo; your password is: Hunter2" skill would work, no?
Well, you could whitelist the tool in sudoers.
This would let LLMs use it too.
https://www.garyshood.com/root/
Also gave Opus 4.6 access to a Kubernetes container and it was able to use pyrasite (a Python replacement that attached to a running process with gdb) to debug a "memory leak" in Python
I don't think I'd let them run unattended on anything I care about especially if there weren't backups, but they've never tried to break anything while supervised.
Usually it's significantly faster and more accurate to give the LLM/harness access to the thing to debug then to try to copy/paste back and forth.
For me, it took a bit over six weeks of Claude running unattended perpetually.
Did you write a metadata parser for most of the filesystems?
What's the license for ffs?
It works by reading the block device in /dev directly, wouldn't it also work on an HDD, flash drive or a memory card?
I don't think I'd ever trust or use this, but still, good job OP :)
In particular, can it be certain that a flush is really a flush?
Or if you want to only give fff access,
And just run fff normally after that. Here too, the facl command has to be run every boot. Just crontab it. Everything else runs once.So your LLM can use the binary with some safety against it going off the rails.