Editing Talk:Maemo security
Warning: You are not logged in.
Your IP address will be recorded in this page's edit history.
The edit can be undone.
Please check the comparison below to verify that this is what you want to do, and then save the changes below to finish undoing the edit.
Latest revision | Your text | ||
Line 47: | Line 47: | ||
=== How does closed mode affect on-device debugging? === | === How does closed mode affect on-device debugging? === | ||
- | + | For example, will ptrace(2) still work (eg gdb, strace & ltrace)? Will we be able to produce code dumps? | |
--[[User:elena_r|elena_r]] 09:00, 28 October 2009 (UTC):For security reasons the idea is that a developer should be able to debug its own code (application), but should not be able to assign a debugger to another process. Of course, the memory dumps, for example of the kernel memory, should be restricted, too. This is valid for the "normal mode". For the "open mode" one should be able to do everything. | --[[User:elena_r|elena_r]] 09:00, 28 October 2009 (UTC):For security reasons the idea is that a developer should be able to debug its own code (application), but should not be able to assign a debugger to another process. Of course, the memory dumps, for example of the kernel memory, should be restricted, too. This is valid for the "normal mode". For the "open mode" one should be able to do everything. |
Learn more about Contributing to the wiki.