Linked by Thom Holwerda on Wed 27th Jun 2007 18:59 UTC, submitted by John Nilsson
Microsoft The Singularity team at Microsoft has recently published a new article concerning their research OS. It is a concise introduction to the Singularity project. It summarizes research in Singularity 1.0 and highlights ongoing research for Singularity 2.0.
Thread beginning with comment 251606
To view parent comment, click here.
To read all comments associated with this story, please click here.
Morin
Member since:
2005-12-31

> The problem I see, and it's a major problem, is that
> there is nothing but the MSIL Runtime preventing me
> from grabbing memory anywhere I want it. The PDF
> even states that this is possible given a bug in the
> Sing# runtime. From what it looks like to me, this
> includes inside the kernel.

With traditional OSes, the problem, and it's a major problem, is that there is nothing but the hardware protection preventing me from grabbing memory anywhere I want it. Bugs in the hardware protection are going to make the OS vulnerable just as bugs in the MSIL do.

> If I can write anywhere in the system without
> triggering hardware exceptions that is IMHO a very
> bad thing.

Which is why this situation cannot occur, bugs in the MSIL or hardware protection aside. With "managed code" as it is called, there is no sequence of instructions that could write to arbitrary memory locations (due to the unforgeability of arbitrary pointers).

Reply Parent Score: 2