Mailinglist Archive: opensuse-features (214 mails)
| < Previous | Next > |
[openFATE 310739] Explain how to "disable" pam-config, if manual pam configuration is in place
- From: fate_noreply@xxxxxxx
- Date: Tue, 10 May 2011 13:23:45 +0200 (CEST)
- Message-id: <feature-310739-9@keeper.suse.de>
Feature changed by: Thorsten Kukuk (kukuk)
Feature #310739, revision 9
Title: Explain how to "disable" pam-config, if manual pam configuration
is in place
openSUSE-11.4: Rejected by Thorsten Kukuk (kukuk)
reject date: 2011-03-29 14:07:59
reject reason: too late
Priority
Requester: Mandatory
Requested by: Michael Calmer (mcalmer)
Product Manager: (Novell)
Project Manager: (Novell)
Engineering Manager: (Novell)
Developer: (Novell)
Documentation Editor: (Novell)
Partner organization: openSUSE.org
Description:
pam-config write the files /etc/pam.d/common-***-pc. If a user want to
use its own configuration, he has to remove the symlink from /etc/pam.
d/common-*** to the -pc files and create the common-*** file with his
configuration to prevent pam-config from removing his configuration.
But this is nowhere explained. It should be added to the pam-config
manpage
Additionally we should think about a way to prevent overwriting manual
changes to the service files, if --service is used.
References:
Packages: pam-config
Documentation Impact:
doc feature
Test Case:
- * - Install package
- * - Check that you can still login via graphical frontend and on the
- console
- * - Check that you can still change the password of root and another
+ * Make sure gnome-keyring (espeically /lib{64}
+ /security/pam_gnome_keyring.so) is installed
+ * Install/Update package
+ * Check that you can still login via graphical frontend (gdm, kdm) and
+ on the console
+ * Check that you can still change the password of root and another
local, non-system user
- * - Call "man pam-config", search for "Note", it should be documented
+ * Call "man pam-config", search for "Note", it should be documented
that, if the symlinks don't point to the common-*-pc files, the config
created and modified by pam-config will not be used.
--
openSUSE Feature:
https://features.opensuse.org/310739
Feature #310739, revision 9
Title: Explain how to "disable" pam-config, if manual pam configuration
is in place
openSUSE-11.4: Rejected by Thorsten Kukuk (kukuk)
reject date: 2011-03-29 14:07:59
reject reason: too late
Priority
Requester: Mandatory
Requested by: Michael Calmer (mcalmer)
Product Manager: (Novell)
Project Manager: (Novell)
Engineering Manager: (Novell)
Developer: (Novell)
Documentation Editor: (Novell)
Partner organization: openSUSE.org
Description:
pam-config write the files /etc/pam.d/common-***-pc. If a user want to
use its own configuration, he has to remove the symlink from /etc/pam.
d/common-*** to the -pc files and create the common-*** file with his
configuration to prevent pam-config from removing his configuration.
But this is nowhere explained. It should be added to the pam-config
manpage
Additionally we should think about a way to prevent overwriting manual
changes to the service files, if --service is used.
References:
Packages: pam-config
Documentation Impact:
doc feature
Test Case:
- * - Install package
- * - Check that you can still login via graphical frontend and on the
- console
- * - Check that you can still change the password of root and another
+ * Make sure gnome-keyring (espeically /lib{64}
+ /security/pam_gnome_keyring.so) is installed
+ * Install/Update package
+ * Check that you can still login via graphical frontend (gdm, kdm) and
+ on the console
+ * Check that you can still change the password of root and another
local, non-system user
- * - Call "man pam-config", search for "Note", it should be documented
+ * Call "man pam-config", search for "Note", it should be documented
that, if the symlinks don't point to the common-*-pc files, the config
created and modified by pam-config will not be used.
--
openSUSE Feature:
https://features.opensuse.org/310739
| < Previous | Next > |