> -----Original Message----- > From: Łukasz Stelmach [mailto:[email protected]] > Sent: Tuesday, November 19, 2013 12:12 AM > To: Schaufler, Casey > Cc: Tizen Dev > Subject: Re: [Dev] The 3 Smack domain status > > It was <2013-11-18 pon 17:04>, when Schaufler, Casey wrote: > >> -----Original Message----- > >> From: Łukasz Stelmach [mailto:[email protected]] > >> Sent: Monday, November 18, 2013 12:38 AM > >> To: Schaufler, Casey > >> > >> It was <2013-11-15 pią 22:56>, when Schaufler, Casey wrote: > >>> The User domain: > >>> > >>> The user experience is provided by the display manager and the > >>> application launcher. They have been set to run in the User domain. > >>> The appropriate manifest files will be updated as part of the merge. > >>> Because these services are managed by systemd the User domain is > >>> granted access to the System::Run label and hence the /run directory. > >> > >> What about $XDG_RUNTIME_DIR (/run/usr/$UID)? Shouldn't these > >> directories be labeled with something like User::Run? > > > > That will depend on what talks to the user bus. > > What does user bus have to do it? /run/user/$UID is a place where user > processes can put their "non-essential runtime files and other file > objects"[1]. These can be for example API sockets.
If user processes are the only ones using the directory it should get relabeled to "User", as it is local to the User domain. If, on the other hand, you have System services creating those API sockets, the current System::Run label is correct. The only case where you'd want User::Run is if the User domain is providing services to a peer domain. > > At this point all user processes are running with the label User. When > > we start dividing the User domain into peer domains you're probably > > right. We'll grill that fish when we've caught it. > > OK. > > >>> The /run directory is a resource managed by systemd and must not be > >>> used as a repository for other data. > >> > >> <nitpicking> > >> This isn't exactly true. UDisks2 for example mounts removable media > >> under /run/media. > >> </nitpicking> > > > > That puts them on separate filesystems, with their own smack > > configuration. It would probably have been better to say "/run > > filesystem" than "/run directory". > > I mean that systemd isn't the only process that manages content (creates > directories) on the "/run filesystem". I'm not sure that I'd call most of what goes on in /run outside of systemd "management", but you're correct. > [1] http://standards.freedesktop.org/basedir-spec/basedir-spec-latest.html > [2] > http://cgit.freedesktop.org/udisks/tree/src/udiskslinuxfilesystem.c?id=bc5e > 358e4ad686a00e8df29a42aabb6332000d98#n890 > -- > Łukasz Stelmach > Samsung R&D Institute Poland > Samsung Electronics _______________________________________________ Dev mailing list [email protected] https://lists.tizen.org/listinfo/dev
