PAM test results on Progeny CL Core and Progeny Debian
I have run the lsb-test-pam 0.9.7-1 test suite on Progeny's
Componentized Linux Core 1.3 and on Progeny Debian 2.0 Alpha 1. I am
currently attempting to make the full results available, and will follow
up when that is complete.
For reference, both products are based on Debian's next release
("sarge"). CL Core 1.3 is based on an older version of sarge, and is
certified to the LSB 1.3 standard. Progeny Debian is closer to sarge's
current state.
For CL Core, here are the most interesting results:
/tset/LSB.pam/testcases/pam_acct_mgmt/pam_acct_mgmt 4 FAIL
/tset/LSB.pam/testcases/pam_acct_mgmt/pam_acct_mgmt 5 FAIL
/tset/LSB.pam/testcases/pam_chauthtok/pam_chauthtok 8 UNREPORTED
/tset/LSB.pam/testcases/pam_close_session/pam_close_session 2 FAIL
/tset/LSB.pam/testcases/pam_open_session/pam_open_session 3 FAIL
For Progeny Debian:
/tset/LSB.pam/testcases/pam_acct_mgmt/pam_acct_mgmt 4 FAIL
/tset/LSB.pam/testcases/pam_acct_mgmt/pam_acct_mgmt 5 FAIL
/tset/LSB.pam/testcases/pam_authenticate/pam_authenticate 6 FAIL
/tset/LSB.pam/testcases/pam_close_session/pam_close_session 2 FAIL
/tset/LSB.pam/testcases/pam_open_session/pam_open_session 3 FAIL
Analysis reveals that the four test failures in common failed for the
same reasons. The pam_*_session tests all succeeded when they should
have returned PAM_SESSION_ERR, and the pam_acct_mgmt tests failed
("Authentication failure") when they should have succeeded.
The pam_chauthtok failure in CL 1.3 was caused by a manual abort of the
test after it had been allowed to run for nearly two hours. I would
imagine this is the result of some problem with the installation
procedure (which is very unorthodox), and should probably be considered
anomalous if it doesn't also appear in Progeny Debian.
The pam_authenticate failure in Progeny Debian was reported in the test
as follows:
pam_authenticate returned User not known to the underlying
authentication module
It was expected to return PAM_AUTHINFO_UNAVAIL
Reply to: