On Wed, Jan 21, 2009 at 01:18:53PM -0000, Thierry Carrez wrote:
> It looks related to bug 303458 (and his evil duplicate bug 302092)
> The problem we solved was bug 260687 (libpam-smbpass segfault caused by
> missing /var/lib/samba), but there seem to be a case of /var/lib/samba/
> contents corruption triggering a similar segfault.
What's the basis for claiming that there's a corruption problem? I haven't
seen tdb corruption in samba for many years.
The backtrace in this bug isn't a corruption issue at all; the
get_global_sam_sid() call panics if called by a process that can't create or
read /var/lib/samba/secrets.tdb. The trick is that libpam-smbpass isn't
supposed to call get_global_sam_sid() - so something has changed here.
--
Steve Langasek Give me a lever long enough and a Free OS
Debian Developer to set it on, and I can move the world.
Ubuntu Developer http://www.debian.org/
<email address hidden> <email address hidden>
On Wed, Jan 21, 2009 at 01:18:53PM -0000, Thierry Carrez wrote:
> It looks related to bug 303458 (and his evil duplicate bug 302092)
> The problem we solved was bug 260687 (libpam-smbpass segfault caused by
> missing /var/lib/samba), but there seem to be a case of /var/lib/samba/
> contents corruption triggering a similar segfault.
What's the basis for claiming that there's a corruption problem? I haven't
seen tdb corruption in samba for many years.
The backtrace in this bug isn't a corruption issue at all; the sam_sid( ) call panics if called by a process that can't create or samba/secrets. tdb. The trick is that libpam-smbpass isn't sam_sid( ) - so something has changed here.
get_global_
read /var/lib/
supposed to call get_global_
-- www.debian. org/
Steve Langasek Give me a lever long enough and a Free OS
Debian Developer to set it on, and I can move the world.
Ubuntu Developer http://
<email address hidden> <email address hidden>