How do I resolved this error on Solaris 11?
"Could not autodetect OpenSSL support. Make sure OpenSSL development packages are installed. Use configure --without-ssl to disable this message."
It is odd because I know that I have openssl 1.0.0e.
Also I know that Node is looking in /usr/include and that the files /usr/include/openssl/ssl.h and /usr/include/openssl/crypto.h exist.
Ubuntu Equivalent
The "OpenSSL development packages" are actually not the "openssl" package.
You need to apt-get (or similar for Solaris) install the package called "libssl-dev".
For me, this solved the problem while trying to configure the source for node.js.
If you have openssl already installed in /usr/local/ssl, use those configure options:
--openssl-includes=/usr/local/ssl/include --openssl-libpath=/usr/local/ssl/lib
Related
In a server linux Centos 5 64bit, I have compile from the source code the webserver Apache version 2.4.6.
Below, the configure instruction that I have used.
./configure --enable-mods-shared=reallyall --with-suexec-caller=apache --enable-cache --enable-cache-disk --with-ldap --enable-ldap --enable-authnz-ldap
Now, I must recompile the webserver Apache to using the new installed version of openssl (1.0.1e-fips).
What is the correct syntax to reconfigure Apache to using the current version of openssl installed on the server?
Many thanks at all.
As you unfortunately didn't mention how you installed OpenSSL 1.0.1e-fips (and where), this can't be answered. Based on 1.0.1e-fips, I see some chances that you used my openssl101e RPM package from EPEL 5 (even more important: openssl101e-devel). If so, run
export CFLAGS="$CFLAGS -I/usr/include/openssl101e"
export CPPFLAGS="$CPPFLAGS -I/usr/include/openssl101e"
export LDFLAGS="$LDFLAGS -L/usr/include/openssl101e"
before ./configure. Otherwise you first need to reveal more details about your OpenSSL 1.0.1e-fips installation/update.
I have a website that uses websocket-sharp for client-server communication and has a certificate issued by Let's Encrypt. Other browsers work, but Google Chrome (on Linux) gives the error ERR_SSL_VERSION_INTERFERENCE in the console. Disabling TLS 1.3 lets users circumvent this error. I am using the latest stable version.
This answer suggests the problem is when Chrome detects "buggy middleware" but I don't know what exactly Chrome is looking for.
This turned out to be a problem with Mono. Mono uses BoringSSL in newer versions but it isn't turned on by default in older versions. On newer Linux distributions you can do export MONO_TLS_PROVIDER=btls but that didn't work for me because the gcc compiler on CentOS 6 (version 4.4) is too old and doesn't support align which is necessary to compile BoringSSL.
First I installed gcc 4.8 with instructions from here: https://gist.github.com/stephenturner/e3bc5cfacc2dc67eca8b
wget -O /etc/yum.repos.d/slc6-devtoolset.repo http://linuxsoft.cern.ch/cern/devtoolset/slc6-devtoolset.repo
sudo yum install devtoolset-2
scl enable devtoolset-2 bash
Then I downloaded the latest release package of mono from their website (currently 5.12.0.226): http://www.mono-project.com/docs/compiling-mono/linux/
wget https://download.mono-project.com/sources/mono/mono-5.12.0.226.tar.bz2
tar xvf mono-5.12.0.226.tar.bz2
cd mono-5.12.0.226
./configure --prefix=/usr/local
make
make install
Just in case, I did export MONO_TLS_PROVIDER=btls too, although I don't think it's necessary, but regardless if you look at the output at the end of ./configure it should tell you if BTLS is enabled.
This also fixed the same problem with recent Firefox update 60.0.0.2.
Im new to node js, im about to install a package via 'npm install', as you can see its 'ursa'.
So for now im stuck with this error C1083.
I use a 64bit maschine, OpenSSL is installed. Path of OpenSLL is
C:\OpenSSL-Win64
Error-Log
http://i.stack.imgur.com/CQSct.png
Microsoft Windows [Version 6.1.7601]
It seems your C++ compiler has problems finding the OpenSSL header files.
The Ursa GitHub page contains multiple issue topics about it not finding openSSL. There is a solution for ubuntu, but there is no general solution for Windows yet. I'd suggest asking for help there
I installed GitLab 6.6.5 via the omnibus package on Ubuntu 12.04 LTE. My question is will the Ubuntu OpenSSL heartbleed update cover the GitLab's installation? The installation has an embedded nginx that is installed. I have enabled SSL via the GitLab Omnibus Merge Request #66.
Having an embedded NGinX doesn't mean it won't use the /usr/bin/openssl installed on your system. (for instance, the ngx_http_ssl_module does require openssl)
If that openssl is 1.0.1g or 1.0.2, you won't have any issue.
openssl version
If not, it is easy enough to recompile it and install it.
To be sure, you can type:
ldd /path/to/nginx
That will give you the path of the openssl used by the binary nginx.
To get the full path, you can then use
readlink -f /path/to/libssl.so.1.0.0
Bruno adds in the comments:
It's probably more about /lib/*/libssl.so.1.0.0 than /usr/bin/openssl (which ldd should indicate indeed).
In principle, upgrading to the package with the fix and restarting NGinX should fix the issue.
Also note that the version numbers in distribution packages (e.g. Ubuntu) don't necessarily match the official version numbers exactly, because they tend to keep the same version number (for the same features), but backport the security patches
The OP crushedGrass points out in the comments Jacob Vosmaer (jacobvosmaer)'s commit "Update omnibus-software (CVE-2014-0160)", in omnibus-gitlab
so all I had to do was run a reconfiguration.
I believe both your and Bruno's feedback is spot on, there are just more dependencies that have to match up.
GitLab uses Chef cookbooks to configure the setup and I definitely do not know enough about it to modify it downstream.
Just so it is clear:
-> # ldd /opt/gitlab/embedded/sbin/nginx
...
libssl.so.1.0.0 => /opt/gitlab/embedded/lib/libssl.so.1.0.0 (0x00007fe3cf8f9000)
libcrypto.so.1.0.0 => /opt/gitlab/embedded/lib/libcrypto.so.1.0.0 (0x00007fe3cf520000)
...
Gitlab omnibus uses its own bundled OpenSSL. apt-get update will not update and protect an install of gitlab omnibus.
I'm trying to build and install the ZeroMQ libraries (2.1.11 cloned from GitHub) under Cygwin (on a Windows 7 system).
configure gives me this error message:
configure: error: cannot link with -luuid, install the e2fsprogs
package
which persists even after I install e2fsprogs (1.41.14-1).
Is this a sign that ZeroMQ needs a real Ext2 file system? Where did I go wrong?
You need to install the libuuid-devel package. (When getting a linker error about -lxyz, searching http://cygwin.com/packages for libxyz usually does the trick.)