19 replies to this topic

[jaSalta387]

Hello all,

I have just upgraded my ET-5000 to openpli 2.1, I used the nightly build of 12 February. Everything when smooth, with almost no problems. I wanted to use SCAM but it did not work "out of the box" after installing it with the plugin manager. So I had to go hands-on using a telnet connection. I experienced the following:

root@et5x00:~# /etc/init.d/softcam.scam start
/usr/bin/scam_3.60: error while loading shared libraries: libssl.so.0.9.7: cannot open shared object file: No such file or directory

I found a workaround by created a symlink to the existing libssl.so.0.9.8

root@et5x00:~# ln -s /usr/lib/libssl.so.0.9.8 /usr/lib/libssl.so.0.9.7

It was not good yet:

root@et5x00:~# /etc/init.d/softcam.scam start
/usr/bin/scam_3.60: error while loading shared libraries: libcrypto.so.0.9.7: cannot open shared object file: No such file or directory

I did the same trick as for the previous library:

root@et5x00:~# ln -s /usr/lib/libcrypto.so.0.9.8 /usr/lib/libcrypto.so.0.9.7

And voila, scam was up and running. It'd be nice that the bug is patched somehow.

[hemertje]

libcrypto.so.0.9.7 is allready a dependency from scam, so it should have worked if you installed it directly via our feeds

so did you install it from our feed or by hand?

[jaSalta387]

libcrypto.so.0.9.7 is allready a dependency from scam, so it should have worked if you installed it directly via our feeds

so did you install it from our feed or by hand?

I installed scam from the feed, that is with the plugin manager... so I think there is a bug.

[tacked]

This problem still exist Have install scam 3.60 from the feed and got the same error.

 

Fixed this way:

 

ln -s /usr/lib/libssl.so.0.9.8 /usr/lib/libssl.so.0.9.7

 

and

 

ln -s /lib/libcrypto.so.0.9.8 /usr/lib/libcrypto.so.0.9.7

Edited by tacked, 13 April 2013 - 12:05.

[littlesat]

It seems good old scam relies on good old libraries... (but the new ones are still fine).

Edited by littlesat, 13 April 2013 - 12:07.

[jor]

I currently use openpli6.2 and there is need to upgrade a viaccess card running scam3.60. I installed via openpli feed but when I run scam3.60 I get the message " error while loading shared libraries: libcrypto.so.0.9.7: cannot open shared object file: No such file or directory ". I tried the soplution with symlinks with no success. Any suggestions ???

[WanWizard]

This is an ongoing problem with antique binaries.

 

You could try

cd /usr/lib
ln -s libcrypto.so.1.0.2 libcrypto.so.0.9.7

and then hope the API and functionality is that far backward compatible...

[jor]

This is an ongoing problem with antique binaries.

 

You could try

cd /usr/lib
ln -s libcrypto.so.1.0.2 libcrypto.so.0.9.7

and then hope the API and functionality is that far backward compatible...

Unfortunately no luck. Any other ideas ??

[WanWizard]

Define no luck? You get an error message on the ln command? Or scam doesn't start?

 

If it doesn't work, you're out of luck, the scam binary needs to be compiled against the current libraries, and only the owner of the source code can do that.

[jor]

Define no luck? You get an error message on the ln command? Or scam doesn't start?

 

If it doesn't work, you're out of luck, the scam binary needs to be compiled against the current libraries, and only the owner of the source code can do that.

Sorry I was not precise. Scam is not starting with the message "error while loading shared libraries: libssl.so.0.9.7: cannot open shared object file: No such file or directory"

[WanWizard]

so did you make the symlink?

[mrvica]

then you have to do the same with libssl

ln -s libssl.so.1.0.2 libssl.so.0.9.7

[WanWizard]

And check what the current versions are, the question is about OpenPLi 6.2, not sure that is already using v1.0.2 (I'm running 7.0-rc locally).

[jor]

Thanks all for your suggestions. The current versions are 1.0.0. So after giving ln -s libssl.so.1.0.0 libssl.so.0.9.7 and ln -s libcrypto.so.1.0.0 libcrypto.so.0.9.7  the problem was solved and scam_3.60 running fine !!!

[Erik Slagter]

... for the time being, count on crashing sooner or later.

[jor]

... for the time being, count on crashing sooner or later.

Why ?? By the way, scam is not the softcam I prefer to use. I just used it trying to update my viaccess card.

[WanWizard]

Because sooner or later the API of the libraries will no longer be compatible. And then the symlink trick will no longer work, a recomplile is the only way to fix that.

 

Doesn't Oscam not update the card?

[jor]

Now I got it. No, the card still remains not updated even after using scam. At the past oscam had some issues to update this card, on the contrary scam update the card in a few minutes. So I guess that the provider stopped sending emms to update it because they want their subscribers to use the V5 or V6 cards.

[littlesat]

Swiss card... ? Then it is indeed Game Over....

[Erik Slagter]

Because sooner or later the API of the libraries will no longer be compatible. And then the symlink trick will no longer work, a recomplile is the only way to fix that.

That was not what I was referring to. I was referring to slight abi-changes between versions of shared libraries, where 99% of the functions keep the same definitions and run without problems and 1% of the functions have a changed definition (other number of parameters, other types of parameters etc.) and at least the calling program will get a nonsense reply, at worst the program will be aborted with a segfault.

 

So that's what I mean with "will crash sooner or later". I really think it's unwise.

Edited by Erik Slagter, 21 November 2018 - 19:37.