It seems that “the community” consists of three separate groups of people:
- the people who loudly demand features
- the developers who loudly debate the ethic, moral, technical religious impacts if the features demanded by 1. would be implemented
- the small group of developers who watch 1. and 2. and at some point say “Oh for crying out loud. What a noise over 5 lines of code.”
As an example, look at the discussion over the feature request in kmail where someone wants kmail to be able to remove attachments from mails.
As another example, look at this one. Some people would like to see single-sign-on in KDE4. The discussion was long and loud.
And, if you Google a bit, you find that the wallet daemon has had the required dbus call since KDE 4.4.2, for crying out loud!
Just that noone has bothered to point a finger at the required pam modules and helpers.
I’ve packaged them for openSUSE, get them from my OBS project and configure them as described in the readme files included in the packages, and you have single sign on.
Note: single sign on only happens if you actually enter a password on login. The typical suse setup with an user session starting automatically on boot can’t work with this.
Note: this seems to work only for local useraccounts, but not in a NIS environment.
Packages such as Likewise allow one to join a domain using your own domain username/password – just as one can do from a Windows workstation. However, openSUSE’s implementation seems to require domain Administrator login. Unfortunately, in office networks where Windows is the dominant OS (99% of them!), it is nigh impossible to get the Admin to help you join your Linux box to the domain — even if Linux is officially supported (like in my company).
Is there a way to do this without domain admin login?