Displaying 2 results from an estimated 2 matches for "0x0x564e841a9da0".
2019 May 31
0
Inconsistency with LANMAN1 and Samba 4.9
...(min password
length), returning 0
tdb(/var/lib/samba/account_policy.tdb): tdb_transaction_start: nesting 1
check lock order 1 for /var/lib/samba/account_policy.tdb
lock order: 1:/var/lib/samba/account_policy.tdb 2:<none> 3:<none>
Locking key 6D696E2070617373776F
Allocated locked data 0x0x564e841a9da0
Unlocking key 6D696E2070617373776F
release lock order 1 for /var/lib/samba/account_policy.tdb
lock order: 1:<none> 2:<none> 3:<none>
account_policy_set: name: min password length, value: 5
account_policy_get: tdb_fetch_uint32_t failed for type 2 (password
history), returning 0
td...
2019 May 31
2
Inconsistency with LANMAN1 and Samba 4.9
On Fri, 2019-05-31 at 11:40 -0700, Jeremy Allison via samba wrote:
> On Fri, May 31, 2019 at 07:09:44PM +0200, Andreas Reichel wrote:
> > > > When adding me as the user with 'smbpasswd -a andreas', and entering a password,
> > > > no LANMAN hash is generated. The generated smbpasswd entry always contains 32 X as the first hash.
> > > >
> > >