Displaying 4 results from an estimated 4 matches for "client_response".
2004 Nov 10
0
[PATCH] NTLM update and crashfix
...-ntlm.c dovecot-1.0-test52/src/auth/mech-ntlm.c
--- dovecot-1.0-test52.vanilla/src/auth/mech-ntlm.c 2004-10-22 17:32:27.000000000 +0400
+++ dovecot-1.0-test52/src/auth/mech-ntlm.c 2004-11-10 16:45:53.000000000 +0300
@@ -42,10 +42,15 @@ lm_credentials_callback(const char *cred
const unsigned char *client_response;
unsigned char lm_response[LM_RESPONSE_SIZE];
unsigned char hash[LM_HASH_SIZE];
+ unsigned int response_length;
buffer_t *hash_buffer;
int ret;
- if (credentials == NULL) {
+ response_length =
+ ntlmssp_buffer_length(request->response, lm_response);
+ client_response = ntlmssp_buffer_...
2004 Oct 29
1
[PATCH] yet another NTLM update
...ech-ntlm.c 2004-10-29 14:54:38.000000000 +0400
@@ -74,7 +74,11 @@ ntlm_credentials_callback(const char *cr
buffer_t *hash_buffer;
int ret;
- if (credentials == NULL && !request->ntlm2_negotiated) {
+ response_length =
+ ntlmssp_buffer_length(request->response, ntlm_response);
+ client_response = ntlmssp_buffer_data(request->response, ntlm_response);
+
+ if ((credentials == NULL && !request->ntlm2_negotiated) || !response_length) {
passdb->lookup_credentials(auth_request,
PASSDB_CREDENTIALS_LANMAN,
lm_credentials_callback);
@@ -85,9 +89,6 @@ ntlm_cred...
2004 Sep 30
1
[PATCH] NTLM2 support
...ponse(hash, auth->challenge, ntlm_response);
+ if (auth->ntlm2_negotiated)
+ ntlmssp2_response(hash, auth->challenge,
+ client_lm_response,
+ ntlm_response);
+ else
+ ntlmssp_v1_response(hash, auth->challenge,
+ ntlm_response);
ret = memcmp(ntlm_response, client_response,
NTLMSSP_RESPONSE_SIZE) == 0;
@@ -145,6 +154,7 @@ mech_ntlm_auth_continue(struct auth_requ
message = ntlmssp_create_challenge(auth->pool, request,
&message_size);
+ auth->ntlm2_negotiated = message->flags & NTLMSSP_NEGOTIATE_NTLM2;
auth->challenge = m...
2006 Sep 26
15
RE: Individual passwords for guest VNC servers ?
> Thanks all point about security, I''ll do as follows.
> I thought that the point was the following two.
>
>
> 1. Storage place of encrypted password
> Should I store it in /etc/xen/passwd ?
> Or, should I wait for DB of Xen that will be released in
> the future?
The xend life cycle management patches were posted by Alistair a couple
of months back.