On 11.3.2014 19:22, Stéphane Desneux wrote:
Now, having this consensus raises another question: if I suppose that we
support user deletion (please confirm that assertion !), what happens at
user deletion time ?
Yes, it is part of gumd feature set. As usual, user's home directory (as
defined in /etc/passwd) is deleted when user is deleted.
In addition, for guest users, home directory is deleted every time user
logs off (tlm calls gumd) and created every time guest user is logged in
(tlm calls gumd).
-2- a user has objects or is referenced OUTSIDE his/her homedir (global
database, global files ...) for example the media-server or package manager.
This would need some hooks, such as scripts to deal with. For example
I'm not sure what to do with /var/mail/<user>
Having some files not cleaned up immediately and then ending up
recycling the same userid for a new user is a potential privacy problem.
At some point search indexers (beagle?) used to store indexes outside
user's home (bad bad bad, especially for those having encrypted homes).
Since people can have home directory encrypted with their login
credentials using ecryptfs, storing any user data outside the home
folder is bad idea, however necessary for certain cases like email
inbox. Otherwise you could have mail delivered only while logged in...
If we exclude deletion hooks on gumd, how can we deal with case 2 ? I
mean: what is the link between gumd and the daemons responsible for
those global, user-related resources ?
I can see two ways to add hooks in gumd;
1) synchronous: scripts called at post-create and pre-delete
2) asynchronous: gumd emits a signals on it's system bus interfaces
There are pros and cons on all approaches, with and without hooks, and
scripts and/or signals. But I don't really have (yet) strong opinions on
the matter.
_______________________________________________
Dev mailing list
[email protected]
https://lists.tizen.org/listinfo/dev
