14 This document describes application framework fundamentals.
15 FCF (Fully Conform to Specification) implementation is still under development.
16 It may happen that current implementation somehow diverges with specifications.
21 The application framework on top of the security framework
22 provides components to install and uninstall applications
23 as well as to run them in a secured environment.
25 The goal of the framework is to manage applications and hide security details
28 For the reasons explained in introduction, it was choose not to reuse Tizen
29 application framework directly, but to rework a new framework inspired from Tizen.
31 fundamentals remain identical: the applications are distributed
32 in a digitally signed container that should match widget specifications
33 normalized by the W3C. This is described by the technical
34 recommendations [widgets] and [widgets-digsig] of the W3 consortium.
36 As today this model allows the distribution of HTML, QML and binary applications
37 but it could be extended to any other class of applications.
39 The management of widget package signatures.
40 Current model is only an initial step, it might be extended in the
41 future to include new feature (ie: incremental delivery).
44 Comparison to other frameworks
45 ------------------------------
53 organization of directory of applications
54 =========================================
56 The main path for applications are: APPDIR/PKGID/VER.
60 - APPDIR is as defined above
61 - PKGID is a directory whose name is the package identifier
62 - VER is the version of the package MAJOR.MINOR
64 The advantage of such an organization is to allow several versions to live together.
65 This is required for multiple reasons (ie: roll back) and to comply with developers habits.
67 Identity of installed files
68 ---------------------------
70 All the files are installed as user "userapp" and group "userapp".
71 All files have rw(x) for user and r-(x) for group and others.
73 This allows any user to read files.
76 labeling the directories of applications
77 -----------------------------------------
83 The data of a user are contain within its directory and are labeled using the application labels
85 Setting Smack rules for the application
86 =======================================
88 For Tizen, the following rules are set by the security manager for each application.
92 System ~PKG~::RO rwxat
94 ~APP~ System::Shared rxl
95 ~APP~ System::Run rwxat
96 ~APP~ System::Log rwxa
103 ~APP~ User::App::Shared rwxat
107 Here, ~PKG~ is the identifier of the package and ~APP~ is the identifier of the application.
109 What user can run an application?
110 =================================
112 Not all user are able to run all applications.
116 [meta-intel]: https://github.com/01org/meta-intel-iot-security "A collection of layers providing security technologies"
117 [widgets]: http://www.w3.org/TR/widgets "Packaged Web Apps"
118 [widgets-digsig]: http://www.w3.org/TR/widgets-digsig "XML Digital Signatures for Widgets"
119 [libxml2]: http://xmlsoft.org/html/index.html "libxml2"
120 [openssl]: https://www.openssl.org "OpenSSL"
121 [xmlsec]: https://www.aleksey.com/xmlsec "XMLSec"
122 [json-c]: https://github.com/json-c/json-c "JSON-c"
123 [d-bus]: http://www.freedesktop.org/wiki/Software/dbus "D-Bus"
124 [libzip]: http://www.nih.at/libzip "libzip"
125 [cmake]: https://cmake.org "CMake"
126 [security-manager]: https://wiki.tizen.org/wiki/Security/Tizen_3.X_Security_Manager "Security-Manager"
127 [app-manifest]: http://www.w3.org/TR/appmanifest "Web App Manifest"
128 [tizen-security]: https://wiki.tizen.org/wiki/Security "Tizen security home page"
129 [tizen-secu-3]: https://wiki.tizen.org/wiki/Security/Tizen_3.X_Overview "Tizen 3 security overview"