Sometimes I think it’s going to be the librarians who will save us all.

I just went to request a feature in #KDE on #Linux and saw that the feature had been requested 10 years ago. I added a comment to bump it and see if it was still under consideration when I got a ding on my phone.

Turns out I had commented on the same bug, under an old email address, seven years ago.

If you only enable scripts on soundcloud[.]com the site doesn't load but no blocked scripts show up either.

Back in the day people were burned at the stake for shit like this.

I've seen a number of people (including some well-respected people in the infosec sphere) promoting a particular blog post/writeup recently about the macOS secure boot chain. As someone who has done a fair bit of research and reverse engineering of iBoot and Apple's secure boot chain over the years, this naturally piqued my interest so I decided to take a look, at minimum to see how much it lined up with my RE of iBoot over the years.

Unfortunately after reading the blog post thoroughly, I can pretty confidently say this: the writeup is almost certainly a pile of AI slop. Let's dive into it and discover some major red flags that I found.

Let's talk about something that I think a lot of the people reposting this post haven't realized yet: this post was *very* factually wrong when it was first posted. (Here (https://web.archive.org/web/20251122220347/https://stack.int.mov/a-reverse-engineers-anatomy-of-the-macos-boot-chain-security-architecture/) is a link to the earliest version on the Wayback Machine, very good resource btw ) Shoutouts to @nicolas17 btw for making archives once he noticed the article rapidly changing, he puts in a lot of work in the archival side of things that imo goes very unnoticed, but his work helps Apple security research in the long run.

This original version of the post has several factual errors (there are too many to list but some of the VERY obvious ones include Apple silicon chips starting at EL3 when no M-series *Mac* chip has implemented EL3 (which is optional per ARM spec) In addition there is contradictory info about the ECID, incorrect info on security fuses, etc, there's a LOT of slop to digest here along with tons and tons of jargon that makes no sense.)

The fact the post gets stuff wrong in and of itself is not the issue (a mistake here and there is completely understandable and in fact quite human), the issue is with the *magnitude* of *how many factual errors* were posted publicly, seemingly without any fact checking or sourcing, it really is quite egregious just how wrong this post is (even the current version of the post still has *many* of these errors), especially to any person who has even took a cursory glance at iBoot or the secure boot chain.

The syntax, per people I discussed this with, screams that it was based on prompting Claude (an LLM that seems to have more natural writing style than some of the others.)

However, what *really* is super insidious is the *history* behind this post. This (https://gist.github.com/nicolas17/81d082c93599c8bc70492caabb97289d/revisions) is a link to diffs of the post over time, and it's pretty damning. The post had very very large chunks changed in very short amounts of time across multiple parts of the very long post, and with how long the post is, this is probably outright infeasible for a human to do in that short time frame (especially when incorporating time to fact-check the updated parts, which any writeup worth their salt imo *should be doing.*)

Per these two comments (https://news.ycombinator.com/item?id=46020891) (https://news.ycombinator.com/item?id=46020395) on HackerNews, along with the drastic changes mentioned before (especially considering that the post changed quite drastically between revisions, saved versions of which you can find here (https://web.archive.org/web/20250000000000*/https://stack.int.mov/a-reverse-engineers-anatomy-of-the-macos-boot-chain-security-architecture/)), it's pretty clear that what's been happening here is the person used AI to churn out this "writeup", then used the fact it was blatantly wrong to get people who knew how these systems actually worked to correct the post, and then told the AI to incorporate said corrections into the original post.

Let's be clear what's happening: the person is outright baiting people using this AI slop into correcting the post, incorporating said corrections *without attribution to the people who corrected the post* and then took the credit for said corrections silently. This isn't okay, this is a blatant abuse of community goodwill and the benefit of the doubt to fraudulently boost your own credibility and platform, without even a legitimate effort or attempt at doing proper research or fact-checking. (Not even diving into how LLMs are plagiarism laundering machines that yoink real human work and mash it together without any attribution.)

This "writeup" is nothing but of AI slop, and I strongly advise avoiding giving it attention. I'm very disappointed that people, even people I respect quite a bit, are promoting this like it's legitimate without reading it deeper and realizing this is AI slop.

Here are some writeups I *strongly* recommend reading, that have real, human, legitimate research placed into them:

- This fantastic writeup/thesis (https://arxiv.org/abs/2510.09272) by Mortiz Steffin and Dr. Jiska Classen on the GXF-protected portions of iOS (SPTM, TXM, Exclaves/SecureKernel) and how it all makes XNU closer to a true microkernel architecture.
- JJTech's writeup (https://jjtech.dev/reverse-engineering/imessage-explained/) on iMessage and how it worked as of 2023 (yes, 2023 was two years ago, but this writeup is still worth reading regardless)
- Snoolie's writeup on an Apple Archive vulnerability (https://snoolie.gay/blog/CVE-2024-27876), this is a great writeup that goes further in depth on CVE-2024-27876.

@mttaggart @da_667 @cR0w @Dio9sys Isn't that a SIP thing? https://www.rfc-editor.org/rfc/rfc3265

Binary Ninja 5.2 adds support for custom string formats and constant encodings. Instead of wrestling with odd or obfuscated values, you can teach Binja how they work and let the analysis reveal the real content anywhere it appears. This update lays the groundwork for more language aware features coming soon. https://binary.ninja/2025/11/13/binary-ninja-5.2-io.html#custom-strings--constants

The Passenger Seat Developer

https://svnscha.de/posts/the-passenger-seat-developer/

Great (and balanced!) post about the false sense of success during prototyping with LLMs.

RE: https://mastodon.social/@jack_daniel/115599160952274592

Here's the thing about this, if MS can override or ignore Group Policy settings for Copilot, it can do so for anything else and that seems bad.
It seems bad, because it is bad.
Further proof MS can not be trusted.
I say this as a long time Windows user and admin, going back even before my MCSE+I in NT4.

Shout out to people who love ebooks but hate Amazon:

Bookshop.org has started doing eBooks! They have an app! They have classics for free! They have daily 99p deals!

Much excite!

#books #bookstodon

I've uploaded the slides of my recent talk "JS Engine Security in 2025": https://saelo.github.io/presentations/poc_25_js_engine_security_in_2025.pdf. I think there'll also be a recording available at some point (otherwise I can make one as not everything's in the slides).

Fantastic conference as usual, big thanks to the PoC Crew!

Call for articles & art is open for Paged Out! magazine issue #8 - https://pagedout.institute/! (check out the zine if you don't know it - it's free)

As usual, we're looking for 1-page technical articles on topics related to programming, cybersecurity, retro-computing, demoscene, reverse-engineering, CTFs (incl. CTF challenge write-ups), file formats, network protocols, artificial intelligence, and so on. We're also happy to publish articles previously published e.g. on blogs, etc (though in 1-page form of course).

Think about writing something - it's just 1 page, so it's pretty fast to create :)

More info:

https://pagedout.institute/?page=cfp.php

https://pagedout.institute/?page=writing.php

Do I know someone who is (remotely) involved in running the `.hm` domain registry?

📢Call for beta testers!📢
The "Architecture 1901: From zero to QEMU - A Gentle introduction to emulators from the ground up!" course by Antonio Nappa @jeppojeps will begin November 28th. Sign up here: https://forms.gle/LUXaThn4YSYSvk5D7

This course explores the fascinating world of emulation, guiding learners from the fundamentals of CPU design to the internals of QEMU and advanced instrumentation techniques.
 You will start by understanding what emulation truly means—how software can imitate hardware—and progressively build your own 8-bit CPU emulator in Python (SimpleProc-8), extend it with interrupts, I/O, and MMIO, and finally instrument real-world emulators like QEMU.
 The course combines hands-on labs, in-browser exercises, and conceptual lectures to bridge theory and practice, preparing students to tackle topics such as system emulation, hardware-assisted execution, and fuzzing of embedded targets.
By the end, you’ll not only understand how emulators work—you’ll be able to build, modify, and analyze them for research, debugging, and vulnerability discovery.

@azonenberg We also did the D&D in bed thing, but arguably less weird versions (maybe because we were friends, not siblings?) :D

/cc @TarkabarkaHolgy may find the topic fun too :)

@th @typeswitch Does it turn into a virus if you play it backwards?

This is AI slop, sorry for posting it earlier (damn thing fooled me)!

https://stack [.] int [.] mov / a-reverse-engineers-anatomy-of-the-macos-boot-chain-security-architecture/

[RSS] How I Debug Driver Verifier Crashes from Kernel Memory Dumps

https://medium.com/@Debugger/how-i-debug-driver-verifier-crashes-from-kernel-memory-dumps-2e03f35b7731?source=rss-3ba65b326b28------2

A year ago, I saw someone open a book lamp in a bar. It was a pretty expensive product. Since I combine electronics and paper crafting, I had to DIY it and develop an easy-to-use circuit template and instructions for it. This educational project is perfect for libraries. Please #retoot :-)
Template and instructions are available on my website: https://www.voltpaperscissors.com/diybooklamp.
Feel free to ask any questions.
#papercircuit #papercraft #diy #MINT #STEM

imagine living in a world where search engines are so reliable that "let me google that for you" is a common reply to someone asking a question