Hacker News Reader

vqtskaon Show HN: Clawk – Give coding agents a disposable Linux VM, not your laptop

Sure, if you assume the agent will be hostile on you. I thought it's just so the agent doesn't accidentally rm -rf / on you

vqtskaon Show HN: Clawk – Give coding agents a disposable Linux VM, not your laptop

What kind of things are you even doing that the agent would try to perform a kernel exploit on you? I thought sandboxing is just to protect from the agent accidentally clearing your home directory.

Side note, just 6 days ago a Linux VM escape exploit was disclosed.

vqtskaon Show HN: Clawk – Give coding agents a disposable Linux VM, not your laptop

I still don't understand the point of all these VMs and containers for agents. Just create a separate user on your machine without sudo privileges, switch to it in your terminal and run all the agents you want without it being able to reach your files. What am I missing?

vqtskaon Show HN: Kage – Shadow any website to a single binary for offline viewing

I used a different project, https://github.com/marionebl/svg-term-cli

vqtskaon Show HN: Kage – Shadow any website to a single binary for offline viewing

You can also do an animated svg which is way smaller than a gif because it's just text keyframes (https://github.com/vytskalt/pseudoc/blob/main/assets/factori...)

vqtskaon Red Squares – GitHub outages as contributions

Forgejo has open source reimplementation of github actions

vqtskaon Show HN: I built a fast RSS reader in Zig

This looks kinda scary to me considering that Zig isn't a safe language and it's being used here to parse untrusted data from the internet. Would the ReleaseSafe mode that Zig provides prevent any attempts of exploiting memory safety bugs?

vqtskaon FFmpeg dealing with a security researcher

I wonder if this vulnerable codec is enabled by default when building FFmpeg? Because if so, then it doesn't matter that it's a "1990s game codec" because any application using FFmpeg to accept arbitrary video files is vulnerable to memory corruption, which should probably be taken more seriously.

vqtskaon GrapheneOS and forensic extraction of data (2024)

There is someone who leaks Cellebrite's support matrix to GrapheneOS dev's and it confirms that they are still unable to exploit it.

"Their documentation has explicitly listed GrapheneOS for years due to the high demand from their customers for breaking into it. It shows they were last able to exploit a GrapheneOS release with a 2022 or earlier patch level.

We have their June 2025 documentation and could obtain the newer documentation if we ask for it, but we have much bigger priorities than that right now and we would have been contacted by the main person providing it if anything relevant changed."

https://x.com/GrapheneOS/status/1965464817914831070