Smoothwall - NTLM - Chrome 47.0.2526.73

[grdrager]

If anyone has downloaded the current version of Chrome - Stable Channel release 47.0.2526.73 released today and is also running a Smoothwall with NTLM authentication, I was wondering if you are seeing any issues?

 

Currently with this release we are no longer getting NTLM "pass-through" or automatic authentication in Chrome. Any sites not on our authentication bypass list are prompting for a username and password. Internet Explorer and Firefox are fine, as was Chrome before this afternoons updates (46.0.2490.86). I am just trying to figure out is this is a global issue or something specific to our configuration.

 

Thanks!

[danlar78]

Hi. We have the same problem on the clients that have updated to 47.0.2526.73. Earlier versions works fine. We don't have a Smoothwall but we do have an other firewall and on the inside of that we have a proxy server that uses NTLM authentication. (IE still works fine.)

[grdrager]

Thanks. I've seen a few other responses as well that indicate it is an issue with 47.0.2526.73. I have reported this as a bug to the Chromium project. https://code.google.com/p/chromium/issues/detail?id=564611. When I filed this it was as a security bug so it is not publicly visible at this point (my bad). Edited December 2, 2015 by grdrager

[bozallen]

We're experiencing the same issue. Chrome 47.0.2526.73 and Smoothwall proxy using NTLM authentication. I also reported a bug. Hopefully if enough people do this a fix will be released soon.

[Sheridan]

Same here, intermittent and random NTLM authentication errors.

 

As Chrome updates itself this is going to start causing a major headache!

 

Anyone got a copy of version 46 I can use to downgrade!?

Edited December 3, 2015 by Sheridan

[Blue_Cookeh]

Same here, intermittent and random NTLM authentication errors.

 

As Chrome updates itself this is going to start causing a major headache!

 

Anyone got a copy of version 46 I can use to downgrade!?

 

I wouldn't bother downgrading, a fix is coming in the next day or so.

[Sheridan]

I wouldn't bother downgrading, a fix is coming in the next day or so.

 

'Or so' - I'll just tell the staff here that!

 

Its a pain as our VLE depends on Chrome - so we use a shortcut that automatically takes them to it using Chrome.

[grdrager]

If you want to track progress on the bug, the merged thread on Chromium is here:

 

https://code.google.com/p/chromium/issues/detail?id=544255

[grdrager]

Just to add a bit the developer working on this said that the fix should be finished today or tomorrow. Once it is fixed it will go out with the next release. They expect this bug to be significant enough to warrant a rush release, but no fixed date.

[grdrager]

@Sheridan: I believe the upgrade process archives the prior version as old_chrome.exe in the same directory as your Chrome executable, so you should be able to use that.

[Sheridan]

@Sheridan: I believe the upgrade process archives the prior version as old_chrome.exe in the same directory as your Chrome executable, so you should be able to use that.

 

I did have a quick look at this earlier, but non of my clients seem to have the old_chrome.exe anywhere.

 

I've told everyone to use IE in the short term.

[grdrager]

In looking at the process, the upgrade is supposed delete old_chrome.exe after the process completes. I guess I just managed to catch it on a machine.

[ass17]

You should be able to get any older software from http://www.oldversion.com otherwise wait another day. BTW we have had no issues here, strange

[Sheridan]

Its quite widespread here, had to move everyone back onto IE. Just like the good old days when you just used one browser!

[zag]

Just run into this one myself after updating chrome. NTLM errors all over the place!

 

Lets hope they fix it over the weekend.

 

Nightmare!

[Sheridan]

Its pretty frustrating as its out of our hands, I notice the chrome developers have locked the issue forum now, they're getting huffy about the amount of comments!

 

It might work out for the best, we've directed people back to IE - they might realise it was as good as chrome all along anyway.

[Sheridan]

Still no sign of a fix, I've had to change shortcuts to force usage of IE.

 

Is there a way to block chrome from auto updating? I know its a bit late now, but it stop them breaking it across the network again in the future.

[jaminben]

Is there a way to block chrome from auto updating? I know its a bit late now, but it stop them breaking it across the network again in the future.

 

Yes, you can block Chrome from updating, you just need to get the .admx files... that's what we do here.

 

Computer Policy - Google/Google Update/Preferences = Disable all auto-update checks (not recommended)

Edited December 7, 2015 by jaminben

[Arthur]

Still no sign of a fix

Based on similar bugs in the past, I wouldn't expect a fix from Google for another week or two.

[Sheridan]

Yes, you can block Chrome from updating, you just need to get the .admx files... that's what we do here.

 

Computer Policy - Google/Google Update/Preferences = Disable all auto-update checks (not recommended)

 

Brilliant, thanks. I'd been looking in the Chrome policy settings themselves, didn't realise it was a seperate policy set!

[grdrager]

Also might want to block Chromebooks from updating in the Admin console if you have any of those. Updated Chromebooks are starting to trickle into my office.

 

Device management >Chrome >Device Settings >Auto Update Settings

[Duke5A]

I'm glad I went through the trouble of moving my Squid proxies over to Kerberos a few years back. Chrome is our default browser, but luckily there hasn't been any issues.

[Sheridan]

I'm glad I went through the trouble of moving my Squid proxies over to Kerberos a few years back. Chrome is our default browser, but luckily there hasn't been any issues.

 

To be fair, we've never had an issue with NTLM on our smoothwall,until they released a buggy version of chrome!

[Localtechie]

Still broken on the latest release!

[zag]

Going to go ahead and restrict comments on this bug. 150 posts about how many users are affected aren't really useful, and we don't need further information for those affected.

 

Thanks for everyone who posted information about working around the issue!

 

I'll post again after the fix starts rolling out.

 

Still waiting, argh!! At least its now confirmed fixed in version 47

Edited December 8, 2015 by zag