ntlmssp.idl: don't generate python bindings for ntlmssp_NTLM_RESPONSE and ntlmssp_LM_...

ntlmssp_NTLM_RESPONSE and NTLM_RESPONSE will both result in
"ntlmssp.NTLM_RESPONSE".

The same applies to ntlmssp_LM_RESPONSE and LM_RESPONSE.

Signed-off-by: Stefan Metzmacher <metze@samba.org>
Reviewed-by: Günther Deschner <gd@samba.org>
Autobuild-User(master): Stefan Metzmacher <metze@samba.org>
Autobuild-Date(master): Thu Oct 13 21:56:27 CEST 2016 on sn-devel-144

diff --git a/librpc/idl/ntlmssp.idl b/librpc/idl/ntlmssp.idl
index f041e32d548a52224035789f2a31a9aa4879a315..6b228869f90247073900e4b315cb1c2ec0950350 100644 (file)
--- a/librpc/idl/ntlmssp.idl
+++ b/librpc/idl/ntlmssp.idl
@@ -207,7 +207,7 @@ interface ntlmssp
                uint8 ChallengeFromClient[8];
        } LMv2_RESPONSE;
 
-       typedef [nodiscriminant] union {
+       typedef [nopython,nodiscriminant] union {
                [case(24)] LM_RESPONSE v1;
                [default];
        } ntlmssp_LM_RESPONSE;
@@ -238,7 +238,7 @@ interface ntlmssp
                NTLMv2_CLIENT_CHALLENGE Challenge;
        } NTLMv2_RESPONSE;
 
-       typedef [public,nodiscriminant] union {
+       typedef [public,nopython,nodiscriminant] union {
                [case(0)] ;
                [case(0x18)] NTLM_RESPONSE v1;
                [default] NTLMv2_RESPONSE v2;