On Mon, 2013-05-13 at 14:24 +0300, Pekka L.J. Jalkanen wrote: > > Any ideas how to resolve this problem? > > No comments, it seems. > > I can see that even if this is a bug in Samba it would be really hard to > reproduce. But it's really frustrating too, because if the > authentication isn't reliable I sort of have to keep the Windows DC around. > > So if somebody would have an enlightened suggestion what to do, I'd be > grateful. > > The only idea I'm having myself would be to recreate the machine > accounts of the computers in question, but that'd be just a shot in the > dark, and if the problem lies within the user accounts instead, that > wouldn't help.
G'Day, I'm sorry I haven't been able to get back to you. The issue is the same for all of these accounts. We simply have a password encoded in a format that we do not correctly parse. The 00 20 stuff is literally some unicode space (ie the spacebar, yes!) padding that is in this structure. I need to get both and encrypted copy of the data and some time to work over it, so we can correct this issue in our IDL. Andrew Bartlett -- Andrew Bartlett http://samba.org/~abartlet/ Authentication Developer, Samba Team http://samba.org -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba