Earlier quoted context omitted.
Better than being insecure by design, I would think.
Insecure is insecure. Or did you mean unfixably insecure?
Parent means infixably and/or intentionally insecure.
A Kernel Hacker Meets Fuchsia OS
21–30 of 296 posts
Re: A Kernel Hacker Meets Fuchsia OS
#22Earlier quoted context omitted.
I right a lot less now then I did as a kid, so maybe it’s about just staying sharp
You rays a good point!
Ah, this remains me of a classique in this field: https://youtu.be/OonDPGwAyfQ
Re: A Kernel Hacker Meets Fuchsia OS
#23The great thing about Fuchsia is it's like a Google version of Plan 9.
The bad thing about Fuchsia is it's like a Google version of Plan 9.
Re: A Kernel Hacker Meets Fuchsia OS
#24The people who work on fuchsia are very good engineers - I’ve worked with many of them in person. But the project itself has always been a staff retention project. It only existed to keep said engineers from going to a competitor. I don’t know how any understanding of fuchsia is possible without this crucial fact
Re: A Kernel Hacker Meets Fuchsia OS
#25The great thing about Fuchsia is it's like a Google version of Plan 9. The bad thing about Fuchsia is it's like a Google version of Plan 9.
The bad thing about Fuchsiais that it's a Google product.
They may decide to kill it next week and switch to XNU or symbian or templeos and no one would be surprised.
Re: A Kernel Hacker Meets Fuchsia OS
#26The people who work on fuchsia are very good engineers - I’ve worked with many of them in person. But the project itself has always been a staff retention project. It only existed to keep said engineers from going to a competitor. I don’t know how any understanding of fuchsia is possible without this crucial fact
> It only existed to keep said engineers from going to a competitor.
Who in this day, and hour tries to make an OS as a commercial product?
Re: A Kernel Hacker Meets Fuchsia OS
#27My takeaway from the article is that Fuchsia exposes a capability-based interface externally, but uses the old kind of privilege-checking inside the kernel. Once a single sloppy check was found, the game was over: a privilege escalation and planting of arbitrary code into the kernel followed.
Did I miss anything?
Re: A Kernel Hacker Meets Fuchsia OS
#28Would be nice to see something like this on seL4 (in some OS like Sculpt, for example)
That would be too hard, it's a kernel that's actually developed with security in mind and is subject to active research (e.g. by DARPA).
If you try using sel4 in a project, you soon realise it is extremely limited and not at all useful for general purpose computers
Re: A Kernel Hacker Meets Fuchsia OS
#29Very nice right up on how unfinished and insecure Fuchsia is as a result of it being so unfinished.
"How insecure" a surprising conclusion based on a single exploit.