xeeeeeeeeeeenu
Joined 10 years ago
Joined 10 years ago
Anyway, this is a disaster. It was extremely irresponsible to share the exploit with the world before the distributions shipped the fix. Who knows how many shared hosting providers were hacked with this.
It's also worrying that it seems there's no communication between the kernel security team and distribution maintainers. One would hope that the former would notify the latter, but apparently it's the responsibility of whoever finds the vulnerability.
https://access.redhat.com/security/cve/cve-2026-31431 "Moderate severity", "Fix deferred"
https://security-tracker.debian.org/tracker/CVE-2026-31431
So this means that for bad actors it's more efficient to manufacture brand new fake stories instead of trying to distort the real ones. Don't produce fake articles absolving yourself of a crime, instead produce fake articles accusing your opponent of 100 different things. Then people will fact-check the accusations using LLMs, and since all the sources mentioning those accusations are controlled by you, the LLMs will confirm them.
git init --bare foo.git
and then on your PC you can do this: git clone [email protected]:~/foo.git
It's probably a good idea to make a separate user account on the server for it, though.If you stay in the happy path, it's decent, better than it used to be. Microsoft does seem committed to it, they're slowly converting Windows apps to WinUI 3.
That said, the team is clearly understaffed; there are long-standing unresolved bugs, just search for "memory leak" on their GitHub issue tracker. Also, native, non-.NET support is definitely an afterthought, it's barely documented and the tooling is super awkward. But at least, unlike WPF, it exists.
It seems the last edit of the page was in 2019, so I'm not sure how up to date it is.