[openssl-users] OpenSSL 1.1.1 release timeframe

[Jayalakshmi bhat]

Hi All,

Please can any one let me know the release date or time line for OpenSSL
1.1.1?

Regards
Jayalakshmi
-- 
openssl-users mailing list
To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-users

Re: [openssl-users] Build from source; library not found?

[Hiran Chaudhuri]

I just verified. The required shared libraries and runpath settings are part of 
the dynamic section in elf files. 

readelf -d openssl 

displays a runpath, while 

readelf -d libssl.so.1.0.0 

does not show a runpath. 

Therefore my test was wrong. I cannot check shared libraries directly. 

 Am 17-May-2017 16:40:40 +0200 schrieb hiran.chaudh...@mail.de: 
Now this is interesting. Yes, openssl can find both the libraries libssl and 
libcrypto. Would that imply that rpath is only a setting for application 
(executables) but not for shared libraries? In that case the test I tried would 
be totally meaningless.   Hiran
-- 
openssl-users mailing list
To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-users

Re: [openssl-users] Build from source; library not found?

[Hiran Chaudhuri]

Hi Richard.
   Thank you for the fast response. 

 Am 17-May-2017 15:40:27 +0200 schrieb levi...@openssl.org: 
The are two ways to handle this. One is with the usual setting of
 LD_LIBRARY_PATH:

 $ LD_LIBRARY_PATH=`pwd` ldd libssl.so.1.0.0 Yes, this seems to work. Somehow 
I'd like to avoid having to tell every user to use the correct settings.   
The other is, when you compile your application, to use
 -Wl,-rpath,/prefix/openssl/lib Where would these options typically go? One of 
the applications is curl, which worked when I set 
"LDFLAGS=-R/prefix/openssl/lib" when doing configure/make/make install in the 
curl build directory. One of the applications is Apache httpd, which seems to 
not work when doing the same. So I'd definitely try your suggestion.   
Incidently, I think that when you do this, you'll find that it finds
 your libraries all right:

 $ ldd /prefix/openssl/bin/openssl Now this is interesting. Yes, openssl can 
find both the libraries libssl and libcrypto. Would that imply that rpath is 
only a setting for application (executables) but not for shared libraries? In 
that case the test I tried would be totally meaningless.   Hiran
-- 
openssl-users mailing list
To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-users

Re: [openssl-users] Build from source; library not found?

[Richard Levitte]

In message <20170517130805.7600d40...@smtp03.mail.de> on Wed, 17 May 2017 
15:08:05 +0200, Hiran Chaudhuri  said:

hiran.chaudhuri> Hi there.
hiran.chaudhuri> I have been building Openssl for quite some time now. Just 
recently I
hiran.chaudhuri> switched to shared mode that will also create shared libraries.
hiran.chaudhuri> What I am wondering about: After configure/make/make install I 
find
hiran.chaudhuri> the expected libraries in the desired output directory. Why 
can ldd
hiran.chaudhuri> not resolve a librarie's dependencies? The target file is just 
in the
hiran.chaudhuri> same directory!
hiran.chaudhuri> user@server:/prefix/openssl/lib> ls
hiran.chaudhuri> engines libcrypto.a libcrypto.so libcrypto.so.1.0.0 libssl.a 
libssl.so
hiran.chaudhuri> libssl.so.1.0.0 pkgconfig
hiran.chaudhuri> user@server:/prefix/openssl/lib> ldd libssl.so.1.0.0
hiran.chaudhuri> linux-vdso.so.1 => (0x7ffdae1fb000)
hiran.chaudhuri> libcrypto.so.1.0.0 => not found
hiran.chaudhuri> libdl.so.2 => /lib64/libdl.so.2 (0x7f8173425000)
hiran.chaudhuri> libc.so.6 => /lib64/libc.so.6 (0x7f81730a9000)
hiran.chaudhuri> /lib64/ld-linux-x86-64.so.2 (0x7f81738ad000)
hiran.chaudhuri> user@server:/prefix/openssl/lib>
hiran.chaudhuri> Is this normal behaviour? Or is it because I entered a prefix 
that is
hiran.chaudhuri> not part of the system's default lib path?

That last question is the correct guess.  /etc/ld.so.conf will tell
you what your default paths are (and if it includes other files, so
will they).

The are two ways to handle this.  One is with the usual setting of
LD_LIBRARY_PATH:

$ LD_LIBRARY_PATH=`pwd` ldd libssl.so.1.0.0

The other is, when you compile your application, to use
-Wl,-rpath,/prefix/openssl/lib

Incidently, I think that when you do this, you'll find that it finds
your libraries all right:

$ ldd /prefix/openssl/bin/openssl

The reason is that the application has been built with said -rpath

A last note: with OpenSSL 1.1.0 and on, rpath isn't automatically
applied to the openssl application, but is a matter of extra
configuration arguments.

Cheers,
Richard

-- 
Richard Levitte levi...@openssl.org
OpenSSL Project http://www.openssl.org/~levitte/
-- 
openssl-users mailing list
To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-users

[openssl-users] Build from source; library not found?

[Hiran Chaudhuri]

Hi there.   I have been building Openssl for quite some time now. Just recently 
I switched to shared mode that will also create shared libraries. What I am 
wondering about: After configure/make/make install I find the expected 
libraries in the desired output directory. Why can ldd not resolve a librarie's 
dependencies? The target file is just in the same directory!   
user@server:/prefix/openssl/lib> ls
engines libcrypto.a libcrypto.so libcrypto.so.1.0.0 libssl.a libssl.so 
libssl.so.1.0.0 pkgconfig
user@server:/prefix/openssl/lib> ldd libssl.so.1.0.0
 linux-vdso.so.1 => (0x7ffdae1fb000)
 libcrypto.so.1.0.0 => not found
 libdl.so.2 => /lib64/libdl.so.2 (0x7f8173425000)
 libc.so.6 => /lib64/libc.so.6 (0x7f81730a9000)
 /lib64/ld-linux-x86-64.so.2 (0x7f81738ad000)
user@server:/prefix/openssl/lib>   Is this normal behaviour? Or is it because I 
entered a prefix that is not part of the system's default lib path?   Hiran
-- 
openssl-users mailing list
To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-users