pull down to refresh
The main problem I have with NixOs is that somehow it feels extremely painful to do a system rebuild so i procrastinate. I just hacked my intel mac into a nixos box and I'm already looking for excuses to just switch to fedora or gentoo (though arguably the latter is a pain in the butt too), and just use nix for userspace (which frankly, would ideally be everything except kernel, firmware and drivers). If this is not a throwaway VPN (the one thing I meant to find out and failed, so yey bubblewrap) I do think you should update to .48.
learn more about kernel bugs.
That's a box of the pandora's kind for a while now... like 20 per day on a good day? ughhh! Lots of very specific ones though.
If this is not a throwaway VPS
It was meant to run on a throwaway VPS, but my internet here is really bad, so I couldn't upload the 1GB+ game filesystem to it haha. So I ended up running it on my personal laptop 🙈
Will run it on a throwaway VPS next time for sure. I won't have the element of (some) surprise on my side next time.
oh! Yeah I don't dev on my laptops anymore. I have clang for just-in-case but I do everything on dev VMs on remote boxes w/ luks. Which is why I try to keep an eye on kernel vulns, especially in virtualization space, because I don't want some neatly sandboxed shit to escape. Also I run my own actions runners, but those are on throwaway VPSs, same with bot harnesses.
No way those bots are going to break out of my jail and find they're in a lush area, no sir. Gonna be in a desert. A jail in a jail.
It's turned off, thanks!
This was def a little reckless. I hoped I didn't miss anything, but I knew it was likely I did (I almost forgot to clear the environment with the nsec for @ctfbot_ in it, lol). I'm glad it didn't take long for all flags to be found. I def didn't want to run this for a lot longer haha.
Thank you for testing and the valuable information! Running this bot more often will motivate me to learn more about kernel bugs.