readme

这是一个LINUX环境的 VDR 插件源代码,可支持Irdeto, Seca, Viaccess, Nagra, Conax & Cryptoworks等CA系统的读卡、共享等操作。

This is a "plugin" for the Video Disk Recorder (VDR).

See the file COPYING for license information.

Description: SoftCAM for Irdeto, Seca, Viaccess, Nagra, Conax & Cryptoworks

-----------------------------------------------------------------------



WARNING! This is the SC plugin development branch !!

This is a beta release. We encourage everybody to try this release, nevertheless
it should be used under controlled conditions.

Feel free to put your bugreports, suggestions and/or wishes to the 4free or DVBN
board. A bugreports should at least include the console log.



What is it ?
------------

First: Most certainly it's not legal to use this software in most countries of
the world. But probably you already know this...

SC means softcam, which means a software CAM emulation.

The main development goal for this branch is a full-featured implementation
without the needs to patch VDR. Recent changes in the new VDR development branch
opened a possibility for that.

The plugin captures the DVB devices in an early startup stage of VDR startup
(before VDR itself has got access to them) and makes VDR believe that there is
another CAM connected to the device. This CAM is emulated from the plugin by
providing a cut-down EN50221 interface for communication with the VDR core. From
VDR views there is no difference between a real hardware CAM and the emulated
CAM. 

The plugin decrypts the scrambling codewords from the incomming ECM stream. The
actual descrambling of the video stream is either done by the ECD chip on
full-featured DVB cards or with the included FFdecsa implementation on budget
cards.

This piece of software is originaly based on (and still contains code from)
mgcam (a standalone CAM emulation). Many thanks to the (anonymous) author for
his really fine piece of software :-)



Requirements
------------

* DVB driver from dvb-kernel 2.6 or 2.4 branch with applied patches
* a patched firmware version 2620 or newer
* VDR 1.5.0 or newer (VDR 1.4.6+ in compatibility mode, see 1.4.x setup section)
* Openssl package version 0.9.7 or newer



How to setup ?
--------------

First you should start with a recent dvb-kernel driver (cvs recomended). Copy
the patched firmware in place and apply at least the dvb-cwidx patch. Make sure
that you use a patched firmware if you intend to use the plugin together with a
full-featured DVB card. You definitely need a patched firmware in this case, but
only recent versions support concurrent recording! Recompile the driver, unload
the modules, install the new ones and reload the DVB driver. If you suffer from
ARM crashes, add "hw_sections=0" while loading the dvb-ttpci module.

Contrary to older plugin versions you MUST NOT apply any patches to the VDR core
(neither vdr-sc nor ffdecsa/softcsa).

You must have installed the openssl development files. For most distributions
this means to install openssl-devel package. You should use a openssl package
with AES and IDEA enabled, as support for openssl without these will be removed
in the near future.

Now follow the VDR instruction to compile plugins (make plugins). Beside the
core plugin (libvdr-sc.so), the make process (if successfull) creates an
additional shared library object for every supported system (libsc-*.so). You
can enable/disable individual systems by adding or removing the shared library
from your VDR plugin lib directory.

Starting with version 0.5.8 all make compile time options (e.g. IRDETO=1) except
DEFAULT_PORT have been removed!

Note that in combination with other plugins which create devices (e.g.
softdevice) it's essential that this plugin is loaded before any of these
plugins, i.e. as a rule of thumb put this plugins first on the VDR commandline.
The plugin will fail on startup if the plugin load order results in mismatched
device numbering inside VDR.

Note that some budget card drivers provide a CA device too. This might make VDR
and the plugin detect the card as a full-featured card, thus disabling FFdecsa.
You should use commandline option -B to force detection as a budget card in such
a case.

For testing purpose you should start VDR in foreground always. The plugin gives
a lot of additional information to the console. This may be helpful in case it
doesn't work at once.



How to setup for VDR 1.4.x ?
----------------------------

Additional to the points mentioned above, you have to patch the VDR core with
the supplied patch (vdr-1.4.x-sc7.diff). Recompile VDR and use the new binary.
Patches from older SC releases are not going to work.

Even with VDR 1.4.x you don't have to use a softcsa/ffdecsa patch.

Activating/deactivating DVB cards in the plugin setup menu needs a VDR restart
to take effect.



Pre-compiled libraries
----------------------


There is the possibility that encryption systems are provided in binary, pre-
compiled only form. During make process, all pre-compiled libraries are copied
to your VDR plugin lib directory.

Please be aware, that pre-compiled libraries are more or less bound to the hard-
& software configuration they have been build on. Currently the build system is
Intel 32bit, gcc 3.2.2, glibc 2.2.5. If your system differs too much, it may be
impossible to use the pre-compiled libraries.

Obviously, pre-compiled libraries cannot be exchanged between different SC
and/or VDR API versions. Be aware that if you patch your VDR core and this patch
involves changes to header files (*.h) this might change the VDR API even if the
API version number hasn't changed. This may lead to silent malfunction/failure
of pre-compiled libraries. In particular you should stay away from thread.h and
tools.h as classes from there are used at many, many places.

The naming scheme for the libraries is libsc-<MODULE>-<SCAPI>.so.<APIVERSION>,
e.g. libsc-cardclient-2.so.1.3.47



CAID and VDR CICAM setup
------------------------

The activation of the SC is controlled by your CICAM setup. As general setup
(which is not SC specific) you should leave the CA values (in channels.conf)
set to zero and let VDR's channel scanner (autopid) fill in the correct values.
Don't touch the CA values afterwards.
In the plugin setup menu, you now have to specify for which DVB cards the SC
should be activated. The first two cards can be setup from the menu. If you
need more, you can edit the setup.conf file manualy and add up to 10 cards.

A real hardware CAM normaly knows which CAIDs it supports. With SC the situation
is a bit different. There is support for a wide range of encryption system and
cardclients. This results in a huge number of supported CAIDs, but for most of
them it's uncertain if SC will actualy be able to decrypt a channel for them.
On the other hand VDR limits the number of supported CAIDs to 16 for a CAM slot,
so SC is able to announce a small number of CAIDs only. This is not as bad as it
sounds, as VDR will try a CAM if ANY of the channel CAIDs matches the CAIDs
announced by the CAM.
On startup and at regular intervals the plugin scans the channels list and
builds a chain of CAIDs. The CAIDs are assigned to the simulated CAM. 

To reduce the number of CAIDs SC has to deal with, you should obey some rules:
-Remove all libsc-* files for encryption system which you don't intend to use
 (e.g. SHL seems pretty useless nowadays).
-When using a cardclient, be as precise as possible with the CAID/MASK values in
 the cardclient.conf file. Using wide open 0000/0000 is deprecated.
-Add CAIDs which you cannot use due to lack of keys to the SC.CaIgnore setting.