Rainer,
The issue is, that the default setup uses /etc/shadow for ssh, ftp, samba & al. It is an extra effort to setup and maintain passwords in different files. Apache has a different file by default.
Let this compare to Lotus Notes. When you define a user there, the system prompts you for two different passwords. One to be used for the ID-file that contains the private key (and is never transmitted anywhere from the local system) and another one, that is used for HTTP basic authentication. This is easy to understand for novice admins and little extra effort.
So, my on my whishlist to Easter Bunny: 1. Suse will add an installation/config option to make a separate pw-db for samba and proftpd (and maybe others) 2. Suse will add a list of passwords for different packages into yast user management.
Rainer
Hmmm. I agree that these two points are desirable to implement, but it is
also too complex to do. One of the side effects will be that people
complain that authentication doesn't work (because the wrong file is
active) and people comlain that SuSE doesn't keep to the standards.
We can't afford these two points in the long run. Also, modifying the
daemons/packages takes time and manpower...
It's nice project, though. Would you want to hack and maintain a set
of patches that resolve these problems in a few packages?
Thanks,
Roman.
--
- -
| Roman Drahtmüller