-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

On 01/25/2014 11:52 PM, Roger Leigh wrote:
> On Sat, Jan 25, 2014 at 08:09:03PM +0100, Thomas Bechtold wrote:
>> I created a clean chroot with debootstrap for sid amd64. I try to
>> use this chroot env together with schroot to run autopkgtests. 
>> When I login to the chroot and then logout, I get the following
>> error:
>> 
>> E: PAM error: No module specific data is present
>> 
>> Attached is the complete log with debugging information. I
>> already tried to build schroot by myself and just ignored the
>> thrown error from lib/sbuild/auth/pam.cc when pam_close_session()
>> fails. If I ignore the error, everything works as expected but I
>> guess that's not the correct resolution for the problem.
> 
> No; we can't afford to ignore the error.  Depending upon what
> happens after this point, it might well be a security issue or
> cause dataloss depending upon what PAM has been configured to do,
> though this is probably unlikely.  But it would certainly be
> against the spirit of the PAM API to ignore it.
> 
> I think it's most likely that the PAM error is external to
> schroot; schroot just asks PAM to start, stop, authenticate etc.
> and does not really have any input into what it does.  I would
> suspect this error is the fault of a single PAM module.  If it
> would be possible to identify which is at fault, we can look into
> it in more detail.
> 
> You could try commenting out the various lines of
> /etc/pam.d.schroot and also in the referenced generic files if they
> don't help.  PAM might have some means of enabling debugging
> messages here, but I don't know for sure.

I commented some pam modules and the problem comes from the ssh
module. If I comment "session optional        pam_ssh.so" from
/etc/pam.d/common-session or just remove the package libpam-ssh,
everything works fine.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1
Comment: Using GnuPG with Icedove - http://www.enigmail.net/

iQIcBAEBCAAGBQJS5MqwAAoJEELuctrCcxmtlYAP/00n6pj43Z+u/kkVLnH5Pz2e
ObAJQo0TkMFF4Ao4hiKfbNYSAhyyxScoefl5cdSdOir6MYzqCA3kvdKuLfnv3IEE
U5Fiw+mHbLPqeoGgMAbWokKFzLt2xEoPC8lQ2ubWVfCekz+S4wtOvxqMHfUGsl9o
oQiESCnaBHpXw2ryzmKQr3IdO5K/jfdyTLV4deJH/GfhnXl/RzcnV6sZo3dapXdB
vC+mLm2W5OPbHJnrXPihZbU5YFgNoI1vz0zEfQYFOGYY47gNCb+GQy1veTB4K+lr
TTqCzmDAiXuvtpDor5KYntB8gJnOiqQOLekSvY+j9y5i11dDfzqDEAXtMZetqwev
aTBO/v29xeeFCtC+wUCjcy5ZDaxeh4ZTdrDnBwN588GSaga0Ve0ft1w73edU/Ljy
R7yuYM3UbEzdKXzMtjMbDFbvdylSSwF3NXBcMFvNTvqmlrd7lU+BxbH3nj5SbxVz
nixi/9iVzg1OwJu3te+Y23vkYSmEBsNyRwtf1oUOF8ul23DHL20XPyh2/B+jjrdK
bU8UM/LGOM0N3v3oRZ0hWQT+mhEISBjjxFT6ObQqCzGTY0QX0Qtwl6b8v2e2Ag2K
F5GoVS4LMpfy4lufanCo8VvKP50MmdQ94kNONtYhIPjg6fO6E6tyejabOOzPb7re
64MFxFbTyMtU0uXf4hV+
=znq8
-----END PGP SIGNATURE-----


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Reply via email to