X-Git-Url: https://gerrit.automotivelinux.org/gerrit/gitweb?a=blobdiff_plain;f=docs%2Foverview.md;h=c3627bc133cae95dd1c907a4bcc9ab38cda3cb5f;hb=d3d069b14a028f976c2f99ed2f002f24407c1dfc;hp=d39e66e6b5a9465951579e800a24c39279cd2764;hpb=4a1409460a7c0a5d26fe10b5f84368b3cb8b8b5a;p=src%2Fapp-framework-main.git diff --git a/docs/overview.md b/docs/overview.md index d39e66e..c3627bc 100644 --- a/docs/overview.md +++ b/docs/overview.md @@ -1,6 +1,5 @@ - -AGL framework, overview of the proposal of IoT.bzh -================================================== +AGL framework, IoT.bzh proposal overview +======================================== Foreword -------- @@ -30,7 +29,7 @@ Here is a minimal list of what was needed: - platform/core/appfw/pkgmgr-info - platform/core/appfw/slp-pkgmgr -But this list is complete because many dependencies are hidden. +But this list isn't complete because many dependencies are hidden. Those hidden dependencies are including some common libraries but also many tizen specific sub-components (iniparser, bundle, dlog, libtzplatform-config, db-util, vconf-buxton, ...). @@ -56,15 +55,7 @@ The 3 layers are providing components for: The figure below shows the history of these layers. - - 2014 2015 - Tizen OBS ----------+---------------------------> - \ - \ - Tizen Yocto +---------+--------------> - \ - \ - meta-intel-iot-security +-----------> +![Security_model_history][Security_model_history] We took the decision to use these security layers that provides the basis of the Tizen security, the security framework. @@ -77,7 +68,7 @@ the dependencies and with minor architectural improvements for AGL. These components are **afm-system-daemon** and **afm-user-daemon**. They provides infrastructure for installing, uninstalling, -launching, terminating, stopping and resuming applications in +launching, terminating, pausing and resuming applications in a multi user secure environment. A third component exists in the framework, the binder **afb-daemon**. @@ -96,50 +87,7 @@ The figure below shows the major components of the framework and their interactions going through the following scenario: APPLICATION installs an other application and then launch it. - +-----------------------------------------------------------------------+ - | User | - | ................................ | - | : Smack isolation context : | - | : : ........................... | - | : +-----------------------+ : : Smack isolation context : | - | : | | : : : | - | : | APPLICATION | : : OTHER application : | - | : | | : :.........................: | - | : +-----------+-----------+ : ^ | - | : | : | | - | : |(1),(7) : |(13) | - | : | : | | - | : +-----------v-----------+ : +---------+---------------+ | - | : | binder afb-daemon | : | | | - | : +-----------------------+ : | afm-user-daemon | | - | : | afm-main-binding | : | | | - | : +-----+--------------+--+ : +------^-------+------+---+ | - | :........|..............|......: | | : | - | |(2) |(8) |(10) | : | - | | | | | : | - | | +----v--------------------+---+ | : | - | | | D-Bus session | |(11) :(12) | - | | +-------------------------+---+ | : | - | | | | : | - | | |(9) | : | - | | | | : | - :===========|===================================|=======|======:========: - | | | | : | - | | +---v-------v--+ : | - | +------v-------------+ (3) | | : | - | | D-Bus system +-----------------> CYNARA | : | - | +------+-------------+ | | : | - | | +------^-------+ : | - | |(4) | : | - | | |(6) v | - | +------v--------------+ +---------+---------------+ | - | | | (5) | | | - | | afm-system-daemon +-------------> SECURITY-MANAGER | | - | | | | | | - | +---------------------+ +-------------------------+ | - | | - | System | - +-----------------------------------------------------------------------+ +![AppFW-APP_install_sequences][AppFW-APP_install_sequences] Let follow the sequence of calls: @@ -197,7 +145,7 @@ the components are: * ***afm-system-daemon***: in charge of installing and uninstalling applications. * ***afm-user-daemon***: in charge of listing applications, querying application details, - starting, terminating, stopping, resuming applications and their instances + starting, terminating, pausing, resuming applications and their instances for a given user context. * ***afb-binder***: in charge of serving resources and features through an @@ -219,7 +167,7 @@ to ensure security and privacy. It also includes features of reporting using audit features and by managing logs and alerts. The application framework manages the applications: -installing, uninstalling, starting, stopping, listing ... +installing, uninstalling, starting, pausing, listing ... The application framework uses the security model/framework to ensure the security and the privacy of the applications that @@ -267,11 +215,11 @@ application framework of Tizen as is but used an adaptation of it. The basis is kept identical: the applications are distributed in a digitally signed container that must match the specifications of widgets (web applications). This is described by the technical -recomendations [widgets] and [widgets-digsig] of the W3 consortium. +recommendations [widgets] and [widgets-digsig] of the W3 consortium. This model allows the distribution of HTML, QML and binary applications. -The management of signatures of the widget packages +The management of signatures of the widget packages. This basis is not meant as being rigid and it can be extended in the futur to include for example incremental delivery. @@ -293,4 +241,5 @@ futur to include for example incremental delivery. [tizen-security]: https://wiki.tizen.org/wiki/Security "Tizen security home page" [tizen-secu-3]: https://wiki.tizen.org/wiki/Security/Tizen_3.X_Overview "Tizen 3 security overview" - +[AppFW-APP_install_sequences]: pictures/AppFW-APP_install_sequences.svg +[Security_model_history]: pictures/Security_model_history.svg