Maemo security
(→Is there a diagram showing the security framework and components?) |
(→Is there a diagram showing the security framework and components?) |
||
| Line 16: | Line 16: | ||
===Is there a diagram showing the security framework and components?=== | ===Is there a diagram showing the security framework and components?=== | ||
| - | See [http://www.slideshare.net/peterschneider/maemo-6-platform-security slide] # | + | See [http://www.slideshare.net/peterschneider/maemo-6-platform-security slide] #2, #5 and #9 of Elena Reshetova's [[Maemo Summit 2009/Day 3#Maemo_Platform_Security:_Principles_and_Concepts | Maemo Summit presentation]] |
===What is "Open Mode" and can it be revoked remotely?=== | ===What is "Open Mode" and can it be revoked remotely?=== | ||
Revision as of 16:40, 15 October 2009
At the Maemo Summit 2009, Nokia shared a great deal of information about the security mechanisms that would be available and/or mandated in upcoming platforms.
- Slides
- Video (TBC)
The concepts outlined include well established favourites in the OSS world (like privilege management) as well as some that are rather less well regarded - such as relatives of the Trusted Computing Platform and DRM.
Inevitably there will be a significant amount of interest and concern about how this affects the open nature of the Maemo platform.
This page is intended to capture community questions (and, eventually I hope, Nokia's answers) about these issues.
Initially please add questions to the discussion page and once they've been refined and consolidated, we'll add them onto this page.
Some examples:
Is there a diagram showing the security framework and components?
See slide #2, #5 and #9 of Elena Reshetova's Maemo Summit presentation
What is "Open Mode" and can it be revoked remotely?
"Open" mode is when an unsigned kernel has been booted. Disabling it remotely would, presumably, require a change to the bootloader. See slide #??? --Jaffa 11:36, 13 October 2009 (UTC)