FreeTDS Development Group

[Samuel Bayer <sam AT mitre.org>]

freddy77 AT gmail.com wrote:

> 2010/11/10 Samuel Bayer<sam AT mitre.org>:
> > I'll check with my admins, but I'm virtually certain that this really is
> > NTLMv2. As I said earlier, the jTDS JDBC connection works with the useNTLMv2
> > flag set, and I'm assuming that that code is correct. But I could be wrong.
> >
> > Unfortunately, I don't believe I have access to a different version of SQL
> > Server.
> >
> > Does anyone know which of the precise cases described in Appendix C of
> > http://davenport.sourceforge.net/ntlm.html my case corresponds to? I've been
> > assuming it's either "NTLMv2 Authentication; NTLM1 Signing and Sealing Using
> > the 40-bit NTLMv2 User Session Key" or "NTLMv2 Authentication; NTLM2 Signing
> > and Sealing Using the 56-bit NTLMv2 User Session Key", but all this NTLM2 vs
> > NTLMv2 stuff is making my head swim a bit.
> >
> > Thanks in advance -
> >
> > Sam Bayer
> > The MITRE Corporation
> > sam AT mitre.org
>
> Just committed a patch for NTLMv2 and 64-bit systems due to different
> structure alignment.
>
> freddy77

Victory, of a sort. It worked - once. I did a clean checkout, "make", 
"make install", and then the installed version allowed me to connect to 
the DB - but I'd installed on top of a previous build from last week's 
checkout. THAT worked. As soon as I removed the previous install and did 
a clean "make install", it failed in the same way it did previously.

I'm mystified, to say the least. I can't reconstruct what I might have 
done to get it to work in that one case.

But we're getting SOMEwhere. I'm going to go try this on Linux and see 
what happens.

Thanks again -
Sam Bayer