Side effect of recent change to more secure defaults like "lanman auth = No" intentionally?

[Guenter Kukkukk]

Am Freitag, 14. September 2007 06:16 schrieb Andrew Bartlett:

> > Sample smbpasswd entry (slightly modified) before first access:
> > gk:1000:EC00EEA187473ED4C2265B23734E0DAC:3A7F56DC5DB01A34FC389A6FB2954BC0:[U          ]:LCT-46E8CFC4:
> > and after:
> > gk:1000:XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX:3A7F56DC5DB01A34FC389A6FB2954BC0:[U          ]:LCT-46E93487:
> 
> Why is the LCT (last change time) in the entry changing?
> 
> Andrew Bartlett
> 

Hi Andrew,

you already asked me on irc, whether the password itself was modified
during the last days,
It was _not_ modified for years - ugly, but true. :-)

True is also, that the LCT is different in my sample 'before first access'
and 'after'.
That was merely a documentation problem, so it's not a true 
'before' --> 'after' regarding a strict time line.
In fact - during debugging - I was trying to get the LM hash back into 
smbpasswd using 'smbpasswd gk', which does not succeed as long as
"lanman auth = No" is active, but is changing LCT. I did some
tries with different lanman auth settings, so LCT is worthless here.

Cheers, Guenter