Forums

Well I've moved from RC to Release and now (again) Scam will not start because it misses the libcrypto compat, and libcrypto ssl.

I've installed that manually - also made a symlink, and still no go...

Any help for this?

That's bound to happen. The Scam binary hasn't been updated in dogs years, symlinking only works if the newer library is still API compatible, eventually your luck will run out. We've started to remove the old junk from the feeds.

 

What can Scam do that Oscam can't (and I'm not interested in illegal activities)?

Quick card update with Scam is way better than with Oscam.

In what way better? Isn't an update an update? Not trying to be difficult, just trying to understand the requirement.

Oscam updates only when you're using the card... Scam (and other softcams) as soon there exist an EMM...

Doesn't that imply that you need to tune into a channel served by the card to receive EMM's for that card? I assume Scam doesn't pull these EMM's out of thin air?

Oscam needs fiddling to engage a card, Scam is - insert a card, wait a few seconds - good to go.

What do you mean with 'fiddling to engage a card'?

Well different card - different setup for oscam, and oscam with more cards to reed for an update doesn't (more times than sometimes) does the job.

Scam is waaaaaayyyy simpler. 

But Oscam still works, and Scam doesn't. Also, more and more boxes are moving to ARM SoC's, for which Oscam is the only option.

this did the trick before, just two symlinks in /usr/lib

ln -s libcrypto.so.1.0.0  libcrypto.so.0.9.7

ln -s libssl.so.1.0.0 libssl.so.0.9.7

 

After linking again (file exists) I get same error mesage.

root@vusolo2:~# /usr/bin/scam: error while loading shared libraries: libssl.so.0.9.7: cannot open shared object file: No such file or directory

what are the versions of libssl and libcrypto in release 6.0

ls -al libssl*

ls -al libcrypto*

lrwxrwxrwx    1 root     root            15 Oct 31 14:28 libssl.so.0.9.7 -> libssl.so.1.0.0

lrwxrwxrwx    1 root     root            18 Oct 30 14:33 libcrypto.so.0.9.7 -> libcrypto.so.0.9.8

where are the big files libcrypto.so.1.0.0 and  libssl.so.1.0.0, are they missing, I have hier in OpenPLi4

 

ls -al libcrypto*
lrwxrwxrwx    1 root     root            18 Oct 31 14:08 libcrypto.so.0.9.7 -> libcrypto.so.1.0.0
lrwxrwxrwx    1 root     root            18 Oct 14 19:34 libcrypto.so.0.9.8 -> libcrypto.so.1.0.0
-rwxr-xr-x    1 root     root       1773328 May  5  2016 libcrypto.so.1.0.0

 

ls -al libssl*
lrwxrwxrwx    1 root     root            15 Oct 31 14:06 libssl.so.0.9.7 -> libssl.so.1.0.0
lrwxrwxrwx    1 root     root            15 Oct 14 19:34 libssl.so.0.9.8 -> libssl.so.1.0.0
-rwxr-xr-x    1 root     root        356316 May  5  2016 libssl.so.1.0.0
 

6.0-release should have

root@hd2400:/usr/lib# ls -al libcrypto*
-rwxr-xr-x    1 root     root       1765488 Oct 14 00:42 libcrypto.so.1.0.0
root@hd2400:/usr/lib# ls -al libssl*
-rwxr-xr-x    1 root     root        356504 Oct 14 00:42 libssl.so.1.0.0
root@hd2400:/usr/lib# 

then soft links will do the job, see above

No go with pyro. Cccam OK, mgcamd NOK.
(just for info)
Edited by zeros, 31 October 2017 - 17:21.

No go with pyro?

what do you mean, copy scam in /tmp and type ./scam

I mean, if you build with pyro branch (the most new and not public image), then mgcamd did not go to work (not in any way). With the develop and all lower branches OK. But the Cccam OK also with pyro