Launchpad has imported 4 comments from the remote bug at https://bugs.freedesktop.org/show_bug.cgi?id=41908.
If you reply to an imported comment from within Launchpad, your comment will be sent to the remote bug automatically. Read more about Launchpad's inter-bugtracker facilities at https://help.launchpad.net/InterBugTracking. ------------------------------------------------------------------------ On 2011-10-18T02:54:38+00:00 Robert Ancell wrote: Some users like to filter out certain users from the login screen / user switcher etc. The accounts can still be logged into but are not shown in the GUI. Suggest adding a filter list to AccountsService that does this, perhaps via a "hidden" property on users that should not be shown in a GUI? Reply at: https://bugs.launchpad.net/accountsservice/+bug/857651/comments/8 ------------------------------------------------------------------------ On 2011-11-15T07:09:45+00:00 Robert Ancell wrote: I've been asking around to find out why you'd not want to log into certain accounts. The cases I've head so far are: - System users showing up (e.g. mysql. This seems like an OS bug) - Running a server and having remote logins. There may be accounts that you want to log into to control the server (i.e. over SSH) but not graphically. The last case makes it sound like there potentially should be a per-seat filter. Reply at: https://bugs.launchpad.net/accountsservice/+bug/857651/comments/14 ------------------------------------------------------------------------ On 2011-11-15T10:55:19+00:00 Yoho-ahoy wrote: My use case is a separate account used to develop or to build packages. This provides environmental isolation from the everyday user account and some security - the separate account might have additional system privileges or private keys. For example: Mock - http://fedoraproject.org/wiki/Projects/Mock#Build_User kde development - using (now outdated, i think) advice such as at http://techbase.kde.org/Getting_Started/Build/KDE4_%28bn_IN%29#Create_a_user_account_for_KDE4_development A test account for a very old version of amarok with X forwarding Accounts that can only be accessed by ssh or that don't make sense to log in directly (and are just noise for other users on the machine) but that are otherwise still normal user accounts with home directories and that don't really belong in the system account pid range. Arguably some of this is better handled by virtual machines nowadays; but the separate build user case for mock is, I believe, still strong. And the ssh keys in a separate account case is reasonable, isn't it? Reply at: https://bugs.launchpad.net/accountsservice/+bug/857651/comments/15 ------------------------------------------------------------------------ On 2011-11-15T12:41:44+00:00 Yoho-ahoy wrote: To cut through some of the guff, this use case boils down to - Accounts intended for local ssh logins. They may have privileges or contain secrets not suitable for day-to-day use. and perhaps - Testing accounts that users at the greeter don't need to be bothered with (whether on a single-owner or a shared machine). Not for security, just aesthetics. Reply at: https://bugs.launchpad.net/accountsservice/+bug/857651/comments/16 ** Changed in: accountsservice Status: Unknown => Confirmed ** Changed in: accountsservice Importance: Unknown => Medium -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/857651 Title: Unable to hide users from login screen / user switcher To manage notifications about this bug go to: https://bugs.launchpad.net/accountsservice/+bug/857651/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs