PAM Integration - Revision history

Andre Schramm: /* Packages dropped */

2013-04-15T14:07:10Z

Packages dropped

← Older revision		Revision as of 14:07, 15 April 2013
Line 1,128:		Line 1,128:
	* libuser: pam is libuser's build dependency, so remove it too.		* libuser: pam is libuser's build dependency, so remove it too.
	* The busybox login has a option to use pam, but we use tinylogin's login right now (tinylogin also provides the su command)		* The busybox login has a option to use pam, but we use tinylogin's login right now (tinylogin also provides the su command)
			* If you want to use pam_limits in /etc/pam.d/login, you have to add VIRTUAL-RUNTIME_login_manager = "busybox" to your distro config in order to replace tinylogin with busybox, as tinylogin does not provide PAM capabilites; also make sure that "login" and "PAM" are enabled in your busybox config
	* gettext only has a example "hello-c++-kde" use pam under source code directory, and it doen't be compiled and only copied to destination. So omit gettext.		* gettext only has a example "hello-c++-kde" use pam under source code directory, and it doen't be compiled and only copied to destination. So omit gettext.
	* sysvinit has a patch contrib/notify-pam-dead.patch for /sbin/init to use pam, but the whole contrib directory didn't take part in compilation. Drop it.		* sysvinit has a patch contrib/notify-pam-dead.patch for /sbin/init to use pam, but the whole contrib directory didn't take part in compilation. Drop it.

2012-10-26T02:57:28Z

Build image

← Older revision		Revision as of 02:57, 26 October 2012
Line 4:		Line 4:
	== Build image ==		== Build image ==
	If you want to enable pam support, please add "pam" to DISTRO_FEATURES by add one line to build/conf/local.conf		If you want to enable pam support, please add "pam" to DISTRO_FEATURES by add one line to build/conf/local.conf
	DISTRO_FEATURES_append = " pam"		DISTRO_FEATURES_append += " pam"

	Then add the packages to sato by apply this patch		Then add the packages to sato by apply this patch

2012-02-22T02:57:56Z

newusers

2011-09-29T09:20:27Z

PAM Unit Tests

← Older revision		Revision as of 09:20, 29 September 2011
Line 1,074:		Line 1,074:

	== PAM Unit Tests==		== PAM Unit Tests==
	We use unit test cases provided by libpam itself, a subdirectory with name "xtests" under libpam source code. Right now we spit it as a sub-package libpam-xtests.		We use unit test cases provided by libpam itself, a subdirectory with name "xtests" under libpam source code. Right now we spit it as a sub-package libpam-xtests. After "bitbake libpam" you can find it under deploy directory. And it requires some packages:
			pam-plugin-debug
			pam-plugin-access
			pam-plugin-cracklib
			pam-plugin-time
			pam-plugin-pwhistory
			pam-plugin-succeed-if

	All test cases are:		All test cases are:

2011-08-25T06:37:58Z

PAM Unit Tests

← Older revision		Revision as of 06:37, 25 August 2011
Line 1,087:		Line 1,087:

	On build machine after install package libpam-xtests, go to the xtexts directory and run tests		On build machine after install package libpam-xtests, go to the xtexts directory and run tests
			export ALL_TESTS="tst-pam_dispatch1 tst-pam_dispatch2 tst-pam_dispatch3 \
			tst-pam_dispatch4 tst-pam_dispatch5 \
			tst-pam_cracklib1 tst-pam_cracklib2 \
			tst-pam_unix1 tst-pam_unix2 tst-pam_unix3 tst-pam_unix4 \
			tst-pam_access1 tst-pam_access2 tst-pam_access3 \
			tst-pam_access4 tst-pam_limits1 tst-pam_succeed_if1 \
			tst-pam_group1 tst-pam_authfail tst-pam_authsucceed \
			tst-pam_pwhistory1 tst-pam_time1"
	cd /usr/share/Linux-PAM/xtests		cd /usr/share/Linux-PAM/xtests
	./run-xtests.sh `pwd` ALL_TESTS ~~# replace All_TESTS with the tests listed above~~		./run-xtests.sh `pwd` $ALL_TESTS

	If you want to run sigle test case, just run (take tst-pam_time1 for example)		If you want to run sigle test case, just run (take tst-pam_time1 for example)

2011-08-25T06:27:49Z

move the "log files" ahead

← Older revision		Revision as of 06:27, 25 August 2011
Line 29:		Line 29:

	Then you can build the core-image-sato and test these packages on the sato image.		Then you can build the core-image-sato and test these packages on the sato image.

			== Log files ==
			We can test the packages both on core-image-sato and core-image-lsb
			* on sato, edit the /etc/syslog.conf, set
			DESTINATION="file"
			then you can check the log via /var/log/message
			* on lsb, the log information are send to /var/log/auth.log

	== Common configure files ==		== Common configure files ==
Line 1,096:		Line 1,103:

	== Notes ==		== Notes ==
	~~=== image to run tests ===~~
	~~We test the packages both on core-image-sato and core-image-lsb~~
	* on sato, edit the /etc/syslog.conf, set
	~~DESTINATION="file"~~
	~~then you can check the log via /var/log/message~~
	* on lsb, the log information are send to /var/log/auth.log

	=== Packages dropped ===		=== Packages dropped ===

2011-08-25T05:55:35Z

← Older revision		Revision as of 05:55, 25 August 2011
Line 859:		Line 859:
	==== su ====		==== su ====
	/etc/pam.d/su		/etc/pam.d/su
	auth sufficient pam_rootok.so		auth sufficient pam_rootok.so
	session required pam_env.so readenv=1		session required pam_env.so readenv=1
	session required pam_env.so readenv=1 envfile=/etc/default/locale		session required pam_env.so readenv=1 envfile=/etc/default/locale
	session optional pam_mail.so nopen		session optional pam_mail.so nopen
	auth include common-auth		auth include common-auth
	account include common-account		account include common-account

2011-07-29T09:31:11Z

Build image

← Older revision		Revision as of 09:31, 29 July 2011
Line 6:		Line 6:
	DISTRO_FEATURES_append = " pam"		DISTRO_FEATURES_append = " pam"

	Then add the packages to by apply this patch		Then add the packages to sato by apply this patch
	diff --git a/meta/recipes-sato/tasks/task-core-x11-sato.bb b/meta/recipes-sato/tasks/task-core-x11-sato.bb		diff --git a/meta/recipes-sato/tasks/task-core-x11-sato.bb b/meta/recipes-sato/tasks/task-core-x11-sato.bb
	index 43b24d2..ea9fa14 100644		index 43b24d2..ea9fa14 100644

2011-07-29T09:30:40Z

Build image

← Older revision		Revision as of 09:30, 29 July 2011
Line 3:		Line 3:

	== Build image ==		== Build image ==
			If you want to enable pam support, please add "pam" to DISTRO_FEATURES by add one line to build/conf/local.conf
			DISTRO_FEATURES_append = " pam"

			Then add the packages to by apply this patch
			diff --git a/meta/recipes-sato/tasks/task-core-x11-sato.bb b/meta/recipes-sato/tasks/task-core-x11-sato.bb
			index 43b24d2..ea9fa14 100644
			--- a/meta/recipes-sato/tasks/task-core-x11-sato.bb
			+++ b/meta/recipes-sato/tasks/task-core-x11-sato.bb
			@@ -31,4 +31,11 @@ RDEPENDS_task-core-x11-sato = "\
			gtk-sato-engine \
			gthumb \
			x11vnc \
			- ${NETWORK_MANAGER}"
			+ ${NETWORK_MANAGER} \
			+ \
			+ at \
			+ cronie \
			+ cups \
			+ polkit \
			+ screen \
			+ shadow \
			+ sudo "

			openssh is conflict with dropbear. If you want to test openssh please uninstall dropbear first and then install openssh.

			Then you can build the core-image-sato and test these packages on the sato image.

	== Common configure files ==		== Common configure files ==

2011-07-29T09:19:22Z

← Older revision		Revision as of 09:19, 29 July 2011
Line 1:		Line 1:
	== Motivation ==		== Motivation ==
	For Yocto 1.1 we are working to ensure that PAM (Pluggable Authentication Module) support is consistent and enabled in recipes where it is applicable.		For Yocto 1.1 we are working to ensure that PAM (Pluggable Authentication Module) support is consistent and enabled in recipes where it is applicable.

			== Build image ==

	== Common configure files ==		== Common configure files ==