User Tools

Site Tools


agl-roadmap

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
agl-roadmap [2018/07/12 13:59]
waltminer [From Connectivity EG]
agl-roadmap [2018/07/18 13:51] (current)
waltminer [From App FW and Security EG]
Line 28: Line 28:
      * {{:​ff-partial-yellow.png?​nolink&​75|FF-PARTIAL}} Distinction between platform services (e.g., nfc, telephone) and user services that run inside a user context (e.g., media player and lightmedia scanner) ​      * {{:​ff-partial-yellow.png?​nolink&​75|FF-PARTIAL}} Distinction between platform services (e.g., nfc, telephone) and user services that run inside a user context (e.g., media player and lightmedia scanner) ​
      * Changes necessary at binder level for V2C (SSL transport)      * Changes necessary at binder level for V2C (SSL transport)
-     * Application signing and installation mechanism+     ​* ​{{:​ff-partial-yellow.png?​nolink&​75|FF-PARTIAL}} ​Application signing and installation mechanism 
 +       * {{:​ff-ready-brightgreen.png?​nolink&​75|FF-READY}} Mechanism for checking signature is in place.  
 +       * Require all apps to be signed in GG 
 +       * Developer workflow is needed for managing keys 
 +       * Development mode and Production mode for app management ​
      * Secure applications running on a remote device such as mobile phone or tablet that are rendered on the IVI system.      * Secure applications running on a remote device such as mobile phone or tablet that are rendered on the IVI system.
      * {{:​ff-ready-brightgreen.png?​nolink&​75|FF-READY}} Binder APIv3 (enable dynamic APIs)      * {{:​ff-ready-brightgreen.png?​nolink&​75|FF-READY}} Binder APIv3 (enable dynamic APIs)
Line 53: Line 57:
          * Improved development cycle (based on partial Widget installation)          * Improved development cycle (based on partial Widget installation)
          * First step to support package manager for SDKs (Yomo)          * First step to support package manager for SDKs (Yomo)
 +
 +     * **GG Priorities for App FW**
 +       * Complete application lifecycle definition to prepare for all apps moving to new app lifecycle in HH
 +       * HTML5 app support as necessary
 +       * Multi-user use case
 +       * API for abstraction of hardware mechanism for signing apps, packages, etc. 
 +       * Headless/ Telematics use case
 +       * Unit testing for app framework
 +       * Modularization of application-framework-main to improve key management, maintainability and building across multiple platforms. ​
 +         * Split off the keys from the App FW. Currently are [[https://​git.automotivelinux.org/​src/​app-framework-main/​tree/​certs | here]]
 +         * Allow keys to be changed by the device developers - git repo and recipe for keys
 +         * Library (or binding) to plug in key management to the app FW. 
 +         * Reference implementation will use the file system as the key store. Can be swapped for a trusted environment by a device creator at a later time. 
 +         * Sign at build time in AGL CI system with a check at run time 
  
 ==== From Graphics EG ==== ==== From Graphics EG ====
agl-roadmap.1531403978.txt.gz · Last modified: 2018/07/12 13:59 by waltminer