Developer 🤓 – Consultant 👔 – Load Tester 🚀
Haven't seen a big splash in the (IT) news yet, but apparently there is a 16 year old vulnerability in KVM which can be used to escape a guest and even take over the host (CVE-2026-53359): https://github.com/V4bel/Januscape. If /dev/kvm is available (world-writable on the host), it can also be used as a LPE to root.
This is kind of bad. REALLY bad.
In a #Rust application, why would I specify a dependency version in Cargo.toml, if I don’t care about a specific version? Like using “*" by default.
Cargo.lock would contain a concrete version, so stuff doesn't break randomly, everybody gets the exact same version. If there is an incompatible change, you can add constraints, like limiting it to version “2” for example.
Which one of the #redis drop-in replacements is still active and maintained these days?
It’s for the Celery worker of paperless and I'm not exactly sure what is needed feature wise. I was just wondering what you would replace "docker.io/library/redis:8" with in a docker-compose file 😀
Any #ruby #minitest users in my timeline? Today I tried to understand how to use MiniTest::Mock to expect a method call with some positional arguments, but arbitrary (none or any) keyword arguments.
I think you can’t. It's just not a thing. The only way to do this, is to use the block form with MiniTest::Mock#expect and to all argument matching yourself.
What am I missing here?
Disclaimer: I’m deep in the RSpec camp when it comes to Ruby test frameworks 🫣
People on the internet trying to look smart by saying "not vibe coding" is like "not using a calculator”. Quite an evolution to the "like not using compilers” I have to listen to in person.
What is this? Some kind of spammy cold calling/outreach? I most certainly did not trigger this. The email looks very legit (as in comes from Anthropic). It's sent to an old email I basically don't use anymore.
Nice "hack" to get all your gists from Github, including private ones by @FND@hachyderm.io: https://prepitaph.org/snippets/gist-exfil/
Copy Fail (https://copy.fail/, CVE-2026-31431) is a good reminder why I don’t want to run CI jobs only in containers.
It would be great to get some momentum to https://code.forgejo.org/forgejo/forgejo-actions-feature-requests/issues/4 (microVMs for forgejo actions). At least on bare metal (or nested VMs with nested KVM) this would make things a lot safer. It would also simplify the usage of containers/docker in CI jobs without compromising security, which is kind of a pain with Codeberg Action currently.
Aside from the abysimal uptime Github currently presents, they -also- had one of the worst security incidents you can think of: An RCE via a simple “git push” with total loss of tenant isolation (via https://www.wiz.io/blog/github-rce-vulnerability-cve-2026-3854).
If GitHub weren't such a central piece of infrastructure, the current situation would be disastrous for their business.
