A Kernel Hacker Meets Fuchsia OS
a13xp0p0v.github.io
A Kernel Hacker Meets Fuchsia OS
1–10 of 296 posts
Re: A Kernel Hacker Meets Fuchsia OS
#2Very nice right up on how unfinished and insecure Fuchsia is as a result of it being so unfinished.
Re: A Kernel Hacker Meets Fuchsia OS
#3[deleted]
Re: A Kernel Hacker Meets Fuchsia OS
#4Very nice right up on how unfinished and insecure Fuchsia is as a result of it being so unfinished.
Was that your takeaway from reading it, or something else?
Re: A Kernel Hacker Meets Fuchsia OS
#5Very nice right up on how unfinished and insecure Fuchsia is as a result of it being so unfinished.
Better than being insecure by design, I would think.
Re: A Kernel Hacker Meets Fuchsia OS
#6Re: A Kernel Hacker Meets Fuchsia OS
#7Very nice right up on how unfinished and insecure Fuchsia is as a result of it being so unfinished.
The word you were looking for is _writeup_.
Re: A Kernel Hacker Meets Fuchsia OS
#8Very nice right up on how unfinished and insecure Fuchsia is as a result of it being so unfinished.
FTA: But to simplify my first security experiment with Fuchsia, I decided to disable SMAP and SMEP in the script starting QEMU and create the fake vtable in my exploit in the userspace
I don’t see them re-enabling it later, so yes, they found security problems, but they didn’t show a complete attack, either.
Re: A Kernel Hacker Meets Fuchsia OS
#9Re: A Kernel Hacker Meets Fuchsia OS
#10Would be nice to see something like this on seL4 (in some OS like Sculpt, for example)