#cheribsd — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #cheribsd, aggregated by home.social.
-
I commend this #podcast episode to the house: https://softwareengineeringdaily.com/2026/03/31/freebsd-with-john-baldwin/
-
I commend this #podcast episode to the house: https://softwareengineeringdaily.com/2026/03/31/freebsd-with-john-baldwin/
-
I commend this #podcast episode to the house: https://softwareengineeringdaily.com/2026/03/31/freebsd-with-john-baldwin/
-
I commend this #podcast episode to the house: https://softwareengineeringdaily.com/2026/03/31/freebsd-with-john-baldwin/
-
I commend this #podcast episode to the house: https://softwareengineeringdaily.com/2026/03/31/freebsd-with-john-baldwin/
-
Arm Morello
https://www.youtube.com/watch?v=2zi28s83exk
– overheard during day one of the FreeBSD Developer Summit at BSDCan 2024.
-
Arm Morello
https://www.youtube.com/watch?v=2zi28s83exk
– overheard during day one of the FreeBSD Developer Summit at BSDCan 2024.
-
Arm Morello
https://www.youtube.com/watch?v=2zi28s83exk
– overheard during day one of the FreeBSD Developer Summit at BSDCan 2024.
-
Arm Morello
https://www.youtube.com/watch?v=2zi28s83exk
– overheard during day one of the FreeBSD Developer Summit at BSDCan 2024.
-
Arm Morello
https://www.youtube.com/watch?v=2zi28s83exk
– overheard during day one of the FreeBSD Developer Summit at BSDCan 2024.
-
The ‘security revenue addiction’ section in this WIRED article really struck home. I remember attending a talk by a new security VP at Microsoft who was talking about this revenue growth in after-market security products as if it were a good thing that customers needed to pay more to fix preventable issues in core products. It was then that I realised how hard it would be for Microsoft to push #CHERI. The cost of porting the Windows ecosystem across was large but the dent that it would put in that revenue stream was much larger.
This is a problem for incumbents (see: the innovator’s dilemma). If you already have 90% of the market, most changes will, at best, do nothing to your market share. If you have 5% then you need only a small number of switchers from the dominant platform do double your market share.
With the mature state of #CheriBSD (#FreeBSD for CHERI platforms), I think there’s a bit opportunity for another vendor to provide a CHERI solution and then pass the ‘must have two suppliers’ rule for requirements in government procurement.
-
The ‘security revenue addiction’ section in this WIRED article really struck home. I remember attending a talk by a new security VP at Microsoft who was talking about this revenue growth in after-market security products as if it were a good thing that customers needed to pay more to fix preventable issues in core products. It was then that I realised how hard it would be for Microsoft to push #CHERI. The cost of porting the Windows ecosystem across was large but the dent that it would put in that revenue stream was much larger.
This is a problem for incumbents (see: the innovator’s dilemma). If you already have 90% of the market, most changes will, at best, do nothing to your market share. If you have 5% then you need only a small number of switchers from the dominant platform do double your market share.
With the mature state of #CheriBSD (#FreeBSD for CHERI platforms), I think there’s a bit opportunity for another vendor to provide a CHERI solution and then pass the ‘must have two suppliers’ rule for requirements in government procurement.
-
The ‘security revenue addiction’ section in this WIRED article really struck home. I remember attending a talk by a new security VP at Microsoft who was talking about this revenue growth in after-market security products as if it were a good thing that customers needed to pay more to fix preventable issues in core products. It was then that I realised how hard it would be for Microsoft to push #CHERI. The cost of porting the Windows ecosystem across was large but the dent that it would put in that revenue stream was much larger.
This is a problem for incumbents (see: the innovator’s dilemma). If you already have 90% of the market, most changes will, at best, do nothing to your market share. If you have 5% then you need only a small number of switchers from the dominant platform do double your market share.
With the mature state of #CheriBSD (#FreeBSD for CHERI platforms), I think there’s a bit opportunity for another vendor to provide a CHERI solution and then pass the ‘must have two suppliers’ rule for requirements in government procurement.
-
The ‘security revenue addiction’ section in this WIRED article really struck home. I remember attending a talk by a new security VP at Microsoft who was talking about this revenue growth in after-market security products as if it were a good thing that customers needed to pay more to fix preventable issues in core products. It was then that I realised how hard it would be for Microsoft to push #CHERI. The cost of porting the Windows ecosystem across was large but the dent that it would put in that revenue stream was much larger.
This is a problem for incumbents (see: the innovator’s dilemma). If you already have 90% of the market, most changes will, at best, do nothing to your market share. If you have 5% then you need only a small number of switchers from the dominant platform do double your market share.
With the mature state of #CheriBSD (#FreeBSD for CHERI platforms), I think there’s a bit opportunity for another vendor to provide a CHERI solution and then pass the ‘must have two suppliers’ rule for requirements in government procurement.
-
The ‘security revenue addiction’ section in this WIRED article really struck home. I remember attending a talk by a new security VP at Microsoft who was talking about this revenue growth in after-market security products as if it were a good thing that customers needed to pay more to fix preventable issues in core products. It was then that I realised how hard it would be for Microsoft to push #CHERI. The cost of porting the Windows ecosystem across was large but the dent that it would put in that revenue stream was much larger.
This is a problem for incumbents (see: the innovator’s dilemma). If you already have 90% of the market, most changes will, at best, do nothing to your market share. If you have 5% then you need only a small number of switchers from the dominant platform do double your market share.
With the mature state of #CheriBSD (#FreeBSD for CHERI platforms), I think there’s a bit opportunity for another vendor to provide a CHERI solution and then pass the ‘must have two suppliers’ rule for requirements in government procurement.
-
#CHERI all the way down (or up)!
Or: The worlds most overengineered (but secure!) lightswitch!
The #EclipseMosquitto MQTT server, running as a pure-capability #CheriBSD pure-capability binary on a Morello system, acting as the server component for an IoT system. Pure-capability programs run with hardware-enforced memory safety, with every pointer represented with a CHERI capability so even single-byte out-of-bounds errors will trap. The kernel is also built in this mode.
I accidentally booted with the wrong kernel, so we don't have temporal safety on the server yet.
On the client, we have a #CHERIoT system, where everything has spatial and temporal memory safety. This connects to the CheriBSD server and sends the state of the switches via MQTT and sets the LEDs on the board based on subscriptions to MQTT events. This all happens over TLS 1.2 with ECDSA.
The network stack is compartmentalised. This demo includes 9 isolated compartments as well as several shared libraries, on a board with 256 KiB of (code + data) RAM, including a memory-safe shared heap.
-
#CHERI all the way down (or up)!
Or: The worlds most overengineered (but secure!) lightswitch!
The #EclipseMosquitto MQTT server, running as a pure-capability #CheriBSD pure-capability binary on a Morello system, acting as the server component for an IoT system. Pure-capability programs run with hardware-enforced memory safety, with every pointer represented with a CHERI capability so even single-byte out-of-bounds errors will trap. The kernel is also built in this mode.
I accidentally booted with the wrong kernel, so we don't have temporal safety on the server yet.
On the client, we have a #CHERIoT system, where everything has spatial and temporal memory safety. This connects to the CheriBSD server and sends the state of the switches via MQTT and sets the LEDs on the board based on subscriptions to MQTT events. This all happens over TLS 1.2 with ECDSA.
The network stack is compartmentalised. This demo includes 9 isolated compartments as well as several shared libraries, on a board with 256 KiB of (code + data) RAM, including a memory-safe shared heap.
-
#CHERI all the way down (or up)!
Or: The worlds most overengineered (but secure!) lightswitch!
The #EclipseMosquitto MQTT server, running as a pure-capability #CheriBSD pure-capability binary on a Morello system, acting as the server component for an IoT system. Pure-capability programs run with hardware-enforced memory safety, with every pointer represented with a CHERI capability so even single-byte out-of-bounds errors will trap. The kernel is also built in this mode.
I accidentally booted with the wrong kernel, so we don't have temporal safety on the server yet.
On the client, we have a #CHERIoT system, where everything has spatial and temporal memory safety. This connects to the CheriBSD server and sends the state of the switches via MQTT and sets the LEDs on the board based on subscriptions to MQTT events. This all happens over TLS 1.2 with ECDSA.
The network stack is compartmentalised. This demo includes 9 isolated compartments as well as several shared libraries, on a board with 256 KiB of (code + data) RAM, including a memory-safe shared heap.
-
#CHERI all the way down (or up)!
Or: The worlds most overengineered (but secure!) lightswitch!
The #EclipseMosquitto MQTT server, running as a pure-capability #CheriBSD pure-capability binary on a Morello system, acting as the server component for an IoT system. Pure-capability programs run with hardware-enforced memory safety, with every pointer represented with a CHERI capability so even single-byte out-of-bounds errors will trap. The kernel is also built in this mode.
I accidentally booted with the wrong kernel, so we don't have temporal safety on the server yet.
On the client, we have a #CHERIoT system, where everything has spatial and temporal memory safety. This connects to the CheriBSD server and sends the state of the switches via MQTT and sets the LEDs on the board based on subscriptions to MQTT events. This all happens over TLS 1.2 with ECDSA.
The network stack is compartmentalised. This demo includes 9 isolated compartments as well as several shared libraries, on a board with 256 KiB of (code + data) RAM, including a memory-safe shared heap.
-
#CHERI all the way down (or up)!
Or: The worlds most overengineered (but secure!) lightswitch!
The #EclipseMosquitto MQTT server, running as a pure-capability #CheriBSD pure-capability binary on a Morello system, acting as the server component for an IoT system. Pure-capability programs run with hardware-enforced memory safety, with every pointer represented with a CHERI capability so even single-byte out-of-bounds errors will trap. The kernel is also built in this mode.
I accidentally booted with the wrong kernel, so we don't have temporal safety on the server yet.
On the client, we have a #CHERIoT system, where everything has spatial and temporal memory safety. This connects to the CheriBSD server and sends the state of the switches via MQTT and sets the LEDs on the board based on subscriptions to MQTT events. This all happens over TLS 1.2 with ECDSA.
The network stack is compartmentalised. This demo includes 9 isolated compartments as well as several shared libraries, on a board with 256 KiB of (code + data) RAM, including a memory-safe shared heap.
-
Ed Maste, Senior Director of Technology at The FreeBSD Foundation, discusses the rapidly-evolving interplay between hardware, cybersecurity, open source, and instruction set architectures.
<https://hackernoon.com/the-cybersecurity-battle-has-come-to-hardware>
#RISCV #Arm #Morello #CHERI #CheriBSD #hardware #ISA #security #cybersecurity #University #Cambridge #SRI #FreeBSD
-
Ed Maste, Senior Director of Technology at The FreeBSD Foundation, discusses the rapidly-evolving interplay between hardware, cybersecurity, open source, and instruction set architectures.
<https://hackernoon.com/the-cybersecurity-battle-has-come-to-hardware>
#RISCV #Arm #Morello #CHERI #CheriBSD #hardware #ISA #security #cybersecurity #University #Cambridge #SRI #FreeBSD
-
Ed Maste, Senior Director of Technology at The FreeBSD Foundation, discusses the rapidly-evolving interplay between hardware, cybersecurity, open source, and instruction set architectures.
<https://hackernoon.com/the-cybersecurity-battle-has-come-to-hardware>
#RISCV #Arm #Morello #CHERI #CheriBSD #hardware #ISA #security #cybersecurity #University #Cambridge #SRI #FreeBSD
-
Ed Maste, Senior Director of Technology at The FreeBSD Foundation, discusses the rapidly-evolving interplay between hardware, cybersecurity, open source, and instruction set architectures.
<https://hackernoon.com/the-cybersecurity-battle-has-come-to-hardware>
#RISCV #Arm #Morello #CHERI #CheriBSD #hardware #ISA #security #cybersecurity #University #Cambridge #SRI #FreeBSD
-
Ed Maste, Senior Director of Technology at The FreeBSD Foundation, discusses the rapidly-evolving interplay between hardware, cybersecurity, open source, and instruction set architectures.
<https://hackernoon.com/the-cybersecurity-battle-has-come-to-hardware>
#RISCV #Arm #Morello #CHERI #CheriBSD #hardware #ISA #security #cybersecurity #University #Cambridge #SRI #FreeBSD
-
Update: this week I saw @dexter post about #CheriBSD/CherIoT, @whitequark & @mntmn chat about #wasm on firmware/embedded, & @rsc post about #unix v6 wasm: https://research.swtch.com/v6/
So apparently I have an assembler problem domain I’m interested in. Now I’ve just got to find an itch worth scratching, and get enough experience to find something interesting to do with a novel asm.
-
Update: this week I saw @dexter post about #CheriBSD/CherIoT, @whitequark & @mntmn chat about #wasm on firmware/embedded, & @rsc post about #unix v6 wasm: https://research.swtch.com/v6/
So apparently I have an assembler problem domain I’m interested in. Now I’ve just got to find an itch worth scratching, and get enough experience to find something interesting to do with a novel asm.
-
Update: this week I saw @dexter post about #CheriBSD/CherIoT, @whitequark & @mntmn chat about #wasm on firmware/embedded, & @rsc post about #unix v6 wasm: https://research.swtch.com/v6/
So apparently I have an assembler problem domain I’m interested in. Now I’ve just got to find an itch worth scratching, and get enough experience to find something interesting to do with a novel asm.
-
Update: this week I saw @dexter post about #CheriBSD/CherIoT, @whitequark & @mntmn chat about #wasm on firmware/embedded, & @rsc post about #unix v6 wasm: https://research.swtch.com/v6/
So apparently I have an assembler problem domain I’m interested in. Now I’ve just got to find an itch worth scratching, and get enough experience to find something interesting to do with a novel asm.
-
Update: this week I saw @dexter post about #CheriBSD/CherIoT, @whitequark & @mntmn chat about #wasm on firmware/embedded, & @rsc post about #unix v6 wasm: https://research.swtch.com/v6/
So apparently I have an assembler problem domain I’m interested in. Now I’ve just got to find an itch worth scratching, and get enough experience to find something interesting to do with a novel asm.
-
-
-
-
-
Just finished reading an article about #CheriBSD in the #FreeBSD journal:
https://freebsdfoundation.org/wp-content/uploads/2023/05/CheriBSD_ports.pdf
Obviously, I want now an #Arm Morello system for added security :-) But at least I'd love to know the status of syslog-ng. Is it already aarch64c, or needs legacy support to run?
