David Chisnall (*Now with 50% more sarcasm!*)

@david_chisnall@infosec.exchange
2.7K Followers
83 Following
6.8K Posts

I am Director of System Architecture at SCI Semiconductor and a Visiting Researcher at the University of Cambridge Computer Laboratory. I remain actively involved in the #CHERI project, where I led the early language / compiler strand of the research, and am the maintainer of the #CHERIoT Platform.

I was on the FreeBSD Core Team for two terms, have been an LLVM developer since 2008, am the author of the GNUstep Objective-C runtime (libobjc2 and associated clang support), and am responsible for libcxxrt and the BSD-licensed device tree compiler.

Opinions expressed by me are not necessarily opinions. In all probability they are random ramblings and should be ignored. Failure to ignore may result in severe boredom and / or confusion. Shake well before opening. Keep refrigerated.

Warning: May contain greater than the recommended daily allowance of sarcasm.

No license, implied or explicit, is granted to use any of my posts for training AI models.

as usual, leave it to the FSF to have the most nonsense contrarian take, like "using a JS based tool to block LLMs is malware".

their slide into incoherence and irrelevance knows no bounds.

"America has been vaccinating people for fifty years. If vaccines caused autism, America would have trains, okay? We would have so many trains." - Jon Allen
Why did you write a new RTOS for CHERIoT? (Part 2)

Back in October last year, I wrote a bit about why we wrote a new RTOS for CHERIoT. Reading that again, I realise that it had a lot of high-level concepts but missed out on some detail. This time, I wanted to take a closer look at some CHERIoT RTOS features to show that being able to rely on CHERI lets us build them in fundamentally different ways to other systems.

#CHERIoT

Why did you write a new RTOS for CHERIoT? (Part 2)

Back in October last year, I wrote a bit about why we wrote a new RTOS for CHERIoT. Reading that again, I realise that it had a lot of high-level concepts but missed out on some detail. This time, I wanted to take a closer look at some CHERIoT RTOS features to show that being able to rely on CHERI lets us build them in fundamentally different ways to other systems.

CHERIoT Platform

still laughing at the xlibre guy not knowing that ^ is xor and c doesn't have a builtin exponentiation operator

this is the kind of thing we learned when we were, idk, 16?

My wife points out that, although I am very sarcastic person, I am always serious when I use the word 'fabulous'.
I realised my previous post about why we wrote a new RTOS for #CHERIoT was light on details. The core reason is at the end of the new post: We don't want to build a system that is secure, where people can then layer insecure things on top, we want to build the core that enables you to build secure systems. And that requires rethinking a lot of core OS abstractions with usability and security as core requirements. We can't do that by retrofitting CHERI to an existing system.
Why did you write a new RTOS for CHERIoT? (Part 2)

Back in October last year, I wrote a bit about why we wrote a new RTOS for CHERIoT. Reading that again, I realise that it had a lot of high-level concepts but missed out on some detail. This time, I wanted to take a closer look at some CHERIoT RTOS features to show that being able to rely on CHERI lets us build them in fundamentally different ways to other systems.

CHERIoT Platform
Nice to see that my faculty has at last caught up with my little Royal Society stunt.
a blog post by my friend eevee which is, y’know, preaching to the choir about exactly what you think, but. yeah. https://eev.ee/blog/2025/07/03/the-rise-of-whatever/
The rise of Whatever

This was originally titled “I miss when computers were fun”. But in the course of writing it, I discovered that there is a reason computers became less fun, a dark thread woven through a number of events in recent history. Let me back up a bit.

Copy files between your host and jails with ease using bastille jcp. No need to
mount or exec—just push or pull directly.

Bastille 1.0 is tried, tested and available soon!

#BastilleBSD #FreeBSD

I need adult supervision because,-
×
Strong Password Policy 101
Edit: for bonus points it messes with your OCD. There's a method to the madness
@beyondmachines1
The "closing" strong is missing a /
Therefore, it can't be accepted 😜
@realn2s that's intentional 🤡
so hackers will try to close the strong and fail login!
@beyondmachines1
😂
Inconceivable!

@realn2s When you have three locks on your door and leave one unlocked.

When burglars tamper with the locks they unlock two and lock one.

@beyondmachines1 @realn2s I can just imagine trying to remember this...

"Let's see, did I intentionally not close the <strong> tag? Or was it the <body> tag? Or the <html> tag? Wait, did I include an <html> tag?"

@beyondmachines1 that certainly was a bold move.
@cjust i'm sure pun not intended
@beyondmachines1 I tend to post a lot of puns - with the intentions of making people laugh. Unfortunately, a friend of mine took a random sampling of 10 of my most recent ones, and sadly not one pun in ten did.
@beyondmachines1 @9x0rg Error: non-closed strong tag
@beyondmachines1 it's also cool that it allows for an italic password or maybe even a BLINK password!
@beyondmachines1 My eye twitches at the unclosed <strong>, but that makes it secure for exactly the same reason that misspellings in otherwise easy-to-remember words made passwords that kept us all safe in the 1990s.
@beyondmachines1 Password makes a body strong

@beyondmachines1,

the “strongness” is leaking 

@beyondmachines1 the HTML is improperly formatted. Embarrassing 😳
@beyondmachines1
don't forget to close the strong tag!
@beyondmachines1 Your <strong> is missing a closing tag. :P

@GrahamDowns @beyondmachines1 Oh, man. What rotten luck.

This kind of password should actually be pretty good, I think. It's long, it draws on a large character set, it's hard to guess, yet it's easy to remember.

Unless it includes a typo.

@GrahamDowns intentional. There's a method to the madness
@beyondmachines1 @GrahamDowns It's so strong that the strength leaks out into everything else!
@beyondmachines1 ngl if this wasn't posted as a meme online this wouldn't even be such a bad password. It is easy to remember and hard to brute force. Also (at least before it become a meme) very unlikely to be within anyones dictionary either.

@agowa338 @beyondmachines1 The irony is probably nothing will take it because it doesn't have mixed case letters or any numbers.

You could create an almost infinite number of huge variations like this and all would be memorable while being super hard to actually guess -- and none would be accepted by most password policies.

https://xkcd.com/936/

Password Strength

xkcd

@beyondmachines1

Did it say it was strong? I do not see any numbers.

@beyondmachines1 @film_girl oh this is perfect, and yes it really does hit my OCD
@beyondmachines1 ERROR: password needs to contain a number.
@beyondmachines1 I’d forget that the second isn’t