On Apr 14, 2014, at 13:13 , LOKESH JANGIR <lk.jangi...@gmail.com> wrote:
> Hi Fedor, > > Yes i did not move this file out. and i can see the output of ls -la > /lib64/libcrypt.so.1 > libcrypt.so -> ../../lib64/libcrypt.so.1 > > > I complied openssl and it created this library files, > engines libcrypto.a libssl.a pkgconfig > > So now should i move this libcrypt.a file to /usr/lib64 folder and rename > this as .so ? You should not need to move any libraries around. Actually, you should not need to build your own openssl in the first place, since CVE-2014-0160 aka heartbleed has been fixed in openssl 1.0.1-4ubuntu5.12. If you have just built openssl 1.0.1g to fix that, and you've previously use the openssl libraries supplied by Ubuntu, reinstall the openssl package using apt-get install --reinstall openssl or aptitude reinstall openssl, and rebuild your apache and mod_ssl (if you tried to re-build them against your openssl 1.0.1g, which does not appear to be the case). To build openssl dynamically, you have to "make build-shared", the .a files are static libraries and useless at runtime, you need .so files. You'll also have to post complete error messages, not only from the console, but possibly from the apache error_log as well. rainer______________________________________________________________________ OpenSSL Project http://www.openssl.org Development Mailing List openssl-dev@openssl.org Automated List Manager majord...@openssl.org
