Fixing Chrome for the Poodle vulnerability seems to be more difficult on OSX than the other Operating Systems

This seems to work...

Exit chrome

Open Applescript editor

Enter this script

do shell script "open -a /Applications/Google\\ Chrome.app --args --ssl-version-min=tls1"

click run.

Check on this page, (you may need to cmd + R) refresh the page.


But is there a better way, or have I missed something?

Source: How do I disable SSLv3 in Safari (OSX & iOS)


Here is a patch, which is renaming Google Chrome/Chromium inside startup file and placing a script for calling browser with --ssl-version-min=tls1 parameter. No wrapper needed.

  • This works quite well. Does it interfere with Chrome's automatic updates? I suspect the shell script, after copying to Chrome.app, will be overwritten by updates. Did you intend people to put it into ~/.bashrc to avoid this? – RichVel Oct 24 '14 at 12:48
  • Currently i'm looking for a safe method to solve that update problem and testing next Google browsers for tls capability without that startup parameter. I'm not sure relying on .bashrc, maybe a user cronjob would be better. – Olivetti Oct 24 '14 at 23:35

This seems to work:

defaults write com.google.chrome org.chromium.ssl.ssl3 -bool no
  • This does not seem to do anything for me. – Volsk Oct 16 '14 at 16:03
  • hmmm, mileage may vary, but this isn't working for me. Visiting www.poodletest.com shows a poodle – chim Oct 16 '14 at 16:09
  • I think it required a browser restart for the test to start passing, but I assume you tried that. – John Evanson Oct 22 '14 at 20:46

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .