[SystemSafety] C for OSs
Robert P. Schaefer
rps at mit.edu
Fri Sep 6 15:34:09 CEST 2019
Hi all,
The problem is a contradiction in what you want to and how to go about doing it.
For security, you have to write OS “kernel” code that controls hardware.
For an OS to be “good”, your kernel code has to be small and fast.
For reasons of hardware access, you need to write assembly language statements to control hardware,
The only small fast language that supports embedding assembly by pragma is C, and C is inherently insecure.
I’m willing to entertain the notion that I am wrong, but, per the quote:
"Very smart people have tried for 50 years, and the solution to the is not reduced to practice."
bob s.
Haystack Observatory, Westford, MA
> On Sep 6, 2019, at 7:54 AM, Peter Bernard Ladkin <ladkin at causalis.com> wrote:
>
> A quote from Tom van Vleck in Risks 31.40 today:
>
> "It seems clear that trying to write secure operating systems in C does not
> work. Very smart people have tried for 50 years, and the solution to the
> problem is not reduced to practice. "
>
> PBL
>
> Prof. Peter Bernard Ladkin, Bielefeld, Germany
> MoreInCommon
> Je suis Charlie
> Tel+msg +49 (0)521 880 7319 www.rvs-bi.de
>
>
>
>
>
> _______________________________________________
> The System Safety Mailing List
> systemsafety at TechFak.Uni-Bielefeld.DE
> Manage your subscription: https://lists.techfak.uni-bielefeld.de/mailman/listinfo/systemsafety
More information about the systemsafety
mailing list