Le 01/12/2014 13:57, jacob travis a écrit :
Hi all,
I'm investigating Multi-User with Tizen 3.0, and I think it’s a little
misleading and inconsistent. I am not sure whether the wiki page is
out of data. So I list things I find, I hope someone can give me some
suggestions.
We will do our best
Tizen 3.0 wiki page is https://wiki.tizen.org/wiki/Tizen_3.0.
Tizen 3.0 Multi-User wiki page is
https://wiki.tizen.org/wiki/Multi-user_Architecture.
Multi-User
presentationshttps://wiki.tizen.org/w/images/0/05/Multi_Users_Presentations_TDC2014_Final.pdf
So far you are good
The multi user use cases can help to understand some of the side effects.
https://wiki.tizen.org/wiki/Multi-user_Architecture#Multi_User_use_cases
*
Multi-User system and Use case for Multi-User.
1.
Muti-User system is the new feature for Tizen 3.0. As the Tizen
3.0 wiki page said, Tizen Common is the base for other profiles,
such as IVI. Tizen has several categories of Multi-User systems,
and what are the categories of Multi-User system? Wiki page only
show me one case, the profile IVI. Is that all for Tizen
Multi-User system? I think it is not enough to detail the
Multi-User system in Tizen 3.0.
Documentation is never enough. When we started with the multi user
requirement in Oct 2013, we had clear requirement for PC/Tablet (since
stopped) and IVI and rather open for Mobile (multi SIM and guest support
mode) and TV (parents, children, family). We started with a clear focus
on multi user as a profile model and with the pressure from the news we
had to seriously focus on Data Privacy. The current model is an
evolution from our starting point and we hope that the current Wiki
reflect where we are today.
1.
2.
Multi-User is the same as Mult-User system, it has no official
standard define. And the listed Multi-User use case is too few.
It’s not enough to descript the Multi-User feature. Such as two
people want to display two different video on Tizen that has one
gstreamer, two audio output and two screen. How does it handle by
Tizen? That means what is the official behavior with more users
want to use more resources and one resource? I don’t find the
standard spec to define the behavior, also the use case is few
that can’t descript the fully Multi-User what the designer want to do.
Multi user is a quite open requirement and we took it with the
understanding of our known use cases an expected evolution. As Tizen
Common is not a final product but is only an enabler to create product
(called verticals in Tizen), some detailed options are out of scope.
For example we have described a mode of multi display, taken from IVI as
it would not make much sense on a TV or a phone. and we explain how the
window can move from one screen to an other. Our goal here was to
demonstrate that Tizen was allowing to break the 1:1 relation between
the Display and the logged user. The difficulty, is that it does not
mean that every profile has to do it.
Remember that the "official" behaviour is defined by a profile not by
Common. In the case of IVI, we can play multiple video (the exact number
depends of the HW, but on IVI IA reference platform 4 is easy to reach,
more requires compromises).
TV may use Picture in Picture and Mobile not allow it at all. It is
their call.
*
Multi_Users_Presentations_TDC2014_Final.pdf,
https://wiki.tizen.org/w/images/0/05/Multi_Users_Presentations_TDC2014_Final.pdf
1.
Page 21, Application Framework,
1.
“Core API should be extended”, the doc said that, and I would
like to know which Core APIs will be extended, dose it already
finished or in progress? Where can I find the details?
Unfortunatly presentations slides desk are not auto updated by
opposition to Wiki pages and the model of SAPI was not finally selected
by the Security group (but still present on old slide decks).
So the core API did not need to change much beside of the AppFW.
see
https://wiki.tizen.org/wiki/Security/TizenSecurityReference
https://wiki.tizen.org/wiki/Multi-user_AMD
1.
1.
2.
Page 23, Resource Services
1.
What resources will be managed and how it was managed by
mult-user case?
If you check the multi user case you will notice that we started with
the network resources.
We also have an active thread on Window management and Package
installation on the mailing list.
1.
1.
2.
Some passivity operation don’t define. For example. Telephone
application is run at different user, once the network side
dial the local number, which telephony UI should be popup, and
who will answer the incoming call? I think Tizen multi-user
will have many confusion like as incoming call, but I don’t
find the official description about it.
No the Tizen Common project is not refining how Profiles will manage
their local conflict. The goal of Common is to enable the mechanism to
present the call to who ever the people in charge of the Phone will have
decided. It might even be a product level decision.
1.
1.
2.
Page 28, Service API
1.
I’m so sorry I don’t find Service API in Tizen 3.0
Architecture diagram. Since that is the key framework for
Multi-user, I am not sure whether someone can update it? what
is the current design? If the current design contain the
Service API, can someone give me a wiki and document about
APIs define?
As said PDF don't update but the wiki was updated.
https://wiki.tizen.org/wiki/Security/SAPI (starts with a "Warning
Obsolete" message)
Please look at the following link to navigate the security model
https://wiki.tizen.org/wiki/Category:Security
In particular you want to read that page.
https://wiki.tizen.org/wiki/Security/Privileges_Study_For_Tizen3
1.
1.
*
Multi user policy,
https://wiki.tizen.org/wiki/Security/Multi_user_policy
1.
“System resources has predefined UID”, Can someone show the list
about the predefined resource UID?
Check here.
https://wiki.tizen.org/wiki/Security/Multi_user_policy#Annex:_User_IDs_policy
1.
2.
“the admin rights erase the device”, dose the admin user only have
the rights to erase the device, right?
*
Multi user security policy
https://wiki.tizen.org/w/images/f/ff/Multi-user-security-policy-march-2014.pdf
3.
This document descript that:
“- default user is the device owner(admin)”.
“Most of files are owned by root except application’s data”
We aim at moving platform services out of root but it's a long quest. We
do them one by one. Currenlty we work on bluetooth deamons. More hand
would be welcome.
“Only default user is able to install & uninstall applications”
Normal user can request App install/update/uninstall but the work is
executed with privileges.
In package application management
https://wiki.tizen.org/wiki/Multi-user_PackageApplicationManagement:
“regular User can only install/uninstall/update application for it
only, and in Tizen 3, by default a user is regular one(i.e, without
particular privileges)”
We have introduced a concept of pivileged user. The first user declared
on a system is always privileged.
There a wrapper to define if a user is privilege or not which by default
is mapped on a special group defined in the platform config meta data
file. Obvious any product could have a more sophisticated to define that
a user is privileged or not.
https://wiki.tizen.org/wiki/Multi-user_Tizen-platform-config
In Multi user policy
https://wiki.tizen.org/wiki/Security/Multi_user_policy:
“the admin rights is install and uninstall applications”. (In basic
principle select)
There have many users, regular user, default user, admin user, root.
What is the difference about those users, and how can I make out those
users. regular user without particular privileges can
install/uninstall/update application for itself with its own
application database. But in other documents, only default user is
able to install/uninstall applications. regular user does not look
like admin user, because regular user has no particular privileges.
The concept is not clear. And how does the admin know which user the
application will be install for?
Words are sometime confusing. We have Linux internal user and the
product user. Internal users (root, bluetooth, ...) are never use to login.
Only product user can login (Bob, Alice, ....). Those are the one who
will install Apps. By Apps we intend Apps from an Apps Store.
4.
Page 5, Service daemon should be able to distinguish user and
enforce access control. if someone want to port the upstream
project to Tizen 3.0, and the upstream is as the Service daemon?
but unfortunately all of currently upstream project don’t support
that, in order to aim the goal, whether the tizen will write a new
related project? Does each upstream project has each Tizen-Related
project?
Simple example of that is BlueZ BlueZ only manages devices and not
user. So if a user pair a device anyone by default can use it.
Same issue with a network connection. In that two example Tizen
middleware must cover for missing feature from upstream projects.
4.
5.
Page 9, Device configuration, only device owner can configure
device. But it’s not aligned with Bluetooth/WiFi Multi-user
requirement. Bluetooth/WiFi requirements are
https://wiki.tizen.org/wiki/Multi-user_Bluetoothand
https://wiki.tizen.org/wiki/Multi-user_WINET. That descript any
user can use the device without device owner configuration, it’s a
little misleading.
See my tow example just before.
Please let me know if you are still confused.
Regards
Dominig
4.
I am not sure if I am understanding this right, and I really sincerely
hope someone can give me some answers.
Thanks
Jacob
_______________________________________________
Dev mailing list
[email protected]
https://lists.tizen.org/listinfo/dev
_______________________________________________
Dev mailing list
[email protected]
https://lists.tizen.org/listinfo/dev
