|
|
| (11 intermediate revisions by 7 users not shown) |
| Line 1: |
Line 1: |
| Suggested questions:
| | #REDIRECT [[Talk:Maemo security]] |
| | |
| ===Is there a diagram showing the security framework and components?===
| |
| There were some diagrams in the presentation - can we see them.
| |
| | |
| ===What is "Open Mode" and can it be revoked remotely?===
| |
| Is that the right terminology?
| |
| Essentially can Nokia reach out the the 2nd stage bootloader and tell it to stop running unsigned kernels.
| |
| Maybe this should be 2 questions.
| |
| | |
| ===How easy is it to switch between Open and Closed modes?===
| |
| | |
| ===How granular is the encryption?===
| |
| If my app creates content in the closed mode can I see it in open mode?
| |
| | |
| ===Can open applications use the privilege mechanisms in the Open and Closed modes?===
| |
| | |
| ===Can open applications use the DRM encryption mechanisms in the Open and Closed modes?===
| |
| I can see that this could be useful. Maybe.
| |
| | |
| ===Will community extensions to the kernel (modules) be permitted in Open/Closed modes?===
| |
| I can't see how - which leads to the question: How do community 'enhancements' to the kernel get adopted?
| |
| | |
| ===Is there any GPLv3 software impacted?===
| |
| Please have a license discussion somewhere and let us know when you have consensus.
| |
| What is Nokias position? Peter made a statement at the talk - can someone transcribe it and/or get Nokia to clarify.
| |
