THe CCcam.cfg in German is certainly completely from time to time interesting:
# Explanation: # All that stands in a line after a # is ignored by CCcam and is used only for commenting # or override a setting. If a # CCcam setting, F: or C: suppose Line, the # must be removed. # All lines have the # behind the no space in this config are # examples for a possible setting. <span id="more-133"> </ span> # # In some settings you have to turn on an option to "on" or "off". Depending on the setting you choose either # 1 or yes for "on" or 0 or no for "off". Whether # you have to use in a particular setting 0/1 or yes / no, can be found in the commentaries of #. # # When a hop is defined as the removal of the card. Cards that are stuck in our Box # for us to Hop0. Cards that are stuck in the box of a friend to us directly # connected for us to hOP1. Cards has this friend on # hOP1, reach us on HOP2. And so on. The closer the card is, the better and faster # it can deliver the required CWs. So it makes no sense # cards from Hop4 or use 5 because these had been wandering through too many # server until they come to us through. # # VERY IMPORTANT: # THE CARD SHARING DOES NOT COUNT THE MASS OF CARDS IN SHARE, BUT THE QUALITY #! DEAR 2 GOOD CARD OF A PROVIDER, AS SLOW ON 20 HOP4 or 5 # TOO MANY CARDS AND UNNECESSARY BURDEN TO SHARE LEAD TO WORSE # SWITCHING, unnecessary network TRAFFIC AND FREQUENT LOSS UP TO # SYSTEM CRASH. # Note to the limitations in the C: Lines. (See examples below) # # To set this config necessarily an editor must be used, which # the Linux format in reserves. Windows users, I recommend Proton32. # Linux users simply take their favorite editor. # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # friends # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # Here we take friends who are allowed to connect to us, so cards are # to get us and / or access to our key File should get. # Parts of the keyfiles (default = 1), EMM allow (default = 1), and optionally # the down Share Limit per Share (Default = No limit), and optionally # the down Share Limit per Share based on caid: id: sid # and, optionally, the time window in which the share is valid and optionally a # hostname or an IP address to which access should be restricted. # If no time window we selected 24 hours a day is geshared. # Emus are only one hop further geshared, even if no limit has been set #. # # The maximum length of the user name is 20 characters. # The password length is unlimited. # # The user name is not an IP or host name. It is in the Q: Line # only to access to our CCcam server. # # F: <Username> <Password> <uphops> <Emus sharen> <EMM erlauben> ({caid: id (: downhops), caid: id (: downhops), ...} {caid: id: sid, caid: id: sid, ...} {start time end time, ...}) hostname / IP address # # examples of different options: # # F: user1 pass1 # # user1 gets all the cards from us, up to 5 hops away from us. # (Our local card / s + virtual cards, which are a maximum of 5 hops away). He can give our cards to his friends # on. It can also get keys from our key file (if it is a 'yes' behind his C: has) # and he is allowed to send us (EMM updates for our cards). # # F: user2 pass2 0 1 0 {0100:000080, 0622:000000:1, 0500:000000:2} # # user2 gets only our local cards, but not the 0100:000080. Our 0622:000000 # map / n he can only use for yourself (1 hop down) # and 0500 cards for himself plus one additional hop on. (2 hops down) # He also has access to the keys of our keyfiles, and may we not send EMM. # # F: user3 pass3 5 0 1 {0:0:3, 0100:000080:1} # # user3 gets all cards to a maximum of 5 hops away from us # and is entitled to give these cards 2 hops behind further . # He is not entitled to the 0100:000080 to give to other users on. # He gets no keys from our key file, and it can send us EMM. # # F: user4 Pass4 5 0 1 {0:0:4, 0100:000080:1} {df} # # user4 0100:000080:15 gets all cards that are maximum of 5 hops away from us # and is entitled to these cards behind to continue to give 3 hops. # He is not entitled to the 0100:000080 to give to other users on. # He is not authorized to view the channel 0100:000080:15 df. (He gets it, at least not by us) # # F: user5 pass5 4 0 1 {} {} {12:00 to 17:00, 19:00 to 20:00} # # user5 gets all cards at most 4 hops are away from us. # The share is limited to the period 12:00 to 17:00 clock and 19:00 to 8:00 p.m. clock. # Outside this time window are not sent CWs to the user. # # # F: user6 pass6 3 1 1 {} {} {} 192.168.1.1 # # user6 gets all cards that are a maximum of 3 hops away from us. # It may only connect from the IP 192.168.1.1. # # Important: # In the F: line can be limited to very simple as far as our cards can be passed on. # If many requests are made on our cards, so this makes our cards obviously slow # and it can lead to dropped frames (freezers) may occur. This is happening very quickly at NDS cards. # In order for our friends, our cards can not pass too far, we limit the Reshare level. # Behind every F: Line, we use the general limitation in the {}. We assume zero as a placeholder for # CAID and ID (0 = all). An example for that we see earlier in the Q: Line # user3. Behind its F: Line is located in the {} "0:0:3". This means that all of our cards # server may be passed only 3 hops. The first hop is user3, the second hop are # all users that are connected to user3, the third hop, all users who are connected to the users of # user3. Can # It is easily seen how quickly the number of users for our cards by this snowballing # increase. I recommend the Reshare on 2 hops limit. So {0:0:2}. # This can also be in the "GLOBAL LIMITS" Settings later in this config for all # F: Set lines at once. Thus, this is in the R: Lines are no longer necessary. # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # compounds # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # Here we take a server from which we want and / or Keys get tickets. # So the friends for us in their config a F: Line have entered. # At the end to the emu of the peer to use "yes" with. (Non Public Private Key / Emu, ...) # This only works with matching F: line in the config of the peer. # Optional limits just like in the F: line, but for incoming shares. (Ignore shares that are located more than X hops) # # # C: <hostname> <Port> <Username> <Password> <Keyfile friend with benutzen> ({caid: id (: uphops), caid: id ( : uphops), ...}) # # Note: if {} limits are set, can <Keyfile Friend erwünscht> not be omitted. # It must be stated then yes or no! # # Examples: # # C: to use server1.dyndns.org 12000 user1 pass1 # Connects to a CCcam server without the emu with the server. # # C: 192.168.1.2 12000 user2 pass2 yes # Connects to a CCcam server and the Emu server is used with. (If allowed by the server) # # Important: # In order not to get many cards that only burden our Share and anyway not work properly # We limit behind every C: Line the distance from which we get our cards. # We do this similarly to the Reshare level limit in the F: line (see above). # At the beginning, when we have yet to build up our share and are connected only to a few servers, # it is still useful maps from Hop 3, may be obtained even hop 4. # Once we're sorted but better, so you should only cards from Hop 2 are related. # This works easily with 0:0:2 in {} after each C: line to limit on Hop 2 or # 0:0:3 to limit on hop 3. A yes or no for <Keyfile Friend erwünscht> before {} may be used in the C #: Line but then not be forgotten! To use 192.168.1.2 12000 user3 pass3 no {0:0:2} # Connects to a CCcam server without the emu with the server: # # C. # Only cards are accepted that are more than two hops away. # # If we have 3 Vollabo card of a provider in one hop in our share, so we are well served by this provider # and need any more cards from this provider. Therefore, we can refuse to accept these cards # of distant hops. To use # Connects to a CCcam server without the emu server with # # C: server2.dyndns.org 12000 user4 Pass4 no {0:0:2 4:1, d22}. # Only cards are accepted that are more than two hops away. # There are no more cards of d22: accepted 4 that are further away than one hop. # CCcam can also be used as client to other servers connect card # This means that up CCcam can also pick up from these servers Card cards. But CCcam itself can be no # cards to a server. # # Dbox2 User must use NewCS to Show off their card. Since CCcam was not written for Dbox2 # can not be read directly by CCcam and NewCS must therefore take this and pass the # map then to CCcam further cards in the Dbox. # # Syntax to connect to a Newcamd / NewCS server: # # N: <IP> <Port> <Username> <Password> <Description Key(14byte)> <Entfernung to map in hops (Standard: 1)> <Tarneinstellung ( Default: 0)> # # Examples: # # N: 127.0.0.1 10000 dummy dummy 01 02 03 04 05 06 07 08 09 10 11 12 13 14 # # Add a newcamd card, which is 2 hops to the share list: # # N: 127.0.0.1 10000 dummy dummy 01 02 03 04 05 06 07 08 09 10 11 12 13 14 2 # # When MGcamd camouflaged on newcamd server log: # # N: 127.0.0.1 10000 dummy dummy 01 02 03 04 05 06 07 08 09 10 11 12 13 14 1 1 # # Tarneinstellungen: 0 = off, 1 = MGcamd new, 2 = MGcamd old, 3 = Evocamd, 4 = Generic # syntax for connecting to a server Radegast # # R: <IP> <Port> <caid> <pid> <Entfernung to map in hops (Standard: 1)> # # Example: # # R: 127.0.0.1 678 0100 0000 80 # syntax for connecting to a server Camd3 # # L: <IP> <Port> <Username> <Password> <caid> <pid> <Entfernung to map in hops (Standard: 1)> # # Example: # # L: 127.0.0.1 567 dummy dummy 0100 000080 # syntax for connecting to a Gbox Server # # G: <eigenes Passwort> <My hostname> <My Port> <Peer Passwort> <Peer hostname> <Peer Port> # # Optional are limitations just like in the C: Line supports ignore (Shares, # the more than X hops are removed) {caid: id (: uphops), caid: id (: uphops) ... #} # Example: # # G: AABBCCDD ich.dyndns.org 2500 12345678 peer.dyndns.org 2500 # # The connection to a server with CCcam Gbox is recommended in any case. All this runs on both sides # extremely unstable! # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # Other configuration settings # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # SERVER LISTEN PORT setting # # # port that our server uses for incoming connections. # When sharing via Internet this port must be forwarded in the router to the IP of our server. # CCcam uses TCP as the protocol. # Default port is 12000, the server can be combined with-s parameter or with set to 0 port off # # SERVER LISTEN PORT: 12000 # # ALLOW TELNET INFO / ALLOW WEBINFO setting # # # The server can some information about connected servers, clients, and Cards Info # output using telnet or a web browser. # # Telnet and Webinfo on / (on yes = no = off) from switch is # default "yes" # # ALLOW TELNET INFO: no # ALLOW WEBINFO: no # # SHOW exteneded CLIENT INFO setting # # # Extended client information in the client list, show # The default is "yes" # # SHOW exteneded CLIENT INFO: no # # WEBINFO USERNAME / PASSWORD WEBINFO setting # # # The Webinfo can be protected with a username and password. # This is disabled by default. # # WEBINFO USERNAME: <username> # WEBINFO PASSWORD: <Password> # # TELNET INFO USERNAME / PASSWORD setting TELNET INFO # # # The telnet info can be protected with a username and password. # This is disabled by default. # # TELNET INFO USERNAME: <username> # TELNET INFO PASSWORD: <Password> # # TELNET INFO LISTEN PORT / WEBINFO LISTEN PORT setting # # # The default port for Telnet info 16000 # The default port for the Webinfo is 16001 # supported commands : # info # active clients # clients # servers # shares # providers # entitlements # examples to use: # echo servers | telnet localhost 16000 # Open the browser: http://IP_des_CCcam-Servers:16001 # # TELNET INFO LISTEN PORT: 16000 # WEBINFO LISTEN PORT: 16001 ZAP OSD TIME setting # # # # # time in seconds in which the On Screen Display is active. # In the OSD date information about the currently used map are displayed on the TV. # Which provider that is peer how far the card is removed, etc. # Default 0 (off) # # ZAP OSD TIME: 3 # OSD USERNAME setting # # # # username used for the popup. It is the same as the password for the web interface of your box. (Default: root) # OSD USERNAME: root OSD PASSWORD setting # # # # # password for the pop. It is the same as the password for the web interface of your box. (Default: dreambox) # OSD PASSWORD: dreambox OSD PORT # # # # # setting port for the PopUP. (Default: 80) # OSD PORT: 80 # SERIAL READER setting # # # # # Card Reader Configuration Here we carry all, via serial or USB connected card reader. # (Not the internal smart card slots of the receiver that are automatically triggered) # Optionally, the reader type be specified: phoenix, mouse UNIPROG, sc8in1, smart reader + # (if no reader type is specified, then the default "UNIPROG" is selected (eg for mastera)) # # SERIAL READER: Path of Reader> <Readertyp> # # Example: # # SERIAL READER: / dev/tts/0 # # SMARTCARD WRITE DELAY setting # # # write delay setting for smart cards. # Here you can the write speed of smart cards to fine tune. The optimal setting depends on the # of the computing power of the system and the computing power of smart cards. # The default value is calculated, but can be canceled with this setting. # Delay in milliseconds hiss bytes, 0 = no delay, -1 = calculated default # Note: There is a large difference between the values 0 and 1, because of the tabular additional expenses. # # SMARTCARD WRITE DELAY: <path <delay> # # Example for 10ms write delay for the card inserted in the card reader to Reader> / dev/ttyUSB0 # # SMARTCARD WRITE DELAY: / dev/ttyUSB0 10000 # # Note to SC8in1; Because 8 smartcards are managed under the same path, use # Pfad_0 .. Pfad_7 for the adjustment of individual smart cards. # Example: / dev/ttyS0_0 / dev/ttyS0_1 .. # Example for 8ms write delay between bytes to smartcard on last slot of the SC8in1, # connected to / dev/tts/0: # # SMARTCARD WRITE DELAY: / dev/tts/0_7 8000 # # SMARTCARD CLOCK FREQUENCY setting # # # Smart Card Set clock frequency # Do not fit if you do not know what you're doing. # In 99% of cases the reader selects by itself the right frequency. # Changing this setting may make the card more slowly, or even destroy it. # # SMARTCARD CLOCK FREQUENCY: <device> <freq in Hz> # # Example to the card in / dev/ttyUSB0 with 5.5 MHz to run: # # SMARTCARD CLOCK FREQUENCY: / dev/ttyUSB0 5500000 # # SHOW TIMING setting # # # Display the ECM times in OSD and debug output # The faster we reach the ECM so much the better, with this setting, we can let the OSD # indicate how long the ECM needed to reach us. # Default is no (turned off) # # SHOW TIMING: yes # # MINI OSD Setting # # # Enables the mini OSD which shows only server (type), cardreader, keys or FTA. # Default is no (turned off) # # MINI OSD: yes # # DEBUG setting # # # Turns on debugging, and from # default is no (turned off) # # DEBUG: yes # # newcamd CONF setting # # # If CCcam try the newcamd.conf for server connections to read and analyze? # Default is no (turned off) # # newcamd CONF: yes # # B: Setting # # # Here you can configure what EMM blocker you want. This can be set separately for each connected # internal and external card reader. # By default, no blocked EMM. # EMM (Entitlement Management Messages) are updates that are sent to our card. For example # for a Keywechsel or zubuchen a package or unlocking an ordered PPV film. # # B: / dev/sci0 01 # 00 - nothing # 01 - SA EMM are blocked (SA = shared Addressed) # 02 - UA EMM are blocked (UA = user Addressed) # 04 - GA EMM are blocked (GA = group Addressed) # values are added to block different EMM. eg 01 + 02 = 03 # blocks SA and UA EMM. # # Examples: # # B: / dev/tts/0 07 # B: / # # DISABLE EMM dev/sci0 01 setting # # # This setting allows the local EMM Read Disable all. # This saves a lot of CPU load, however, the card is no longer now # updated, or only from clients, which one in the F: line has the permission granted to #. # It is very useful to put this in any case in a pure server, which anyway is not # cable has a satellite /,. # # Default: no # # DISABLE EMM: yes EXTRA EMM LEVEL setting # # # # # With this setting, you allow clients that are two hops away # to send updates on our map. # Will not really needed. Power only unnecessary traffic and is also a security risk, because our Card Serial # is transferred to update to the peer. # # Default: no # # EXTRA EMM LEVEL: yes # # EMM THREADS setting # # # This setting can be configured as many EMM listener # to start. # It takes two, if you for example a 7025 operates with Twin Tuner and # looks an encrypted channel and would like another record. # However, this is only important if the used card permanently EMM # benötig. No map is known to me who needs it. # # Default: 1 # # EMM THREADS: 1 # # # # # boxkey setting NDS Boxkey replace (4 byte hex) # Some NDS Videoguard card only run in the intended box. # CCcam can map to pretend this receiver. For this you need a # Boxkey. # Sky Germany and KabelBW NDS cards have not been this lock. # # Boxkey: Path of Reader> <Byte1> <Byte2> <Byte3> <Byte4> # # Example: # # boxkey: / dev/sci0 00 11 22 33 # # # # # setting PIN PIN cards for Cryptoworks cards put. (Youth protection PIN) # but not work at arenaSAT # * Note: This can block the card! * # # PIN: Path of Reader> <PIN> # # Example: # # PIN: / dev/sci0 1234 # # # # # CAMKEY setting replacing the Irdeto Camkeys (8 byte hex), default 11 22 33 44 55 66 77 88 # # CAMKEY: Path of Reader> <Byte1> <Byte2> <Byte3> <Byte4> <Byte5> <Byte6> <Byte7> <Byte8> # # Example: # # CAMKEY: / dev/sci0 11 22 33 44 55 66 77 88 # # # # # Replace CamData setting the Irdeto CamData (64 byte hex) # null bytes at the end can be omitted. # Default for unknown ASC's is 11 22 33 44 55 66 77 88 00 00 .. 00, known ASC's have other standards. # # CamData: Path of Reader> <Byte1> <Byte2> <Byte3> <Byte4> <Byte5> <Byte6> ... <Byte64> # # Example, when only the first 15 bytes of the CamData not exist nuller blocks of: # # CamData: / dev/sci0 11 22 33 44 55 66 77 88 99 aa bb cc dd ee ff # # BEEF ID setting # # # Special set of IDs for BEEF patched cards # # BEEF ID: <Ident1> <Ident2> <Ident3> <Ident4> <Ident5> <Ident6> <Ident7> <Ident8> Path of Reader> # # Example: # # BEEF ID: 4101 0 0 0 0 0 0 0 / dev/sci0 # # FILE softkey setting # # # Where is the SoftCam.Key file? # This file keys registered for the transmitter, which can be decrypted at the time by the # in CCcam Softcam built-Emu. # The file is for the operation of CCcam Cardsharing as-Emu is not mandatory, but # should be used to relieve the network. Because for stations which are opened by the file # go no requests to the CS network. # # Default: / var / keys / SoftCam.Key # # SOFT KEY FILE: / var / keys / SoftCam.Key # # AUTO ROLL FILE setting # # # Where is the AutoRoll.Key file? # In this file, so-called AU-Keys are entered (auto update). If functioning # AU-keys are available will be automatically decrypted at a Keywechsel the new Key from the satellite or cable # Stream and entered into the SoftCam.Key file. # This file is for the operation of CCcam not mandatory. # # Default: / var / keys / AutoRoll.Key # # AUTO ROLL FILE: / var / keys / AutoRoll.Key # # STATIC CW FILE setting # # # Where is the constant.cw file? # In this file, so-called CW Keys are entered. These keys appear again and again #, but usually keep for longer than a few hours. Normally to # decrypt a station approximately every 10 sec can be calculated a new Control Word (CW). With a # error in the system of pay-TV provider, it may happen that this does not happen and a # CW stays longer valid. And so long until it will be noticed and / or the server of the provider # is restarted. # This file is for the operation of CCcam not mandatory. # # Default: / var / keys / constant.cw # # contents of the file can look like this: # # ca4: id6: SID4 <img title = "Stick Out Tongue" src = "http://www.marco1.eu/ / wp-content/uploads/2011/03/tongue.png "border =" 0 "alt =" "/> mtpid4: ecmpid4: Key16 (01 02 03 ..) # # STATIC CW FILE: / var / keys / # # CAID PRIO FILE constant.cw setting # # # Where the file is CCcam.prio? # This file can be configured, which caïds CCcam or prefer to ignore. # Since version 2.0.8, this file almost no longer necessary, but it can reduce the switching times # enormously with some providers. In version 2.0.10 and 2.0.11 Share the logic is again # significantly improved. However, much to the detriment of the network traffic. # # Default: / var / etc / CCcam.prio # The file contents can Ignores (I) and prio (P) contain lists. # # Note 1: I: Lines concern ECM and EMM (there are no EMM from ignoriertem system) # P: Lines only affect the ECM selection (EMM will continue for all existing systems received # and not just for the preferred system) # # Note 2: ident 0 means 'all idents'. So 'caid: 0' the Same as 'caid'. # # Note 3: For some systems (eg nagra (caid 18xx)), the ident at the time where the priority list # tested is not known. In this case, the adjustment is carried out only on the caid. # Even if the P: Line not intended zeroed idents. # So, for example, behaves '1801: 401 'exactly as '1801' in a P: Line. # I: Lines operate differently. They are two times tested. A is times then the ECM or EMM received # and once after. (And the Nagra ident should be known) # P: lines are only checked once, before ECM are received. # # Note 4: If a P: Line CAID: contains ident pairs which are not available for the current channel #, this P: Line not used for the current channel. # Example: The channel has the system 626, 1801:401 then P is: line ignored "1801,100:96,626" # from this channel because this channel does not have 100:96. But # P: line with "1801" is taken and the "626.1801" is taken for that channel. # # Note 5: P: Lines are in which they are dependent on the order in the file. # Only the first matching P: Line is being used. # # Note 6: I: Lines certain caïds for your own use will be ignored. This does not mean that # this caïds no longer exist now in the Share. You will still be accepted and passed on #. I: Lines are therefore not suitable for sorting out old, no longer active providers # and Fakekarten. This is best done right at the end of each C: line. # # Note 7: A Prio you created on your own needs. Ready Prios, as they are offered in many forums and ULCs #, can do more harm than use them. Therefore, anyone who is dissatisfied with the card selection # his CCcam itself deal with the creation of its priorities. It must be noted # that will be the priority as small as possible and only really necessary adjustments are made. # The more stands in a priority, the more must also execute CCcam. # # Situation 1: ignore this caid always, all idents, on all channels. # I: caid # # situation 2: ignore getting this CAID / ident pair. # I: caid: ident # # situation 3: ignore this caid / ident pair on this channel 'SID'. # I: caid: ident: sid # # situation 4: If CAID1 and CAID2 exist on a channel is CAID1 preferred. # P: caid1, caid2 # # situation 5: If CAID1: Ident1 to CAIDX: IdentX exestieren on one channel, they are used in # the order of the list. # P: caid1: Ident1, caid2: ident2, .., caidX: identX # # situation 6: when CAID1: Ident1 to CAIDX: IdentX exist on the channel 'SID', they are used in # the order of the list. # The SID on the first CAID / ident pair identifies which SID for this list is # used. All other SIDs ignore this list. # P: caid1: Ident1: sid, caid2: ident2, .., caidX: # # CAID PRIO FILE identX: / var / etc / CCcam.prio # # PROVIDER INFO FILE setting # # # Where is the CCcam.providers file? # This file contains the provider are determined. It is not necessary for the operation of CCcam. # The information in this file are used for the CCcam web interface to display the # cards with the matching provider name in the list. # # Format: # <caid> <ident> "Provider description" # # PROVIDER INFO FILE: / var / etc / CCcam.providers # # CHANNEL INFO FILE setting # # # Where to CCcam.channelinfo is file? # In this file, the channels are determined. It is not necessary for the operation of CCcam. # The information in this file are used for the CCcam web interface. # # Format: # caid: ident: sid "Channel description" # # CHANNEL INFO FILE: / var / etc / CCcam.channelinfo # # LOG WARNINGS setting # # # false logins into a disk file. # This file can have read if not tried authorized users to connect to us. # Goes course at the expense of performance and should only occasionally activated. # By default this is turned off. # # LOG WARNINGS: / tmp / warnings.txt # # newcamd STEALTH setting # # # General settings for the disguised as other Emu connect to newcamd / NewCS servers. # The setting in the N: line is preferred. # Tarneinstellung: 0 = off, 1 = MGcamd new, 2 = MGcamd old, 3 = Evocamd, 4 = Generic # # Default: 0 # # newcamd STEALTH: 0 # # # # # LOAD BALANCE setting load balancing between identical cards. It lists the paths of the card reader, # containing identical cards, optionally followed by a list of service IDs which # are excluded from balancing. # # LOAD BALANCE: Path of Reader1> Path of Reader2> .. Path of ReaderX> {<ausgenommene SID1>, <ausgenommene SID2> .. , <ausgenommene SIDX>} # # multiple loadbalance groups can be configured, by adding multiple lines. # Warning: restart is required, when loadbalance group configuration has been changed. # # Example 1: load balance query for three identical cards. # # LOAD BALANCE: / dev/ttyS0 / dev/ttyS1 / dev/ttyS2 # # example 2: load balance request for two almost identical cards, SID 0df3 and 0de1 are only available # on one of the cards, so requests to these SIDs should not poised be. # # LOAD BALANCE: / dev/ttyS5 / dev/ttyS6 {0df3, 0de1} # # MINIMUM CLIENT VERSION setting # # # In version 1.2.1 and earlier versions have a problem which may result to # the connection is terminated to clients . # In Version 1.4.0 wurde die Netzwerkbelastung deutlich reduziert. # In version 1.7.0 wurde ein gefährlicher Password-Bug behoben. # ... # In Version 2.0.5 wurde das Karten-Faken, mit Hilfe von anderen Emus, gesperrt. # # Aufgrund der vielen Erneuerungen sollten User mit alten Versionen zu aktuellen Versionen wechseln. # Mit dieser Einstellung kann man Usern, die eine alte CCcam Version nutzen, die Probleme verursachen kann, # den Zugang zu unserem Server verweigern. # # Standard: alle Versionen zugelassen # # Beispiel: alle Versionen vor 1.7.0 werden geblockt # #MINIMUM CLIENT VERSION : 1.7.0 # # VORSICHT: Mit mit der Version 2.0.10 ist es zu folgendem Problem gekommen: Diese Version wird als 2.0.1 erkannt # und somit können sich diese Peers nicht mehr zu uns verbinden, wenn wir das Minumum auf einen Wert # höher als 2.0.1 stellen. Das bedeutet bei eingestellter "MINIMUM CLIENT VERSION : 2.0.2" bis # "MINIMUM CLIENT VERSION : 2.0.9" können sich 2.0.1x Server nicht mehr zu uns verbinden. # Seit CCcam 2.1.1 sind alle Probleme mit dieser Einstellung wieder behoben worden. ## TRY ALL CHIDS Einstellung ## # Irdeto Smartcards: Option um das "smart ChannelID checking" für Irdeto Smartcards abzuschalten. # Standard: Nur ChannelIDs die von der Karte angegeben werden, werden akzeptiert. # Dies bedeutet viel unerwünschten Datenverkehr für die Karte. # # Doch wenn die Smartcard versteckte/unbekannte Chids hat, sollten alle Chids probiert werden. # In diesem Fall ist die 'TRY ALL CHIDS' Option für den Cardreader zu setzen. # Dies ist mit Bedacht zu nutzen, da das Aktivieren dieser Option mehr Card Traffic bedeutet. # Diese Einstellung nur nutzen, wenn einige Kanäle nicht funktionieren. # Bemerkung: Wenn auch diese Einstellung nicht hilft alle Kanäle zu entschlüsseln, versuche das # Kommandozeilen Argument -l zu nutzen, um alle Selbstlern-Features zu deaktivieren (Warnung: langsamer) # # TRY ALL CHIDS : <Pfad zum Reader> # # Beispiel: Die Karte in /dev/ttyUSB0 bekommt ECM für alle möglichen CHIDs, nicht # nur die CHIDs die sie offiziell unterstützt. # #TRY ALL CHIDS : /dev/ttyUSB0 ## POSTINIT Einstellung ## # Ausführen von Smartcard Post Init Kommandos # # POSTINIT : <Pfad zum Reader> <Dateiname> (<autodelete>) # # Sendet Komandos aus 'Dateiname' zum 'Pfad zum Reader' und löscht 'filename' wenn das optionale # 'autodelete' nicht genullt ist. # # Beispiel: # #POSTINIT : /dev/sci0 /tmp/postinit # # Beispiel für den Inhalt in /tmp/postinit: # c134000003000000 # c13201000a ## DVB API Einstellung ## # Option zum Überschreiben der automatisch erkannten DVB-API-Version. Neustart erforderlich. # # DVB API: <Wert> # # <Wert> <1 = kein DVB, 1 = DVB API 1, 3 = DVD API 3> # # Warnung: Nur nutzen wenn die automatische Erkennung fehlgeschlagen ist! # # Beispiel für das Abschalten nicht laufender DVB-Hardware: #DVB API: -1 ## GLOBAL LIMITS Einstellung ## # Option um die allgemeinen Share-Begrenzungen zu setzen. # Hier lässt sich in einem Abwasch erledigen, was sonst hinter jede F: Line gesetzt werden müsste. # zB die Reshare-Begrenzung für unsere Karten. # # GLOBAL LIMITS: { caid:id(:downhops), caid:id(:downhops), ... } # # Beispiel: # #GLOBAL LIMITS : { 0100:000080, 0622:000000:1, 0500:000000:2 } # # Alle Peers bekommen nicht die 0100:000080 Karten # und alle 0622:000000 Karten nur für sich selbst (1 hop down) # und 0500 Karten für sich, plus einen zusätzlichen Hop weiter. # Die allgemeinen Begrenzungen werden von den clientspezifische Begrenzungen außer Kraft gesetzt # (siehe Beischreibung zur F: Line) ## MINIMUM DOWNHOPS ## # Option um Karten mit geringem Reshare auszusortieren. # # MINIMUM DOWNHOPS: <Wert> # # Standard: 0 (ignoriert keine Karten) # # Beispiel: # #MINIMUM DOWNHOPS: 1 # # Ignoriert alle Karten, die nicht mehr an andere Peers weiter geshared werden können. # Sinnvoll für Server, auf denen eh kein Fernsehen geschaut wird oder # auch eine einfache Art zu begrenzen, wenn man zu viele Karten bekommt. ################## # ab CCcam 2.1.0 # ################## ## IGNORE NODE Einstellung ## # Einstellung für das Ignorieren aller Karten von bestimmten Peers, # welche nicht unbeding direkt mit uns verbunden sein müssen. # Mit dieser Eistellung lassen sich nun auch Karten von Peers ignorieren, welche unseren Share stören. # Dies können zB RSA-Karten wie die Anaconda oder Minerva sein, welche immer noch auf # auf Anfragen antworten und somit einen schwarzen Bildschirm bei uns verursachen, oder aber auch # ständig überlastete Peers oder Karten die zwar korrekt antworten, aber dauernd Bildaussetzer # verursachen. # # Für diese Einstellung benötigen wir die zur schlechten Karte/Peer dazugehörige NodeID. # Diese finden wir in der Datei "Ecm.info" im Ordner /tmp, die wir auslesen, wenn unser Share gestört wird. # # Leider ist die NodeID nicht statisch. Bei einem Neustart des Systems wird jedes mal eine neue generiert. # Deshalb sind erstellte IGNORE NODE Lines nicht lange gültig. # # IGNORE NODE: <NodeID> # # Beispiel für das Ignorieren zweier NodeIDs: # #IGNORE NODE: ccd536ab515767ad #IGNORE NODE: aad536ab515761af ## SECA HANDLER Einstellung ## # Der SECA Handler wird genutzt, um die Kartenauswahl auf Providern, welche SECA2 und SECA3 gleichzeitig # über die selbe Ident nutzen, zu verbessern. # # Mit dieser Einstellung lässt sich das Verhalten beeinflussen, wie SECA genutzt werden sollen. # Diese Einstellung wird ignoriert, so lange nicht SECA2/SECA3 simulcrypt erkannt wird!! # # Wenn es abgeschatet ist, dann verhält sich CCcam wie in den Versionen vor 2.1.0. # # Wenn SECA3 vor SECA2 bevorzugt wird, dann wird versuch erst SECA3 ECM zu verwenden und dann erst SECA2. # # Wenn SECA2 vor SECA3 bevorzugt wird, dann wird versuch erst SECA2 ECM zu verwenden und dann erst SECA3. # # Wenn SECA2 ignoriert wird, dann werden keine Anfragen mehr an SECA2 Karten mehr gestellt, # welche nicht verarbeitet werden können. # # Wenn SECA3 ignoriert wird, dann werden keine Anfragen mehr an SECA3 Karten mehr gestellt, # welche nicht verarbeitet werden können. # # Folgende Einstellungen können genutzt werden: # # SECA HANDLER: <Wert> # <Wert> : 0 = abgeschaltet, 1 = bevorzugt SECA3 vor SECA2, 2 = bevorzugt SECA2 vor SECA3, 3 = ignoriert SECA2, 4 = ignoriert SECA3 # # Standard: 1 # # Beispiel 1: Erst wird SECA3 ECM, dann SECA2 versucht # #SECA HANDLER: 1 # # Beispiel 2: Erst wird SECA2 ECM, dann SECA3 versucht # #SECA HANDLER: 2 # # Beispiel 3: Alle SECA2 ECM werden ignoriert, so das SECA3 Karten keine SECA2 Anfragen bekommen, # welche sie nicht verarbeiten können. # #SECA HANDLER: 3 # # Beispiel 4: Alle SECA3 ECM werden ignoriert, so das SECA2 Karten keine SECA3 Anfragen bekommen, # welche sie nicht verarbeiten können. # #SECA HANDLER: 4 # # Beispiel 4: Seca Handler ist abgeschaltet #SECA HANDLER: 0 ################## # ab CCcam 2.1.2 # ################## ## SMARTCARD SID ASSIGN Einstellung ## # Hier lässt sich nun endlich einstellen, welche SIDs unsere lokalen Karte(n) erhellen können, oder dürfen # sollen. Dies reduziert den Traffic zur Karte und macht somit den Share schneller und reduziert # Freezer, die durch überlastete Karten entstehen. # # JEDER SOLLTE SICH DIE ZEIT NEHMEN UND SEINE KARTE(N) MIT DIESER EINSTELLUNG KONFIGURIEREN! # # Wenn keine Einstellungen vorgenommen werden, werden alle SIDs zugelassen. # (Es kann zusammen mit der LOADBALACE Einstellung (siehe oben), # oder für Einzelkarten genutzt werden) # # SMARTCARD SID ASSIGN : <Pfad zum Reader> <Maximale Anzahl zugelassener SIDs> { <SID1>, <SID2>, ... <SIDn> } # # <Maximale Anzahl zugelassener SIDs> = begrenzt die Anzahl unterschiedlicher SIDs, für die Anfragen # an die Karte gesendet werden (0 = erlaubt alle SIDs aus der SID Liste) # { <SID1>..<SIDn> } = Diese SID Liste gibt an, für welche SIDs Anfragen an unsere Smartcard # zugelassen werden. Wenn die Liste weg gelassen wird, dann werden alle SIDs zugelassen, bis die # <Maximale Anzahl zugelassener SIDs> erreicht ist. # # Wenn <Maximale Anzahl zugelassener SIDs> größer ist, als die Anzahl der SIDs in der SID Liste, # dann werden die weiteren SIDs automatisch gewählt, bis das Limit ereicht ist. # # Die Einstellungen könen im WebIF und der TelnetInfo von CCcam unter Entitlements eingesehen werden. # # Warnung: Wenn die SMARTCARD SID ASSIGN Einstellung verändert wurde, ist ein Neustart der CCcam # erforderlich, damit die Veränderungen übernommen werden. # # Beispiel 1: Die Smartcard im Reader /dev/ttyUSB0 bearbeitet nur Anfragen für die SIDs: # df3, df4, df5 # #SMARTCARD SID ASSIGN : /dev/ttyUSB0 0 { 0df3,0df4,0df5 } # # Beispiel 2: Die Smartcard im Reader /dev/ttyUSB0 bearbeitet nur Anfragen für maximal 5 SIDs # gleichzeitig. Eine Anfrage für eine sechste SID wird abgewiesen. Welche SIDs dies sind wird # automatisch über die Reihenfolge der Anfragen ausgewählt. # #SMARTCARD SID ASSIGN : /dev/ttyUSB0 5 # # Beispiel 3: Die Smartcard im Reader /dev/ttyUSB0 bearbeitet nur Anfragen für maximal 5 SIDs # gleichzeitig, 3 von ihnen sind fest gesetzt (hier: df3, df4 und df5), die restlichen 2 werden # automatisch zugewiesen. # #SMARTCARD SID ASSIGN : /dev/ttyUSB0 5 { 0df3,0df4,0df5 } ################## # ab CCcam 2.2.0 # ################## ## SMARTCARD SID REJECT Einstellung ## # Hier lässt sich einstellen, welche SIDs auf der Karte nicht freigegeben sind. # Wenn hier nichts Eingetragen wird, sind alle SIDs erlaubt oder es greift die SMARTCARD SID ASSIGN # Einstellung, sofern vorhanden. # Nicht zusammen mit der (gefixten) SMARTCARD SID ASSIGN liste benutzen. Entweder das eine oder # das andere, abhängig davon, welches die kürzeste Liste ergibt. # Sie arbeitet nicht mit der dynamischen SMARTCARD SID ASSIGN (bedeutet: Angabe wie viele SIDs # gleichzeitig zugelassen werden) Liste zusammen. # Sie arbeitet LOADBALANCE Einstellung zusammen. (nicht zugelassene SIDs werden automatisch von # der Ladebalance ausgeschlossen) # # SMARTCARD SID REJECT: <Pfad zum Reader> { <SID1>, <SID2>, ... <SIDn> } # # { <SID>..<SIDn> } gibt die SIDs an, für welche keine Anfragen an die Karte gesendet werden. # # Warnung: Wenn die SMARTCARD SID REJECT Einstellung verändert wurde, ist ein Neustart der CCcam # erforderlich, damit die Veränderungen übernommen werden. # # Beispiel: Die Karte in Reader /dev/ttyUSB0 soll keine Anfragen für die SIDs df3, df4, df5 erhalten. # #SMARTCARD SID REJECT: /dev/ttyUSB0 { 0df3,0df4,0df5 } ## SCIDEVICES Einstellung ## # Hier lässt sich einstellen, wie viele sci Kartenleser (Receiver eigene Kartenleser) # von CCcam angesprochen werden sollen # # SCIDEVICES: <Nummer> # # Beispiel 1: Es werden keine sci Kartenleser angesprochen # #SCIDEVICES: 0 # # Beispiel 2: Es werden zwei sci Kartenleser angesprochen # #SCIDEVICES: 2 # # Wenn hier nichts eingetragen wird. wird die Anzahl der sci Kartenleser automatisch erkannt. # Warnung: Wenn die SCIDEVICES Einstellung verändert wurde, ist ein Neustart der CCcam # erforderlich, damit die Veränderungen übernommen werden.
