2003-01-13 15:48:37 +03:00
/*
Unix SMB / Netbios implementation .
Version 3.0
handle NLTMSSP , server side
Copyright ( C ) Andrew Tridgell 2001
Copyright ( C ) Andrew Bartlett 2001 - 2003
This program is free software ; you can redistribute it and / or modify
it under the terms of the GNU General Public License as published by
the Free Software Foundation ; either version 2 of the License , or
( at your option ) any later version .
This program is distributed in the hope that it will be useful ,
but WITHOUT ANY WARRANTY ; without even the implied warranty of
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE . See the
GNU General Public License for more details .
You should have received a copy of the GNU General Public License
along with this program ; if not , write to the Free Software
Foundation , Inc . , 675 Mass Ave , Cambridge , MA 0213 9 , USA .
*/
# include "includes.h"
Changes all over the shop, but all towards:
- NTLM2 support in the server
- KEY_EXCH support in the server
- variable length session keys.
In detail:
- NTLM2 is an extension of NTLMv1, that is compatible with existing
domain controllers (unlike NTLMv2, which requires a DC upgrade).
* This is known as 'NTLMv2 session security' *
(This is not yet implemented on the RPC pipes however, so there may
well still be issues for PDC setups, particuarly around password
changes. We do not fully understand the sign/seal implications of
NTLM2 on RPC pipes.)
This requires modifications to our authentication subsystem, as we
must handle the 'challege' input into the challenge-response algorithm
being changed. This also needs to be turned off for
'security=server', which does not support this.
- KEY_EXCH is another 'security' mechanism, whereby the session key
actually used by the server is sent by the client, rather than being
the shared-secret directly or indirectly.
- As both these methods change the session key, the auth subsystem
needed to be changed, to 'override' session keys provided by the
backend.
- There has also been a major overhaul of the NTLMSSP subsystem, to merge the 'client' and 'server' functions, so they both operate on a single structure. This should help the SPNEGO implementation.
- The 'names blob' in NTLMSSP is always in unicode - never in ascii.
Don't make an ascii version ever.
- The other big change is to allow variable length session keys. We
have always assumed that session keys are 16 bytes long - and padded
to this length if shorter. However, Kerberos session keys are 8 bytes
long, when the krb5 login uses DES.
* This fix allows SMB signging on machines not yet running MIT KRB5 1.3.1. *
- Add better DEBUG() messages to ntlm_auth, warning administrators of
misconfigurations that prevent access to the privileged pipe. This
should help reduce some of the 'it just doesn't work' issues.
- Fix data_blob_talloc() to behave the same way data_blob() does when
passed a NULL data pointer. (just allocate)
REMEMBER to make clean after this commit - I have changed plenty of data structures...
(This used to be commit f3bbc87b0dac63426cda6fac7a295d3aad810ecc)
2003-11-22 16:19:38 +03:00
/**
* Return the challenge as determined by the authentication subsystem
* @ return an 8 byte random challenge
*/
static const uint8 * auth_ntlmssp_get_challenge ( const struct ntlmssp_state * ntlmssp_state )
2003-01-13 15:48:37 +03:00
{
2003-01-16 06:29:54 +03:00
AUTH_NTLMSSP_STATE * auth_ntlmssp_state = ntlmssp_state - > auth_context ;
2003-01-15 23:39:33 +03:00
return auth_ntlmssp_state - > auth_context - > get_ntlm_challenge ( auth_ntlmssp_state - > auth_context ) ;
2003-01-13 15:48:37 +03:00
}
Changes all over the shop, but all towards:
- NTLM2 support in the server
- KEY_EXCH support in the server
- variable length session keys.
In detail:
- NTLM2 is an extension of NTLMv1, that is compatible with existing
domain controllers (unlike NTLMv2, which requires a DC upgrade).
* This is known as 'NTLMv2 session security' *
(This is not yet implemented on the RPC pipes however, so there may
well still be issues for PDC setups, particuarly around password
changes. We do not fully understand the sign/seal implications of
NTLM2 on RPC pipes.)
This requires modifications to our authentication subsystem, as we
must handle the 'challege' input into the challenge-response algorithm
being changed. This also needs to be turned off for
'security=server', which does not support this.
- KEY_EXCH is another 'security' mechanism, whereby the session key
actually used by the server is sent by the client, rather than being
the shared-secret directly or indirectly.
- As both these methods change the session key, the auth subsystem
needed to be changed, to 'override' session keys provided by the
backend.
- There has also been a major overhaul of the NTLMSSP subsystem, to merge the 'client' and 'server' functions, so they both operate on a single structure. This should help the SPNEGO implementation.
- The 'names blob' in NTLMSSP is always in unicode - never in ascii.
Don't make an ascii version ever.
- The other big change is to allow variable length session keys. We
have always assumed that session keys are 16 bytes long - and padded
to this length if shorter. However, Kerberos session keys are 8 bytes
long, when the krb5 login uses DES.
* This fix allows SMB signging on machines not yet running MIT KRB5 1.3.1. *
- Add better DEBUG() messages to ntlm_auth, warning administrators of
misconfigurations that prevent access to the privileged pipe. This
should help reduce some of the 'it just doesn't work' issues.
- Fix data_blob_talloc() to behave the same way data_blob() does when
passed a NULL data pointer. (just allocate)
REMEMBER to make clean after this commit - I have changed plenty of data structures...
(This used to be commit f3bbc87b0dac63426cda6fac7a295d3aad810ecc)
2003-11-22 16:19:38 +03:00
/**
* Some authentication methods ' fix ' the challenge , so we may not be able to set it
*
* @ return If the effective challenge used by the auth subsystem may be modified
*/
static BOOL auth_ntlmssp_may_set_challenge ( const struct ntlmssp_state * ntlmssp_state )
{
AUTH_NTLMSSP_STATE * auth_ntlmssp_state = ntlmssp_state - > auth_context ;
struct auth_context * auth_context = auth_ntlmssp_state - > auth_context ;
return auth_context - > challenge_may_be_modified ;
}
/**
2005-06-28 02:06:18 +04:00
* NTLM2 authentication modifies the effective challenge ,
Changes all over the shop, but all towards:
- NTLM2 support in the server
- KEY_EXCH support in the server
- variable length session keys.
In detail:
- NTLM2 is an extension of NTLMv1, that is compatible with existing
domain controllers (unlike NTLMv2, which requires a DC upgrade).
* This is known as 'NTLMv2 session security' *
(This is not yet implemented on the RPC pipes however, so there may
well still be issues for PDC setups, particuarly around password
changes. We do not fully understand the sign/seal implications of
NTLM2 on RPC pipes.)
This requires modifications to our authentication subsystem, as we
must handle the 'challege' input into the challenge-response algorithm
being changed. This also needs to be turned off for
'security=server', which does not support this.
- KEY_EXCH is another 'security' mechanism, whereby the session key
actually used by the server is sent by the client, rather than being
the shared-secret directly or indirectly.
- As both these methods change the session key, the auth subsystem
needed to be changed, to 'override' session keys provided by the
backend.
- There has also been a major overhaul of the NTLMSSP subsystem, to merge the 'client' and 'server' functions, so they both operate on a single structure. This should help the SPNEGO implementation.
- The 'names blob' in NTLMSSP is always in unicode - never in ascii.
Don't make an ascii version ever.
- The other big change is to allow variable length session keys. We
have always assumed that session keys are 16 bytes long - and padded
to this length if shorter. However, Kerberos session keys are 8 bytes
long, when the krb5 login uses DES.
* This fix allows SMB signging on machines not yet running MIT KRB5 1.3.1. *
- Add better DEBUG() messages to ntlm_auth, warning administrators of
misconfigurations that prevent access to the privileged pipe. This
should help reduce some of the 'it just doesn't work' issues.
- Fix data_blob_talloc() to behave the same way data_blob() does when
passed a NULL data pointer. (just allocate)
REMEMBER to make clean after this commit - I have changed plenty of data structures...
(This used to be commit f3bbc87b0dac63426cda6fac7a295d3aad810ecc)
2003-11-22 16:19:38 +03:00
* @ param challenge The new challenge value
*/
static NTSTATUS auth_ntlmssp_set_challenge ( struct ntlmssp_state * ntlmssp_state , DATA_BLOB * challenge )
{
AUTH_NTLMSSP_STATE * auth_ntlmssp_state = ntlmssp_state - > auth_context ;
struct auth_context * auth_context = auth_ntlmssp_state - > auth_context ;
SMB_ASSERT ( challenge - > length = = 8 ) ;
auth_context - > challenge = data_blob_talloc ( auth_context - > mem_ctx ,
challenge - > data , challenge - > length ) ;
auth_context - > challenge_set_by = " NTLMSSP callback (NTLM2) " ;
DEBUG ( 5 , ( " auth_context challenge set by %s \n " , auth_context - > challenge_set_by ) ) ;
DEBUG ( 5 , ( " challenge is: \n " ) ) ;
dump_data ( 5 , ( const char * ) auth_context - > challenge . data , auth_context - > challenge . length ) ;
return NT_STATUS_OK ;
}
/**
* Check the password on an NTLMSSP login .
*
* Return the session keys used on the connection .
*/
2004-04-06 12:11:16 +04:00
static NTSTATUS auth_ntlmssp_check_password ( struct ntlmssp_state * ntlmssp_state , DATA_BLOB * user_session_key , DATA_BLOB * lm_session_key )
2003-01-13 15:48:37 +03:00
{
2003-01-16 06:29:54 +03:00
AUTH_NTLMSSP_STATE * auth_ntlmssp_state = ntlmssp_state - > auth_context ;
2003-01-15 23:39:33 +03:00
auth_usersupplied_info * user_info = NULL ;
NTSTATUS nt_status ;
2003-01-13 15:48:37 +03:00
2003-01-15 23:39:33 +03:00
/* the client has given us its machine name (which we otherwise would not get on port 445).
we need to possibly reload smb . conf if smb . conf includes depend on the machine name */
2003-01-13 15:48:37 +03:00
2003-03-18 12:52:55 +03:00
set_remote_machine_name ( auth_ntlmssp_state - > ntlmssp_state - > workstation , True ) ;
2003-01-13 15:48:37 +03:00
2003-01-15 23:39:33 +03:00
/* setup the string used by %U */
/* sub_set_smb_name checks for weird internally */
sub_set_smb_name ( auth_ntlmssp_state - > ntlmssp_state - > user ) ;
2003-01-13 15:48:37 +03:00
2003-01-15 23:39:33 +03:00
reload_services ( True ) ;
2003-01-13 15:48:37 +03:00
2003-01-15 23:39:33 +03:00
nt_status = make_user_info_map ( & user_info ,
auth_ntlmssp_state - > ntlmssp_state - > user ,
auth_ntlmssp_state - > ntlmssp_state - > domain ,
auth_ntlmssp_state - > ntlmssp_state - > workstation ,
2004-04-03 19:41:32 +04:00
auth_ntlmssp_state - > ntlmssp_state - > lm_resp . data ? & auth_ntlmssp_state - > ntlmssp_state - > lm_resp : NULL ,
auth_ntlmssp_state - > ntlmssp_state - > nt_resp . data ? & auth_ntlmssp_state - > ntlmssp_state - > nt_resp : NULL ,
NULL , NULL , NULL ,
True ) ;
2003-01-13 15:48:37 +03:00
2005-11-08 09:19:34 +03:00
user_info - > logon_parameters = MSV1_0_ALLOW_SERVER_TRUST_ACCOUNT | MSV1_0_ALLOW_WORKSTATION_TRUST_ACCOUNT ;
2003-01-15 23:39:33 +03:00
if ( ! NT_STATUS_IS_OK ( nt_status ) ) {
return nt_status ;
2003-01-13 15:48:37 +03:00
}
Changes all over the shop, but all towards:
- NTLM2 support in the server
- KEY_EXCH support in the server
- variable length session keys.
In detail:
- NTLM2 is an extension of NTLMv1, that is compatible with existing
domain controllers (unlike NTLMv2, which requires a DC upgrade).
* This is known as 'NTLMv2 session security' *
(This is not yet implemented on the RPC pipes however, so there may
well still be issues for PDC setups, particuarly around password
changes. We do not fully understand the sign/seal implications of
NTLM2 on RPC pipes.)
This requires modifications to our authentication subsystem, as we
must handle the 'challege' input into the challenge-response algorithm
being changed. This also needs to be turned off for
'security=server', which does not support this.
- KEY_EXCH is another 'security' mechanism, whereby the session key
actually used by the server is sent by the client, rather than being
the shared-secret directly or indirectly.
- As both these methods change the session key, the auth subsystem
needed to be changed, to 'override' session keys provided by the
backend.
- There has also been a major overhaul of the NTLMSSP subsystem, to merge the 'client' and 'server' functions, so they both operate on a single structure. This should help the SPNEGO implementation.
- The 'names blob' in NTLMSSP is always in unicode - never in ascii.
Don't make an ascii version ever.
- The other big change is to allow variable length session keys. We
have always assumed that session keys are 16 bytes long - and padded
to this length if shorter. However, Kerberos session keys are 8 bytes
long, when the krb5 login uses DES.
* This fix allows SMB signging on machines not yet running MIT KRB5 1.3.1. *
- Add better DEBUG() messages to ntlm_auth, warning administrators of
misconfigurations that prevent access to the privileged pipe. This
should help reduce some of the 'it just doesn't work' issues.
- Fix data_blob_talloc() to behave the same way data_blob() does when
passed a NULL data pointer. (just allocate)
REMEMBER to make clean after this commit - I have changed plenty of data structures...
(This used to be commit f3bbc87b0dac63426cda6fac7a295d3aad810ecc)
2003-11-22 16:19:38 +03:00
nt_status = auth_ntlmssp_state - > auth_context - > check_ntlm_password ( auth_ntlmssp_state - > auth_context ,
user_info , & auth_ntlmssp_state - > server_info ) ;
2003-01-15 23:39:33 +03:00
free_user_info ( & user_info ) ;
2003-01-13 15:48:37 +03:00
Changes all over the shop, but all towards:
- NTLM2 support in the server
- KEY_EXCH support in the server
- variable length session keys.
In detail:
- NTLM2 is an extension of NTLMv1, that is compatible with existing
domain controllers (unlike NTLMv2, which requires a DC upgrade).
* This is known as 'NTLMv2 session security' *
(This is not yet implemented on the RPC pipes however, so there may
well still be issues for PDC setups, particuarly around password
changes. We do not fully understand the sign/seal implications of
NTLM2 on RPC pipes.)
This requires modifications to our authentication subsystem, as we
must handle the 'challege' input into the challenge-response algorithm
being changed. This also needs to be turned off for
'security=server', which does not support this.
- KEY_EXCH is another 'security' mechanism, whereby the session key
actually used by the server is sent by the client, rather than being
the shared-secret directly or indirectly.
- As both these methods change the session key, the auth subsystem
needed to be changed, to 'override' session keys provided by the
backend.
- There has also been a major overhaul of the NTLMSSP subsystem, to merge the 'client' and 'server' functions, so they both operate on a single structure. This should help the SPNEGO implementation.
- The 'names blob' in NTLMSSP is always in unicode - never in ascii.
Don't make an ascii version ever.
- The other big change is to allow variable length session keys. We
have always assumed that session keys are 16 bytes long - and padded
to this length if shorter. However, Kerberos session keys are 8 bytes
long, when the krb5 login uses DES.
* This fix allows SMB signging on machines not yet running MIT KRB5 1.3.1. *
- Add better DEBUG() messages to ntlm_auth, warning administrators of
misconfigurations that prevent access to the privileged pipe. This
should help reduce some of the 'it just doesn't work' issues.
- Fix data_blob_talloc() to behave the same way data_blob() does when
passed a NULL data pointer. (just allocate)
REMEMBER to make clean after this commit - I have changed plenty of data structures...
(This used to be commit f3bbc87b0dac63426cda6fac7a295d3aad810ecc)
2003-11-22 16:19:38 +03:00
if ( ! NT_STATUS_IS_OK ( nt_status ) ) {
return nt_status ;
}
2004-04-06 12:11:16 +04:00
if ( auth_ntlmssp_state - > server_info - > user_session_key . length ) {
2005-09-30 21:13:37 +04:00
DEBUG ( 10 , ( " Got NT session key of length %u \n " ,
( unsigned int ) auth_ntlmssp_state - > server_info - > user_session_key . length ) ) ;
2004-04-06 12:11:16 +04:00
* user_session_key = data_blob_talloc ( auth_ntlmssp_state - > mem_ctx ,
auth_ntlmssp_state - > server_info - > user_session_key . data ,
auth_ntlmssp_state - > server_info - > user_session_key . length ) ;
Changes all over the shop, but all towards:
- NTLM2 support in the server
- KEY_EXCH support in the server
- variable length session keys.
In detail:
- NTLM2 is an extension of NTLMv1, that is compatible with existing
domain controllers (unlike NTLMv2, which requires a DC upgrade).
* This is known as 'NTLMv2 session security' *
(This is not yet implemented on the RPC pipes however, so there may
well still be issues for PDC setups, particuarly around password
changes. We do not fully understand the sign/seal implications of
NTLM2 on RPC pipes.)
This requires modifications to our authentication subsystem, as we
must handle the 'challege' input into the challenge-response algorithm
being changed. This also needs to be turned off for
'security=server', which does not support this.
- KEY_EXCH is another 'security' mechanism, whereby the session key
actually used by the server is sent by the client, rather than being
the shared-secret directly or indirectly.
- As both these methods change the session key, the auth subsystem
needed to be changed, to 'override' session keys provided by the
backend.
- There has also been a major overhaul of the NTLMSSP subsystem, to merge the 'client' and 'server' functions, so they both operate on a single structure. This should help the SPNEGO implementation.
- The 'names blob' in NTLMSSP is always in unicode - never in ascii.
Don't make an ascii version ever.
- The other big change is to allow variable length session keys. We
have always assumed that session keys are 16 bytes long - and padded
to this length if shorter. However, Kerberos session keys are 8 bytes
long, when the krb5 login uses DES.
* This fix allows SMB signging on machines not yet running MIT KRB5 1.3.1. *
- Add better DEBUG() messages to ntlm_auth, warning administrators of
misconfigurations that prevent access to the privileged pipe. This
should help reduce some of the 'it just doesn't work' issues.
- Fix data_blob_talloc() to behave the same way data_blob() does when
passed a NULL data pointer. (just allocate)
REMEMBER to make clean after this commit - I have changed plenty of data structures...
(This used to be commit f3bbc87b0dac63426cda6fac7a295d3aad810ecc)
2003-11-22 16:19:38 +03:00
}
if ( auth_ntlmssp_state - > server_info - > lm_session_key . length ) {
2005-09-30 21:13:37 +04:00
DEBUG ( 10 , ( " Got LM session key of length %u \n " ,
( unsigned int ) auth_ntlmssp_state - > server_info - > lm_session_key . length ) ) ;
Changes all over the shop, but all towards:
- NTLM2 support in the server
- KEY_EXCH support in the server
- variable length session keys.
In detail:
- NTLM2 is an extension of NTLMv1, that is compatible with existing
domain controllers (unlike NTLMv2, which requires a DC upgrade).
* This is known as 'NTLMv2 session security' *
(This is not yet implemented on the RPC pipes however, so there may
well still be issues for PDC setups, particuarly around password
changes. We do not fully understand the sign/seal implications of
NTLM2 on RPC pipes.)
This requires modifications to our authentication subsystem, as we
must handle the 'challege' input into the challenge-response algorithm
being changed. This also needs to be turned off for
'security=server', which does not support this.
- KEY_EXCH is another 'security' mechanism, whereby the session key
actually used by the server is sent by the client, rather than being
the shared-secret directly or indirectly.
- As both these methods change the session key, the auth subsystem
needed to be changed, to 'override' session keys provided by the
backend.
- There has also been a major overhaul of the NTLMSSP subsystem, to merge the 'client' and 'server' functions, so they both operate on a single structure. This should help the SPNEGO implementation.
- The 'names blob' in NTLMSSP is always in unicode - never in ascii.
Don't make an ascii version ever.
- The other big change is to allow variable length session keys. We
have always assumed that session keys are 16 bytes long - and padded
to this length if shorter. However, Kerberos session keys are 8 bytes
long, when the krb5 login uses DES.
* This fix allows SMB signging on machines not yet running MIT KRB5 1.3.1. *
- Add better DEBUG() messages to ntlm_auth, warning administrators of
misconfigurations that prevent access to the privileged pipe. This
should help reduce some of the 'it just doesn't work' issues.
- Fix data_blob_talloc() to behave the same way data_blob() does when
passed a NULL data pointer. (just allocate)
REMEMBER to make clean after this commit - I have changed plenty of data structures...
(This used to be commit f3bbc87b0dac63426cda6fac7a295d3aad810ecc)
2003-11-22 16:19:38 +03:00
* lm_session_key = data_blob_talloc ( auth_ntlmssp_state - > mem_ctx ,
auth_ntlmssp_state - > server_info - > lm_session_key . data ,
auth_ntlmssp_state - > server_info - > lm_session_key . length ) ;
}
2003-01-15 23:39:33 +03:00
return nt_status ;
2003-01-13 15:48:37 +03:00
}
2003-01-15 23:39:33 +03:00
NTSTATUS auth_ntlmssp_start ( AUTH_NTLMSSP_STATE * * auth_ntlmssp_state )
2003-01-13 15:48:37 +03:00
{
NTSTATUS nt_status ;
2003-01-15 23:39:33 +03:00
TALLOC_CTX * mem_ctx ;
2003-01-13 15:48:37 +03:00
2003-01-15 23:39:33 +03:00
mem_ctx = talloc_init ( " AUTH NTLMSSP context " ) ;
2003-01-13 15:48:37 +03:00
2004-12-07 21:25:53 +03:00
* auth_ntlmssp_state = TALLOC_ZERO_P ( mem_ctx , AUTH_NTLMSSP_STATE ) ;
2003-01-15 23:39:33 +03:00
if ( ! * auth_ntlmssp_state ) {
DEBUG ( 0 , ( " auth_ntlmssp_start: talloc failed! \n " ) ) ;
talloc_destroy ( mem_ctx ) ;
return NT_STATUS_NO_MEMORY ;
}
2003-01-13 15:48:37 +03:00
2003-01-15 23:39:33 +03:00
ZERO_STRUCTP ( * auth_ntlmssp_state ) ;
2003-01-13 15:48:37 +03:00
2003-01-15 23:39:33 +03:00
( * auth_ntlmssp_state ) - > mem_ctx = mem_ctx ;
2003-01-13 15:48:37 +03:00
2003-01-15 23:39:33 +03:00
if ( ! NT_STATUS_IS_OK ( nt_status = ntlmssp_server_start ( & ( * auth_ntlmssp_state ) - > ntlmssp_state ) ) ) {
return nt_status ;
2003-01-13 15:48:37 +03:00
}
2003-01-15 23:39:33 +03:00
if ( ! NT_STATUS_IS_OK ( nt_status = make_auth_context_subsystem ( & ( * auth_ntlmssp_state ) - > auth_context ) ) ) {
return nt_status ;
}
2003-01-13 15:48:37 +03:00
2003-01-15 23:39:33 +03:00
( * auth_ntlmssp_state ) - > ntlmssp_state - > auth_context = ( * auth_ntlmssp_state ) ;
( * auth_ntlmssp_state ) - > ntlmssp_state - > get_challenge = auth_ntlmssp_get_challenge ;
Changes all over the shop, but all towards:
- NTLM2 support in the server
- KEY_EXCH support in the server
- variable length session keys.
In detail:
- NTLM2 is an extension of NTLMv1, that is compatible with existing
domain controllers (unlike NTLMv2, which requires a DC upgrade).
* This is known as 'NTLMv2 session security' *
(This is not yet implemented on the RPC pipes however, so there may
well still be issues for PDC setups, particuarly around password
changes. We do not fully understand the sign/seal implications of
NTLM2 on RPC pipes.)
This requires modifications to our authentication subsystem, as we
must handle the 'challege' input into the challenge-response algorithm
being changed. This also needs to be turned off for
'security=server', which does not support this.
- KEY_EXCH is another 'security' mechanism, whereby the session key
actually used by the server is sent by the client, rather than being
the shared-secret directly or indirectly.
- As both these methods change the session key, the auth subsystem
needed to be changed, to 'override' session keys provided by the
backend.
- There has also been a major overhaul of the NTLMSSP subsystem, to merge the 'client' and 'server' functions, so they both operate on a single structure. This should help the SPNEGO implementation.
- The 'names blob' in NTLMSSP is always in unicode - never in ascii.
Don't make an ascii version ever.
- The other big change is to allow variable length session keys. We
have always assumed that session keys are 16 bytes long - and padded
to this length if shorter. However, Kerberos session keys are 8 bytes
long, when the krb5 login uses DES.
* This fix allows SMB signging on machines not yet running MIT KRB5 1.3.1. *
- Add better DEBUG() messages to ntlm_auth, warning administrators of
misconfigurations that prevent access to the privileged pipe. This
should help reduce some of the 'it just doesn't work' issues.
- Fix data_blob_talloc() to behave the same way data_blob() does when
passed a NULL data pointer. (just allocate)
REMEMBER to make clean after this commit - I have changed plenty of data structures...
(This used to be commit f3bbc87b0dac63426cda6fac7a295d3aad810ecc)
2003-11-22 16:19:38 +03:00
( * auth_ntlmssp_state ) - > ntlmssp_state - > may_set_challenge = auth_ntlmssp_may_set_challenge ;
( * auth_ntlmssp_state ) - > ntlmssp_state - > set_challenge = auth_ntlmssp_set_challenge ;
2003-01-15 23:39:33 +03:00
( * auth_ntlmssp_state ) - > ntlmssp_state - > check_password = auth_ntlmssp_check_password ;
2003-01-16 06:29:54 +03:00
( * auth_ntlmssp_state ) - > ntlmssp_state - > server_role = lp_server_role ( ) ;
2003-01-13 15:48:37 +03:00
2003-01-15 23:39:33 +03:00
return NT_STATUS_OK ;
}
2003-01-13 15:48:37 +03:00
Changes all over the shop, but all towards:
- NTLM2 support in the server
- KEY_EXCH support in the server
- variable length session keys.
In detail:
- NTLM2 is an extension of NTLMv1, that is compatible with existing
domain controllers (unlike NTLMv2, which requires a DC upgrade).
* This is known as 'NTLMv2 session security' *
(This is not yet implemented on the RPC pipes however, so there may
well still be issues for PDC setups, particuarly around password
changes. We do not fully understand the sign/seal implications of
NTLM2 on RPC pipes.)
This requires modifications to our authentication subsystem, as we
must handle the 'challege' input into the challenge-response algorithm
being changed. This also needs to be turned off for
'security=server', which does not support this.
- KEY_EXCH is another 'security' mechanism, whereby the session key
actually used by the server is sent by the client, rather than being
the shared-secret directly or indirectly.
- As both these methods change the session key, the auth subsystem
needed to be changed, to 'override' session keys provided by the
backend.
- There has also been a major overhaul of the NTLMSSP subsystem, to merge the 'client' and 'server' functions, so they both operate on a single structure. This should help the SPNEGO implementation.
- The 'names blob' in NTLMSSP is always in unicode - never in ascii.
Don't make an ascii version ever.
- The other big change is to allow variable length session keys. We
have always assumed that session keys are 16 bytes long - and padded
to this length if shorter. However, Kerberos session keys are 8 bytes
long, when the krb5 login uses DES.
* This fix allows SMB signging on machines not yet running MIT KRB5 1.3.1. *
- Add better DEBUG() messages to ntlm_auth, warning administrators of
misconfigurations that prevent access to the privileged pipe. This
should help reduce some of the 'it just doesn't work' issues.
- Fix data_blob_talloc() to behave the same way data_blob() does when
passed a NULL data pointer. (just allocate)
REMEMBER to make clean after this commit - I have changed plenty of data structures...
(This used to be commit f3bbc87b0dac63426cda6fac7a295d3aad810ecc)
2003-11-22 16:19:38 +03:00
void auth_ntlmssp_end ( AUTH_NTLMSSP_STATE * * auth_ntlmssp_state )
2003-01-15 23:39:33 +03:00
{
TALLOC_CTX * mem_ctx = ( * auth_ntlmssp_state ) - > mem_ctx ;
2003-01-13 15:48:37 +03:00
2003-01-15 23:39:33 +03:00
if ( ( * auth_ntlmssp_state ) - > ntlmssp_state ) {
Changes all over the shop, but all towards:
- NTLM2 support in the server
- KEY_EXCH support in the server
- variable length session keys.
In detail:
- NTLM2 is an extension of NTLMv1, that is compatible with existing
domain controllers (unlike NTLMv2, which requires a DC upgrade).
* This is known as 'NTLMv2 session security' *
(This is not yet implemented on the RPC pipes however, so there may
well still be issues for PDC setups, particuarly around password
changes. We do not fully understand the sign/seal implications of
NTLM2 on RPC pipes.)
This requires modifications to our authentication subsystem, as we
must handle the 'challege' input into the challenge-response algorithm
being changed. This also needs to be turned off for
'security=server', which does not support this.
- KEY_EXCH is another 'security' mechanism, whereby the session key
actually used by the server is sent by the client, rather than being
the shared-secret directly or indirectly.
- As both these methods change the session key, the auth subsystem
needed to be changed, to 'override' session keys provided by the
backend.
- There has also been a major overhaul of the NTLMSSP subsystem, to merge the 'client' and 'server' functions, so they both operate on a single structure. This should help the SPNEGO implementation.
- The 'names blob' in NTLMSSP is always in unicode - never in ascii.
Don't make an ascii version ever.
- The other big change is to allow variable length session keys. We
have always assumed that session keys are 16 bytes long - and padded
to this length if shorter. However, Kerberos session keys are 8 bytes
long, when the krb5 login uses DES.
* This fix allows SMB signging on machines not yet running MIT KRB5 1.3.1. *
- Add better DEBUG() messages to ntlm_auth, warning administrators of
misconfigurations that prevent access to the privileged pipe. This
should help reduce some of the 'it just doesn't work' issues.
- Fix data_blob_talloc() to behave the same way data_blob() does when
passed a NULL data pointer. (just allocate)
REMEMBER to make clean after this commit - I have changed plenty of data structures...
(This used to be commit f3bbc87b0dac63426cda6fac7a295d3aad810ecc)
2003-11-22 16:19:38 +03:00
ntlmssp_end ( & ( * auth_ntlmssp_state ) - > ntlmssp_state ) ;
2003-01-15 23:39:33 +03:00
}
if ( ( * auth_ntlmssp_state ) - > auth_context ) {
( ( * auth_ntlmssp_state ) - > auth_context - > free ) ( & ( * auth_ntlmssp_state ) - > auth_context ) ;
}
if ( ( * auth_ntlmssp_state ) - > server_info ) {
free_server_info ( & ( * auth_ntlmssp_state ) - > server_info ) ;
2003-01-13 15:48:37 +03:00
}
2003-01-15 23:39:33 +03:00
talloc_destroy ( mem_ctx ) ;
* auth_ntlmssp_state = NULL ;
}
2003-01-13 15:48:37 +03:00
2003-01-15 23:39:33 +03:00
NTSTATUS auth_ntlmssp_update ( AUTH_NTLMSSP_STATE * auth_ntlmssp_state ,
2003-02-24 05:35:54 +03:00
const DATA_BLOB request , DATA_BLOB * reply )
2003-01-15 23:39:33 +03:00
{
Changes all over the shop, but all towards:
- NTLM2 support in the server
- KEY_EXCH support in the server
- variable length session keys.
In detail:
- NTLM2 is an extension of NTLMv1, that is compatible with existing
domain controllers (unlike NTLMv2, which requires a DC upgrade).
* This is known as 'NTLMv2 session security' *
(This is not yet implemented on the RPC pipes however, so there may
well still be issues for PDC setups, particuarly around password
changes. We do not fully understand the sign/seal implications of
NTLM2 on RPC pipes.)
This requires modifications to our authentication subsystem, as we
must handle the 'challege' input into the challenge-response algorithm
being changed. This also needs to be turned off for
'security=server', which does not support this.
- KEY_EXCH is another 'security' mechanism, whereby the session key
actually used by the server is sent by the client, rather than being
the shared-secret directly or indirectly.
- As both these methods change the session key, the auth subsystem
needed to be changed, to 'override' session keys provided by the
backend.
- There has also been a major overhaul of the NTLMSSP subsystem, to merge the 'client' and 'server' functions, so they both operate on a single structure. This should help the SPNEGO implementation.
- The 'names blob' in NTLMSSP is always in unicode - never in ascii.
Don't make an ascii version ever.
- The other big change is to allow variable length session keys. We
have always assumed that session keys are 16 bytes long - and padded
to this length if shorter. However, Kerberos session keys are 8 bytes
long, when the krb5 login uses DES.
* This fix allows SMB signging on machines not yet running MIT KRB5 1.3.1. *
- Add better DEBUG() messages to ntlm_auth, warning administrators of
misconfigurations that prevent access to the privileged pipe. This
should help reduce some of the 'it just doesn't work' issues.
- Fix data_blob_talloc() to behave the same way data_blob() does when
passed a NULL data pointer. (just allocate)
REMEMBER to make clean after this commit - I have changed plenty of data structures...
(This used to be commit f3bbc87b0dac63426cda6fac7a295d3aad810ecc)
2003-11-22 16:19:38 +03:00
return ntlmssp_update ( auth_ntlmssp_state - > ntlmssp_state , request , reply ) ;
2003-01-13 15:48:37 +03:00
}