From 04872cb4b5110bf4be81833ea547e189344ceee0 Mon Sep 17 00:00:00 2001 From: Zlatko Knezevic Date: Sun, 15 May 2016 20:50:56 -0700 Subject: [PATCH] Update known-issues.md (#3045) Add OpenSSL section to the known issues list as per feedback from various community members. List out the Homebrew step but also show the MacPorts steps. --- Documentation/known-issues.md | 20 ++++++++++++++++++++ 1 file changed, 20 insertions(+) diff --git a/Documentation/known-issues.md b/Documentation/known-issues.md index 29af92b03..b3a858cb7 100644 --- a/Documentation/known-issues.md +++ b/Documentation/known-issues.md @@ -1,6 +1,26 @@ Known issues & workarounds ========================== +## OpenSSL dependency on OS X +OS X "El Capitan" (10.11) comes with 0.9.8 version of OpenSSL. .NET Core depends on versions >= 1.0.1 of OpenSSL. You can update the version by using [Homebrew](https://brew.sh), [MacPorts](https://www.macports.org/) or manually. The important bit is that you need to have the required OpenSSL version on the path when you work with .NET Core. + +With Homebrew, you can run the following commands to get this done: + +```console +brew update +brew install openssl +brew link --force openssl +``` + +MacPorts doesn't have the concept of linking, so it is reccomended that you uninstall 0.9.8 version of OpenSSL using the following command: + +```console +sudo port upgrade openssl +sudo port -f uninstall openssl @0.9.8 +``` + +You can verify whether you have the right version using the `openssl version` command from the Terminal. + ## `dotnet restore` times out on Win7 x64 If you have Virtual Box and you try to use the CLI on a Win7 x64 machine, `dotnet restore` will be really slow and will eventually time out without doing much restoring.