Hi, > I recently noticed that when runing pbuilder build, it fails as > it calls su internally. I tracked this down to su wanting a password, > and futher tracked this to pam using nullok_secure, wheras nullok works, > I guess we aren't coming from a secure tty.
I don't seem to be able to reproduce this particular problem; what's causing this? Hmmm: http://archives.neohapsis.com/archives/pam-list/2005-08/0014.html So, /etc/securetty somewhere (possibly inside the chroot) is not what pam wants. I have one problem in that pbuilder will feed it with < /dev/null, and that's not a tty, according to tty command, $ tty < /dev/null not a tty regards, junichi -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
