Oscam

[abu baniaz]

The version of libcrypto was updated a long time ago to fix a bug where devices where being hacked. More than likely libcrypto compat needs an edit to crate a symlink.

[Trial]

Hi,
does ViX create symlinks to 0.9.7 and 0.9.8? At least it was the case when the update to 1.x.x was made because of these kinds of problems.

ciao

[lincsat]

There is quite a long thread about this problem on another forum. Basically libcrypto 0.9.8 is required and can be ftp'd to usr/lib and attribute 755. Then oscam will start.

I added a symlink to the existing libcrypto and patched the SoftcamManager to double the ulimit size and now all OScam's I've tried do run fine

[spanner123]

I added a symlink to the existing libcrypto and patched the SoftcamManager to double the ulimit size and now all OScam's I've tried do run fine

Great work. Maybe you should post your fix on the other forum as lots of people having problems!

Edit: I have just quoted you on the other forum hope that's ok?

Sent from my SM-G930F using Tapatalk

[abu baniaz]

Hi,
does ViX create symlinks to 0.9.7 and 0.9.8? At least it was the case when the update to 1.x.x was made because of these kinds of problems.

ciao

root@tmnanosem2:~# opkg install libcrypto-compat-0.9.7
Package libcrypto-compat-0.9.7 (1.0-r0) installed in root is up to date.

root@tmnanosem2:~# opkg install libcrypto-compat-0.9.8
Couldn't find anything to satisfy 'libcrypto-compat-0.9.8'.
Unknown package 'libcrypto-compat-0.9.8'.
Collected errors:
* opkg_solver_install: Cannot install package libcrypto-compat-0.9.8.

root@tmnanosem2:~# opkg install libcrypto-compat-1.0.0
Package libcrypto-compat-1.0.0 (1.1-r0) installed in root is up to date.


Looks like we have an issue with 0.98. Solo 4k had same problem. All it is is a symlink installer.

[abu baniaz]

The symlinks can be added by the following command

ln -sf /usr/lib/libcrypto.so.1.0.2 /usr/lib/libcrypto.so.0.9.7
ln -sf /usr/lib/libssl.so.1.0.2 /usr/lib/libssl.so.0.9.7
ln -sf /usr/lib/libcrypto.so.1.0.2 /usr/lib/libcrypto.so.0.9.8
ln -sf /usr/lib/libssl.so.1.0.2 /usr/lib/libssl.so.0.9.8
ln -sf /usr/lib/libcrypto.so.1.0.2 /usr/lib/libcrypto.so.1.0.0
ln -sf /usr/lib/libssl.so.1.0.2 /usr/lib/libssl.so.1.0.0

[lincsat]

Great work. Maybe you should post your fix on the other forum as lots of people having problems!

Edit: I have just quoted you on the other forum hope that's ok?

Sent from my SM-G930F using Tapatalk

I have posted in a couple of forums but I've no problem with you quoting me elsewhere M8.

From within /usr/bin/ I used the

ln -sf libcrypto.so.1.0.2 libcrypto.so.0.9.8

Then with a text editor, did a search and replace in the SoftcamManager.py to replace ulimit -s 512 with ulimit -s 1024

[abu baniaz]

Also how come the OpenViX feed doesn't always have the latest version of OSCam when it becomes available?

Posting answer to your question in this thread.

We use the name "oscam latest" so that the softcam manager/settings uses the same name. If oscam on Vix feeds is updated and user updates image, the newer one will be used without user having to change anything

oscam-latest = version defined in bitbake file used by us in 4.2 branch. 4.3 branch has auto rev

Arm
https://github.com/oe-alliance/oe-al...test-arm.bb#L9

Mips
https://github.com/oe-alliance/oe-al...t-mipsel.bb#L9

Oscam history is here
http://www.streamboard.tv/svn/svnsty...arget=//trunk/

It does not mean the latest available oscam. Sometimes issues arise so we don't always use the "latest" version. As you may have seen from willo's thread, he was unable to download the source files, so the image build he was trying failed, but anyhow, that was after a succesful build by us. I think other teams use Persian Prince's repo as it is more reliable.

OpenVix does not do daily builds. You will have to wait until a build is run for any plugins on the plugin server to be updated. We already have 11517 on our server