PS: I also cannot reproduce the problem when going back to MacOS 10.12's default python installation, installing and './emsdk update' both work:
➜ emsdk_portable python -c "import ssl; print ssl.OPENSSL_VERSION" OpenSSL 0.9.8zh 14 Jan 2016 ➜ emsdk_portable python --version Python 2.7.10 ➜ emsdk_portable ... ./emsdk update Downloading: /Users/floh/projects/fips-sdks/osx/emsdk_portable/zips/emsdk_unix_update.tar.gz from https://s3.amazonaws.com/mozilla-games/emscripten/packages/emsdk_unix_update.tar.gz Unpacking '/Users/floh/projects/fips-sdks/osx/emsdk_portable/zips/emsdk_unix_update.tar.gz' to '/Users/floh/projects/fips-sdks/osx/emsdk_portable' x emscripten-tags.txt x emsdk x emsdk_env.sh x emsdk_manifest.json x README.md Fetching all tags from Emscripten Github repository... Done. 81 tagged releases available, latest is 1.36.9. As far as I know, the problem on Debian Linux was going away when switching from unstable Debian to a stable version. Am Montag, 19. September 2016 11:44:21 UTC+2 schrieb Floh: > > I haven't seen the certificate problem on OSX yet (I'm currently on the > latest MacOS Sierra prerelease-version). > > However I'm not using the standard python version coming with OSX (which > is 2.7.10), but use the brew version 2.7.12. I have also openssl installed > via brew (although not directly must be a dependency of another package). > > I guess this is how to find out which openssl version python is using: > > > python -c "import ssl; print ssl.OPENSSL_VERSION" > > ...which in my case prints: > > OpenSSL 1.0.2h 3 May 2016 > > Cheers, > -Floh. > > > Am Sonntag, 18. September 2016 21:58:38 UTC+2 schrieb jj: >> >> No idea which version will be used. Emsdk invokes 'python' on the command >> line to do all the work (via #!/usr/bin/python shebang at top of emsdk >> script), and the http(s) requests it does are launched via python's http >> libraries, and git commands via the 'git' command line, by looking its >> location up in PATH. I think the question thus boils down to "which version >> of openssl does 'python'/'git' use on my system?". >> >> 2016-09-18 12:58 GMT+03:00 Matt Wallis <[email protected]>: >> >>> On Sunday, August 14, 2016 at 10:21:57 AM UTC+1, Floh wrote: >>>> >>>> Hi, I just got a bug ticket in one of my projects from a user who has >>>> trouble setting up the emscripten SDK because of an SSL certificate >>>> validation error in the emsdk script when downloading the file >>>> https://s3.amazonaws.com/mozilla-games/emscripten/packages/emsdk_unix_update.tar.gz. >>>> >>>> >>>> >>> I have the same problem, but on MacOS/X 10.11.5. Having download >>> https://s3.amazonaws.com/mozilla-games/emscripten/releases/emsdk-portable.tar.gz, >>> >>> and unpacked it, I can't get beyond `.emsdk update`, which produces the >>> following error from urllib2: >>> >>> urllib2.URLError: <urlopen error [SSL: CERTIFICATE_VERIFY_FAILED] >>> certificate verify failed (_ssl.c:590)> >>> >>> >>> I think that the route cause of thie error is explained at >>> http://stackoverflow.com/a/27826829/685715 - this says that the problem >>> should be fixed in openssl 1.0.2. I have 2 versions of openssl >>> >>> >>> - Version provided by mac OS/X: /usr/bin/openssl, version 0.9.8 >>> >>> - Version provided by macports: /opt/local/bin/openssl, version 1.0.2 >>> >>> >>> So which version will be used when I run `./emsdk update` ? If it turns >>> out to be the older version, how do i force it to use the newer version, in >>> the hope that this fixes the problem? >>> >>> >>> Matt >>> >>> -- >>> You received this message because you are subscribed to the Google >>> Groups "emscripten-discuss" group. >>> To unsubscribe from this group and stop receiving emails from it, send >>> an email to [email protected]. >>> For more options, visit https://groups.google.com/d/optout. >>> >> >> -- You received this message because you are subscribed to the Google Groups "emscripten-discuss" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
