On Wed, 2013-10-16 at 10:58 -0500, Steve M. Robbins wrote:
> On Tue, Oct 15, 2013 at 11:44:47PM -0700, Steve Langasek wrote:
> > Control: tags -1 moreinfo
> >
> > Hi Steve,
> >
> > > For the benefit of anyone else who got stuck: I ran "smbpasswd -a" to
> > > create
> > > each user/passwd in the new password database.
> >
> > What do you mean by "new password database"? The tdbsam backend has been
> > the default backend for years, and this hasn't changed in 4.0. The file has
> > moved location on the filesystem, but the maintainer scripts take care of
> > moving the file on upgrade. Were you using a non-default configuration for
> > your samba password handling previously?
>
> Good question. Perhaps I was. I set it up so long ago, I can't
> remember what I did but I do know that it has generally worked across
> upgrades over the years. But not this one.
>
> The old password file was /etc/samba/smbpasswd which seems to be ASCII while
> the new one is in /var/lib:
>
> steve@riemann{~}sudo file /etc/samba/smbpasswd /var/lib/samba/passdb.tdb
> /etc/samba/smbpasswd: ASCII text
> /var/lib/samba/passdb.tdb: TDB database version 6, little-endian hash size
> 131 bytes
>
>
> If it helps: I had been using SWAT to configure samba.What was the old version you upgraded from? The default has been tdbsam for quite some time now. Can you show us your smb.conf? I was assuming the bug here is that the automatic migration between smb.conf backends was lost, which would permit an upgrade from a very old version to one using tdbsam by default, but I can't find any evidence in the packaging source tree for that. Steve, how was this handled at the time? Thanks, Andrew Bartlett -- Andrew Bartlett http://samba.org/~abartlet/ Authentication Developer, Samba Team http://samba.org Samba Developer, Catalyst IT http://catalyst.net.nz
signature.asc
Description: This is a digitally signed message part
