Whoops, sorry for the empty message. This seems like a broken client. Can you check whether the client sending that was a legitimate one? On Mon, Oct 6, 2014 at 10:24 AM, Victor Sudakov <sudakov@xxxxxxxxxxxxxxxx> wrote: > Colleagues, > > The NTLM (LM) plugin in squid27 worked perfectly while the NTLM plugin in > squid34 is obviously broken. > > I am attaching two log files, one of the old plugin and the other of > the new one. Could someone please have a look at bad-ntlm.log to see > why ntlm_smb_lm_auth does not work any more after upgrading to 34? > > What does this failure > > ntlmssp: bad ascii: ffffffab > No auth at all. Returning no-auth > ntlm_smb_lm_auth.cc(531): pid=16346 :sending 'NA Logon Failure' to squid > > actually mean? > > I know that LM is bad and insecure, but I cannot give it up for the > present in the production environment until I make Kerberos > (negotiate) work. > > -- > Victor Sudakov, VAS4-RIPE, VAS47-RIPN > sip:sudakov@xxxxxxxxxxxxxxxx > > _______________________________________________ > squid-users mailing list > squid-users@xxxxxxxxxxxxxxxxxxxxx > http://lists.squid-cache.org/listinfo/squid-users > -- Francesco _______________________________________________ squid-users mailing list squid-users@xxxxxxxxxxxxxxxxxxxxx http://lists.squid-cache.org/listinfo/squid-users
