-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Christopher G. Lewis wrote: > Sorry I'm late in joining in on this thread - the dlist change screwed me up > :-).
Sorry about that. The new list seems to have latency issues, too; but I was getting fed up with people's subscription/unsubscription requests being rejected. And the alarming periods of downtime didn't help either. > Anyway - I've got NTLM working through the first part of the > Challenge/Response for NTLMv1 and NTLM v2, including v2's signing and > sealing (I believe). What an amazing piece of work :-) So, I take it the available builds on your site don't have NTLM support built? Is there a reason you weren't able to use the same code we Unix folks are using to support NTLM in the basic builds? > Most of what I'm working on has been taken from the LibCurl library, but my > C skills are sorely lacking, and there are some config items in LibCurl that > I'm not sure that we have in our ntlm.c. > > I can forward what I've got to anyone, including the inline diags that I've > got. Works gotten crazy (again) so haven't had time to work why my final > response calculation is failing. NTLMv2 uses MD5 vs NTLMv1's MD4. Boy, can I relate to being too busy to work on stuff. I didn't even know you were doing something with this, though! > This obviously should be a priority for the next release - I'm currently > using two versions of Wget.exe for internal stuff :-) Sounds like you've been secretly busy! :) - -- Micah J. Cowan Programmer, musician, typesetting enthusiast, gamer. GNU Maintainer: wget, screen, teseq http://micah.cowan.name/ -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkkcazcACgkQ7M8hyUobTrF2eQCfda2o/hO+SnISZR6FWFjJjpcy yIgAoIgVQ9p9gLbKzVEZkxDtD+eqLxHE =07ct -----END PGP SIGNATURE-----
