-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

FACORAT Fabrice wrote:
> Le dim 03/08/2003 à 19:53, Dave Cotton a écrit :
>
>>Just to show a non negative approach, I went into MCC and enabled mdkkdm
>>and it was installed, as I had kdm set up _not_ to show icons and to use
>>the last login, I must say mdkkdm picked up this config.

Well, mdkkdm should follow all configurations in
/usr/share/config/kdm/kdmrc that are valid (taking into account some
features which may not make sense I guess in some mdkkdm configurations).

>>So the problem for me, from the last time I updated and allowed mdkkdm,
>>was that it defaulted to showing all the logins, a ridiculous situation
>>on a machine with a large number of users. This machine has standard
>>security level.
>

Is the fact that you run a machine with a large number of users in
standard security level not the ridiculous situation?

> IMHO when using NIS/LDAP/Samba auth, all dm should default too "no users
> list"

Is it not better to default to msec 4 in any network auth setup? This
gets you a few other features which may be useful (restrictions on su etc).

IMHO, a good default sudo config would also help in these situations (ie
allow member of adm group to 'sudo /sbin/service' with (without?) password.

Regards,
Buchan

- --
|--------------Another happy Mandrake Club member--------------|
Buchan Milne                Mechanical Engineer, Network Manager
Cellphone * Work            +27 82 472 2231 * +27 21 8828820x202
Stellenbosch Automotive Engineering         http://www.cae.co.za
GPG Key                   http://ranger.dnsalias.com/bgmilne.asc
1024D/60D204A7 2919 E232 5610 A038 87B1 72D6 AC92 BA50 60D2 04A7
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.2 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQE/LkTPrJK6UGDSBKcRAnCrAJ0UZrAjQNm2642BKeWHls1dJacP9gCeLCw2
lSVekZJkTDZjxmbgEnYwkGg=
=oOBX
-----END PGP SIGNATURE-----

******************************************************************
Please click on http://www.cae.co.za/disclaimer.htm to read our
e-mail disclaimer or send an e-mail to [EMAIL PROTECTED] for a copy.
******************************************************************

Reply via email to