s3:libsmb: no need to reset capabilities in cli_session_setup_lanman2()

This is only used cli->protocol < PROTOCOL_NT1, in which case
cli_negprot_done() has already reset cli->capabilities.

metze

diff --git a/source3/libsmb/cliconnect.c b/source3/libsmb/cliconnect.c
index 1f222f88fd68bb50b1e55904b45b6084727d4c08..f162e7e3056807c509a35d2c0a3008616fae4c18 100644 (file)
--- a/source3/libsmb/cliconnect.c
+++ b/source3/libsmb/cliconnect.c
@@ -133,16 +133,6 @@ static struct tevent_req *cli_session_setup_lanman2_send(
        state->user = user;
        vwv = state->vwv;
 
-       /*
-        * LANMAN servers predate NT status codes and Unicode and
-        * ignore those smb flags so we must disable the corresponding
-        * default capabilities that would otherwise cause the Unicode
-        * and NT Status flags to be set (and even returned by the
-        * server)
-        */
-
-       cli->capabilities &= ~(CAP_UNICODE | CAP_STATUS32);
-
        /*
         * if in share level security then don't send a password now
         */