Hello,
I’m building an application that depends on openssl 1.0 version yet. I read in release notes that openssl 1.0 version was moved to legacy module.
So, I suppose that Suse15 will support openssl 1.0 until the end of 2019 because as says on openssl blog “Our current LTS release is 1.0.2, and it will be supported until the end of 2019.”.
My application is trying to load libraries with SONAME 1.0.0, but on SLED the libraries has already the new SONAME (1.1).
How SLED supports 1.0 yet? Should my installer require a dependency of openssl 1.0 ?
Note: When I try to use autocomplete on command “zypper install openssl” isnt listed any 1.0 version.
Best regards,
Pedro
Hi and welcome to the Forum 
The Legacy Module product is for SLES, not SLED, perhaps it would be better to switch (grab a developer free 1 year registration?) and then can install?
Can you reach this download (openssl 1.0.2p update)?
https://download.suse.com/Download?buildid=f4RctDutehw~
[QUOTE=malcolmlewis;56530]Hi and welcome to the Forum
The Legacy Module product is for SLES, not SLED, perhaps it would be better to switch (grab a developer free 1 year registration?) and then can install?
Can you reach this download (openssl 1.0.2p update)?
https://download.suse.com/Download?buildid=f4RctDutehw~[/QUOTE]
Thanks for quick reply malcolmlewis.
I just looked at https://www.suse.com/releasenotes/x86_64/SUSE-SLED/15/, is from SLED, so I suppose they commited a mistake on release notes on point 12.4.2.
I didnt understand very well your comment, let me try to be more clear.
We developed a product that uses OpenSSL 1.0.2 and we created an installer on SLES (It was possible install openssl-1_0_0 module on SLES machine).
Afterwards I have created a SLED VM to test the installer. Installation was ok, but when I run the application it returns the error:
app: error while loading shared libraries: libcrypto.so.1.0.0: cannot open shared object file: No such file or directory
With your reply I am thinking that my SLED15 clients wont be able run my application because openssl 1.0 is not supported. Is it correct?
By the way, I can access and download the resources from website that you pasted.
[QUOTE=plopes_aet;56533]Thanks for quick reply malcolmlewis.
I just looked at https://www.suse.com/releasenotes/x86_64/SUSE-SLED/15/, is from SLED, so I suppose they commited a mistake on release notes on point 12.4.2.
I didnt understand very well your comment, let me try to be more clear.
We developed a product that uses OpenSSL 1.0.2 and we created an installer on SLES (It was possible install openssl-1_0_0 module on SLES machine).
Afterwards I have created a SLED VM to test the installer. Installation was ok, but when I run the application it returns the error:
app: error while loading shared libraries: libcrypto.so.1.0.0: cannot open shared object file: No such file or directory
With your reply I am thinking that my SLED15 clients wont be able run my application because openssl 1.0 is not supported. Is it correct?
By the way, I can access and download the resources from website that you pasted.[/QUOTE]
Hi
So if you download the rpm and manually install, they will/should co-exist since they are shared libraries.
Re support, I would assume they will be unsupported since they relate to SLES, however I would suggest opening a Support Request to ask if they can be.
[QUOTE=malcolmlewis;56539]Hi
So if you download the rpm and manually install, they will/should co-exist since they are shared libraries.
Re support, I would assume they will be unsupported since they relate to SLES, however I would suggest opening a Support Request to ask if they can be.[/QUOTE]
Thanks for your response. I had to install Legacy Module and it worked.