Hi,
With the recent discovery of OpenSSL vulnerabilities, I've been reviewing the versions of Nginx and OpenSSL / libssl used on our MyTardis server.
The Chef recipe installed:
/etc/apt/sources.list.d/nginx-stable-lucid.list
but not
/etc/apt/sources.list.d/nginx-stable-precise.list
Is there any reason why MyTardis needs to use Nginx's Lucid package on Precise?
Running "ldd /usr/sbin/nginx | grep ssl" shows that our Nginx is linking against the libssl 0.9.8 shared library (quite an old version of libssl). As a result of this, I had to jump through an extra hoop to get this libssl library patched for the latest OpenSSL vulnerability. I installed Ubuntu's Lucid .deb package for libssl 0.9.8 to patch the vulnerability, because the Precise .deb package for libssl 0.9.8 hasn't yet been patched:
So our MyTardis server is now listed as safe with regard to the recent OpenSSL vulnerabilities, however, I'm thinking maybe it's time to upgrade to an Nginx package which uses a more recent version of libssl, e.g. 1.0.1?
If anyone else has faced similar issues, can you comment on whether it's OK to replace the Chef-installed "/etc/apt/sources.list.d/nginx-stable-lucid.list" with "/etc/apt/sources.list.d/nginx-stable-precise.list" ?
Thanks,
James