s3:auth: use data_blob_null instead of data_blob(NULL, 0) in sam_password_ok()

This way it is more explicit that there is no allocated data here
that may leak.

Michael
(cherry picked from commit c9e05e11b152401d63ae9b8b40c717d0bd3d0646)

diff --git a/source3/auth/auth_sam.c b/source3/auth/auth_sam.c
index 42ede641412c76febe24858ec7a5e0e81a457157..a9f1600d1778483b44f8fe91d21372d46faa4b6d 100644 (file)
--- a/source3/auth/auth_sam.c
+++ b/source3/auth/auth_sam.c
@@ -47,8 +47,8 @@ static NTSTATUS sam_password_ok(const struct auth_context *auth_context,
        struct samr_Password *client_nt_hash = NULL;
        const char *username = pdb_get_username(sampass);
 
-       *user_sess_key = data_blob(NULL, 0);
-       *lm_sess_key = data_blob(NULL, 0);
+       *user_sess_key = data_blob_null;
+       *lm_sess_key = data_blob_null;
 
        acct_ctrl = pdb_get_acct_ctrl(sampass);
        if (acct_ctrl & ACB_PWNOTREQ) {