Registry Segfault after krb5 AD domain logon

[Jelmer Vernooij]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi Andrew,

Andrew Bartlett wrote:

> Now that we do the AD domain logon, we seem to have uncovered a
> segfault in the reg_backend_ldb code. I don't have the backtrace
> to hand, and it may indeed be an issue with the recent ldb_dn
> changes by simo, but I wondered if you might be able to reproduce
> and debug it. I'm all at sea in that code.
>
> The steps to reproduce are simple: - provision - set
> 'gensec:gssapi_krb5=yes' in your smb.conf - join a win2k3 (or
> winXP) client to the new Samba4 ADS domain - perform a domain logon
>
>
>
> During the domain logon, there is a crash in ldb_dn operations in
> that code. The workstation proceeds to login however.

This  has now been fixed - it was caused by a bug in the reg_add_key()
function that accidently set the wrong struct member.. You will now see
a client try to create various registry values under
HKLM\System\CurrentControlSet\Control\Terminal
Server\DefaultUserConfiguration.

Cheers,

Jelmer

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)

iD8DBQFDJ0OXPa9Uoh7vUnYRAjbSAJ92QMf8rVXmSMaihgz+Qhzv/w85EACffPXU
ewuH13nHAPbaLiWM5Nvcwrg=
=Ghj/
-----END PGP SIGNATURE-----