source of cccam ?!!

How about applying symbolic links to old-new versions of libraries ? :) Backward compatibility should almost always be maintained. Only new features are added and BUGs are being fixed. There will be little change in the output or use of functions in libraries.

If it is a set-top-box and not some x86 machine with full Linux, so if there is no conflict of many other dependencies on the old library, then it is sufficient to use symbolic links.

In the case of set-top boxes and Softcams, it is common practice to use symbolic links to older libraries that are already removed from the system, but sometimes cccam or oscam (or other softcam) still require them.

Verify that your links are created correctly:

ls -al /usr/lib/libcrypt*

This is what it looks like in OpenATV 6.3 Enigma:

root@formuler3ip:~# ls -al /usr/lib/libcrypt*
lrwxrwxrwx    1 root     root            17 Jun  9 20:28 /usr/lib/libcrypt.so.1 -> libcrypt.so.1.1.0
-rwxr-xr-x    1 root     root        137664 Jun  9 20:28 /usr/lib/libcrypt.so.1.1.0
lrwxrwxrwx    1 root     root            18 Jun 10 20:20 /usr/lib/libcrypto.so.0.9.7 -> libcrypto.so.1.0.2
lrwxrwxrwx    1 root     root            18 Jun 10 20:20 /usr/lib/libcrypto.so.1.0.0 -> libcrypto.so.1.0.2
-rwxr-xr-x    1 root     root       1774316 Jul 19 19:18 /usr/lib/libcrypto.so.1.0.2

In order to achieve the above, creating links in the right way is as follows:

cd /usr/lib
ln -s libcrypt.so.1.1.0 /usr/lib/libcrypt.so.1

# then check it again :
ls -al libcrypt*

Or try the following commands ... of course only for testing purposes ... create and then delete the "libscrypt.so.2" symbolic link:

root@vusolose:/usr/lib# ln -s libcrypt.so.1.1.0 /usr/lib/libcrypt.so.2
root@vusolose:/usr/lib# ls -al /usr/lib/libcryp*
lrwxrwxrwx    1 root     root            17 Jun 10 02:35 /usr/lib/libcrypt.so.1 -> libcrypt.so.1.1.0
-rwxr-xr-x    1 root     root        137664 Jun 10 02:35 /usr/lib/libcrypt.so.1.1.0
lrwxrwxrwx    1 root     root            17 Oct 10 00:15 /usr/lib/libcrypt.so.2 -> libcrypt.so.1.1.0
lrwxrwxrwx    1 root     root            18 Jun 11 05:00 /usr/lib/libcrypto.so.0.9.7 -> libcrypto.so.1.0.2
lrwxrwxrwx    1 root     root            18 Jun 11 05:00 /usr/lib/libcrypto.so.1.0.0 -> libcrypto.so.1.0.2
-rwxr-xr-x    1 root     root       1774316 Jul 19 20:00 /usr/lib/libcrypto.so.1.0.2

root@vusolose:/usr/lib# unlink libcrypt.so.2
root@vusolose:/usr/lib# ls -al /usr/lib/libcryp*
lrwxrwxrwx    1 root     root            17 Jun 10 02:35 /usr/lib/libcrypt.so.1 -> libcrypt.so.1.1.0
-rwxr-xr-x    1 root     root        137664 Jun 10 02:35 /usr/lib/libcrypt.so.1.1.0
lrwxrwxrwx    1 root     root            18 Jun 11 05:00 /usr/lib/libcrypto.so.0.9.7 -> libcrypto.so.1.0.2
lrwxrwxrwx    1 root     root            18 Jun 11 05:00 /usr/lib/libcrypto.so.1.0.0 -> libcrypto.so.1.0.2
-rwxr-xr-x    1 root     root       1774316 Jul 19 20:00 /usr/lib/libcrypto.so.1.0.2

Hello.

In that case, I only find that the dude who invented or compiled the above Cccam deserves the punishment of shame :). I wonder what the reason was to cancel compatibility.

Linux is getting worse than Windows. I understand dependency on kernel versions, but I don't understand dependency on library versions. Any scared developer can't program some of the code himself, so will he use the features of the 2.0.0 library? :) New libraries are suitable for use in full-featured Linux systems and can be used there for large projects (eg dvb headend). I do not understand when someone in such a small thing as Cccam has to use the latest libraries or a newer Linux kernel system. These developers are a shame to other developers because they absolutely do not think at all.

This is the same as when we design new applications and games, basically only for the new Android 10 and not older versions. Only apps and drivers for Windows 10 and not for older versions of Windows. Apps and drivers and modules only for linux kernel 5.4 and no other - ie. without compatibility in older versions.

In the textbook for beginners - developers for Android systems, at the beginning of the book reads:

Try to keep the compatibility with the oldest version possible! Otherwise, no one will use your app.

please link to download cccam source code

cccam source code is private and not avaliable