[Meego-security-discussion] Arbitrary 3rd Party Code
Michael Leibowitz
michael.leibowitz at intel.com
Thu Apr 7 08:27:45 PDT 2011
On Wed, 2011-04-06 at 12:27 -0700, Ryan Ware wrote:
> Since Arjan announced changes in the security direction for MeeGo, I've had
> a large number of questions regarding what the new architecture is going to
> look like. I want to emphasize that this direction isn't set in stone. I
> would like feedback from people in the community to determine if this fits
> their needs and if not, it what ways does it fall short. This will be
> significantly different from MSSF, but I believe it fits our current
> security requirements and is simpler to implement. Keep in mind that this
> is an overview. I will be generating a detailed architecture over the next
> couple of weeks. There are also some areas that I will not yet touch on
> because they haven't been grounded yet.
>
> To start, I'm intending to break things up conceptually into a Trusted Side
> and Untrusted Side.
The solution is proposed before the problem and assumptions are clearly
articulated.
Cheers
--
Michael Leibowitz <michael.leibowitz at intel.com>
More information about the MeeGo-security-discussion
mailing list