Posts
3165
Following
706
Followers
1560
"I'm interested in all kinds of astronomy."
repeated

Trusting your own judgement on 'AI' is a huge risk: https://www.baldurbjarnason.com/2025/trusting-your-own-judgement-on-ai/

5
9
0
repeated
I think this will be the day when we'll have The Talk with kiddo...

I'm only thinking about basic Git commands for linear version tracking, he'll learn about branching and merging as he gains some experience.

#parenting
1
0
7
repeated
Edited 7 months ago
LinkedIn upped their cookie banner game so much I literally can't use the site anymore. This is probably the most useful feature update they did in the last 10 years!
0
1
4
Just set some of my recursors to DNS4EU, let's see how it performs!

https://www.joindns4.eu/for-public#resolver-options
1
0
1
repeated

We wrote a blog post about a Linux kernel vulnerability we reported to Red Hat in July 2024. The vulnerability had been fixed upstream a year before, but Red Hat and derivatives distributions didn't backport the patch. It was assigned the CVE-2023-52922 after we reported it.

The vulnerability is a use-after-free read. We could abuse it to leak the encoded freelist pointer of an object. This allows an attacker to craft an encoded freelist pointer that decodes to an arbitrary address.

It also allows an attacker to leak the addresses of objects from the kernel heap, defeating physmap/heap address randomization.These primitives facilitate exploitation of the system by providing the attacker with useful primitives.

Additionally, we highlighted a typical pattern in the subsystem, as two similar vulnerabilities had been discovered. However, before publishing the blog post, we noticed that the patch for this vulnerability doesn't fix it. We could still trigger the use-after-free issue.

This finding confirms the point raised by the blog post. Furthermore, we discovered another vulnerability in the subsystem. An out-of-bounds read. We've reported them, and these two new vulnerabilities were already patched. A new blog post about them will be written.

Use-after-free vulnerability in CAN BCM subsystem leading to information disclosure (CVE-2023-52922)

https://allelesecurity.com/use-after-free-vulnerability-in-can-bcm-subsystem-leading-to-information-disclosure-cve-2023-52922/

1
4
0
repeated

I don’t know who to credit for this, but it’s beautiful

6
10
0
repeated

A human being should be able to change a diaper, plan an invasion, butcher a hog, conn a ship, design a building, write a sonnet, balance accounts, build a wall, set a bone, comfort the dying, take orders, give orders, cooperate, act alone, solve equations, analyze a new problem, pitch manure, program a computer, cook a tasty meal, fight efficiently, die gallantly. Specialization is for insects.

— Robert A. Heinlein

0
3
0
repeated

WinDBG vs esReverse: same concept (time travel debugging), very different scope.

We break down the differences in our blog: https://eshard.com/posts/difference-between-windbg-and-esreverse

0
2
0
[RSS] Discovering a JDK Race Condition, and Debugging it in 30 Minutes with Fray

https://aoli.al/blogs/jdk-bug/
0
1
3
repeated
repeated
How Compiler Explorer Works in 2025 — Matt Godbolt’s blog
https://xania.org/202506/how-compiler-explorer-works

#fromBsky
0
3
4
repeated

Zen quote of the day.

5
16
2
repeated

When you go to the lavatory, spend a longer time there than is necessary.

0
3
0
repeated

⚠️ woman reportedly found having fun

7
2
0
repeated

Communist Poland was exceptionally good at making fun of secret police and egomaniacal leaders.

If my American friends need some good authoritarian jokes so that they can keep their spirits up for the long run I can suggest some!

6
8
0
repeated

In case anyone here has connections with the Python team: can you please tell them to update their docs on XML security? The way it is is quite misleading, and it's been annoying me for a while. I raised this a while ago in their issue tracker, but it got no reaction whatsoever. https://github.com/python/cpython/issues/127502 🧵

1
1
0
Show older