Kernel Developer Guide
- Overview
- Considerations for Developing a Kernel
- Kernel & Features Specification (KF)
- Kernel Creation
- Kernel APIs
- Runtime Environment
- Kernel UID
- Sandboxed Application Lifecycle
- Define a Security Policy
- Resource Manager
- Kernel and Features Communication
- Multi-Sandbox Enabled Libraries
- Setup a KF Testsuite
- Kernel Linking
- Application Linking
- FAQ
- Glossary
- Security & Sandboxing
- How is Applications’ code isolated from the rest of the device code?
- How do we protect against malicious code injection in the App?
- Can you outline what the Application integrity check does?
- Are the Apps Signed?
- I want to open app development to 3rd parties. How can I control API access from Apps?
- Any recommendation about app deployment?
- What kind of isolation exists between applications?
- Inter-App Communication & APIs
- Scheduling & Resource Management
- App Deployment & Compatibility
- How is Application compatibility ensured to prevent runtime linking errors?
- What happens if a
.fois found to be incompatible? Is there an event or programmatic way to detect this? - My Kernel exposes the
widgetlibrary as a Kernel API. My application has a dependency on thewidgetlibrary. Will the code of the library be embedded into my app? - Can I pre-install applications in my device firmware?
- Can the Kernel access the app’s resources before they are started?
- How to access application metadata before installing it? (e.g. name, version, description)
- Can I stop an Application at any time?
- Can applications be used across different manufacturers?
