Return-Path: Delivered-To: apmail-jakarta-commons-httpclient-dev-archive@www.apache.org Received: (qmail 35519 invoked from network); 20 Feb 2004 11:44:51 -0000 Received: from daedalus.apache.org (HELO mail.apache.org) (208.185.179.12) by minotaur-2.apache.org with SMTP; 20 Feb 2004 11:44:51 -0000 Received: (qmail 67065 invoked by uid 500); 20 Feb 2004 11:44:50 -0000 Delivered-To: apmail-jakarta-commons-httpclient-dev-archive@jakarta.apache.org Received: (qmail 66820 invoked by uid 500); 20 Feb 2004 11:44:49 -0000 Mailing-List: contact commons-httpclient-dev-help@jakarta.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Help: List-Post: List-Id: "Commons HttpClient Project" Reply-To: "Commons HttpClient Project" Delivered-To: mailing list commons-httpclient-dev@jakarta.apache.org Received: (qmail 66805 invoked from network); 20 Feb 2004 11:44:48 -0000 Received: from unknown (HELO felix.lh.net.au) (203.149.69.43) by daedalus.apache.org with SMTP; 20 Feb 2004 11:44:48 -0000 Received: from [192.168.1.4] (ppp188-40.lns1.bne1.internode.on.net [150.101.188.40]) by felix.lh.net.au (Postfix) with ESMTP id 68F125061 for ; Fri, 20 Feb 2004 21:44:35 +1000 (EST) User-Agent: Microsoft-Entourage/10.1.4.030702.0 Date: Fri, 20 Feb 2004 21:44:45 +1000 Subject: Re: NTLM or NTLMv2? From: Adrian Sutton To: Commons HttpClient Project Message-ID: In-Reply-To: <4035CC79.8030003@gli-micram.de> Mime-version: 1.0 Content-type: text/plain; charset="US-ASCII" Content-transfer-encoding: 7bit X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N > It is possible to set the minimum security that is used for programs > that use the NTLM Security Support Provider (SSP) by modifying a > registry key. So anybody may set level 5 which does not accept NTLM but > NTLMv2 only. Do you refer to that by naming Windows 2003 Server? > If so that would mean NTLMv2 is not supported by HttpClient. Correct? Hi Steven, The information you quote is for Windows NT 4.0 and Windows 2000, as far as can be determined, HttpClient is fully compatible with these OS's, the only problem (and it is theoretical as we haven't received any actual reports of it not working) is with Windows 2003 Server in a specific configuration. As I understand it, the configuration isn't so much a new version of NTLM as adding a cryptographic key to the messages such that only Windows can be compatible with it. It is essentially an attempt by Microsoft to break SAMBA (the linux-based project). >From what you've sent through I would say that HttpClient does support NTLMv2 however I have to stress that there are no published specs for NTLM (any version) and as such the only real way to know if it works for you is to test it. > Stefan Dingfelder Regards, Adrian Sutton. ---------------------------------------------- Intencha "tomorrow's technology today" Ph: 38478913 0422236329 Suite 8/29 Oatland Crescent Holland Park West 4121 Australia QLD www.intencha.com --------------------------------------------------------------------- To unsubscribe, e-mail: commons-httpclient-dev-unsubscribe@jakarta.apache.org For additional commands, e-mail: commons-httpclient-dev-help@jakarta.apache.org