Nicolas: > On Tue, Aug 18, 2009 at 05:44:43PM -0500, Brian Cameron wrote: >> The GDM co-maintainers did not like the above proposal. They >> disagreed strongly with the idea of including or excluding users >> based on whether they have a face image defined. Remember the >> face browser shows users who do not have a face image defined with >> a generic "face" image. >> >> Instead, they propose the following: >> >> Add back the GDM Include and Exclude configuration options so that >> the sysadmin can define which users should be included in the face >> browser even if they have not previously logged in and which users >> should be always excluded. This is how the old GDM also worked. >> Will this satisfy the opt-in/opt-out requirements? > > Provided that it is possible for the installer(s) and user add tools to > edit the configuration, yes. If not then... no.
If the installer runs as a user which can modify the GDM configuration file /etc/gdm/custom.conf with 644 root:sys permissions, then it can. I'd think the installer would be able to do this. In fact there was no reason that the installer couldn't have had this sort of integration with the old GDM 2.20, since it also supported a Face Browser. This isn't really a new GDM feature, though the Face Browser does work better in the new GDM. > BTW, the cache did have one nice side-effect: you could see recently > logged in, not just opted-in users, in the face browser. This would be the behavior if the new IncludeAll setting is false. In this case ck-history is used to get the list of recently logged in users to display. This would be the default setting on Solaris. If the setting is changed to true, then GDM will use the heuristics to add local users to the system. The Include/Exclude options will simply filter the output of ck-history so the users will still show up in recently logged in order when IncludeAll is false. Brian
