(And since this page is a highly ranked google search result for downloading old versions of chrome, mountain lion, etc, many of those currently reading this are likely in the same situation I was in: simply looking to install a functioning Chrome on Mountain Lion.)įortunately, as of today, Chrome 49 can simply be downloaded and installed from either of the following sites: (Chrome 52 did not work for me as Kay Yin suggested, though your mileage may vary.)Īlthough the OP asks for Chrome 50, my suggestion is to stick with Chrome 49. (I tried on Mountain Lion I was able to make the "no" symbol go away, but when I attempted to open Chrome, I simply got an error alert claiming that the app was corrupt and suggesting that I move it to the trash.)Īs the OP mentions, Chrome 50 was the first version to drop legacy OS support, so Chrome 49 is the latest version that can be installed without much ado.
Download the googlechrome.dmg file from the link directly above,.To get the latest version of Google Chrome on OS X Mountain Lion 10.8.x, do the following: At the present time that googlechrome.dmg file contains version.On later versions of OS X, the downloaded googlechrome.dmg file's URL is:.
If you have an earlier version installed, e.g.109, and update it through Google Chrome it will report: "Google Chrome is up to date."
Note that the downloaded googlechrome.dmg file's URL is: Direct Download Links for Mac OS X 10.6.8: If you need to update multiple computers but only want to download the update once, or you simply don’t want to go the Software Update route, here are the direct download links: Mac OS X 10.6.8 Update (474.2 MB) Mac OS X 10.6.8 Update Combo (1.09 GB) Mac OS X Server v10.6.8 Update (542 MB.If you then try to update it through Google Chrome it will report: "Google Chrome is up to date." If you do not have Google Chrome installed, and you download a copy and install it, the version will show as. Sudo echo 'exec /Applications/Google\ Chrome.app/Contents/MacOS/Google\ Chrome.bin -args -auth-server-whitelist="*DOMAIN.TLD" -auth-negotiate-delegate-whitelist="*DOMAIN.At the present time the latest version of Google Chrome is. Sudo echo "#!/bin/bash" > "Google Chrome" Sudo mv 'Google Chrome' 'Google Chrome.bin' #!/bin/bashĬd /Applications/Google\ Chrome.app/Contents/MacOS/ Running the following shell script at log in was the final solution to get around Chrome updates and extra doc icons. Unfortunately Google Chrome for Mac has no way of specifying command line arguments on every load, so some sort of shell script will need to be made. SOLUTION open 'Google Chrome.app' -args -auth-server-whitelist="*DOMAIN.TLD" -auth-negotiate-delegate-whitelist="*DOMAIN.TLD" -auth-schemes="digest,ntlm,negotiate" There is a proxy setup, but it gets bypassed for local intranet sites, so I don't think it is playing a role.Īlso tried using the -auth-server-whitelist command line switch, didn't work. appcmd set config /section:windowsAuthentication /-providers.Īnyone know a solution for Chrome on OS X?Ĭentrify for Mac will be used to authenticate to the (Windows 2008 R2 ActiveDirectory) network via CAC. I've tried toggling the Windows Authentication on the site to negotiate, but same user/pass prompt. Since the internal network uses CAC/PKI no one has a password.
When hit from Chrome on windows the pass-through authentication works fine (no User / Password prompt), however, Chrome on a Mac you get a prompt. An IIS7 Intranet site with Windows Authentication enabled.