The new possibilities in latest MultiCAS - how do they function?

[gorski]

Hello, foreros!!!

0) Of course, before all else, one will have to install MultiCAS into one's AZbox HD.

How do we do that? Well, you have it in my "Alternative guide to AZbox HD" kindly translated into Spanish by our fellow forero pe.tardo! See the Manuales sub-section in original FW section of the forum.

Let us start, then, with the very basis. Download and install the latest FW in your Abox HD as follows...

-Make sure you're online ["connected"] for the next step. How? HOME => Settings => System Information. If you cannot see “connected”, that is to say an IP address assigned to your AZbox HD, the first thing you can do is to reboot. Then, if you're still not online, check the LAN cable or your wireless settings, your modem/router etc.

-When you are online, this will allow you to download and install directly into AZbox HD. From various Firmwares[FW]/Operating Systems [OS], to various Emulators/Card Sharing [CS] software [SW]/”plug-ins”, which will either read or emulate original and pirate smartcards, connect to your Leete las normas/servers in terms of Card Sharing [CS] etc.

If you cannot do it, that is because you do not have the links from which to do it, as they do not come included in official FWs. There are different ways of adding them to your AZbox HD menu…

-HOME button on your remote => Settings => System Information => right button next to the OK button => Firmware upgrade => green button to "Edit URL" => move the cursor right and place it before the last 'w' in 'www' => press DEL/BACK button on your remote twice => press button number 3 three times to write 'f' [it should look like this now: http://fw.azupd.com] => press OK button.

-When one is done doing the above, press OK on your remote and choose the latest FW [now, it is 0.9.5305]. This action will download and install it in one go. For all the details, including the configuration of Settings etc. - please consult my "Alternative Guide" in Spanish, thanx to pe.tardo!

Now, let us install OpenXCAS, which is a pre-requisite for MultiCAS. This is how it is done...

-Press HOME => Plug-in => "Add plug-in" by pressing the red button => edit the links by pressing the blue button ["Edit Server URL"] on your remote [do not add more than 4 links!].

A note: one gets the sign " / " by pressing the CAPS/NUM on your remote a couple of times, then 1 = / etc. Also, use that button to change between the caps, numbers etc.

Here are my links, from which to download into AZbox HD directly and install stuff with ease:

http://azboxworld.com
http://techsat.info/AZPlugins 
http://www.islaremota.com/azp
http://www.descargas.azboxhd.es

Now, you can easily download and install OpeXCAS by doing the following...

HOME => Plug-ins => Add plug-in via red button => [choose the first link] OK => choose OpenXCAS by pressing OK => when done reboot!

The next step is to install the latest MultiCAS itself...

HOME => Plug-ins => OpenXCAS => Download Executable => edit the links by pressing the blue button (the same goes for Config and Others)...

Here are my links in this section:

http://azboxworld.com 
http://www.islaremota.com/aza
www.satelites.info/azbox/
http://techsat.info/AZCamd

So, now choose the first link with OK => install the latest MultiCAS and reboot by pressing the top left [red] Standby/Power button on your remote by about 5 seconds!

Congratulations! B) Let the fun begin! :D

 

[gorski]

1) Before all else, I have a confession to make: let me tell you that I do not understand some of the functions of the latest MultiCAS very well myself.

Partly, it's because I haven't yet tried. So, you can try with me...

But partly it's because the language in "example" files really puts me off. It is a terrible language, without any meaning whatsoever! Whoever wrote it is both a terrible English speaker as well as terrible thinker. Nothing is separated into smaller, logical cells properly, so that it makes sense and that it is easier to follow.

Then, it's the jargon. As if all the users must be technically educated a s well as the writer of MultiCAS, which is terribly naive, immature and self-centred.

And so on and on and on...

2) So, let us explore it together, as there are some very well educated people on this forum who will definitively be able to help, like Morser, hperez, JPbravo, oscar and so on, to mention but a few... Sorry, I can't draw an exhaustive list... :D

3) Ergo, let us do it in detail, without presuming anything at all, with as little as possible of the technical jargon, please.

4) The latest version has various "example" file, which need to be edited according to one's needs. We will try to analyse those together and shed some light on it.

5) In order to edit them you need to connect with your AZbox HD. Do that using the freeware FTP SW called FileZilla Client, which you can download here:

http://filezilla-project.org/download.php

In the FZ Client itself you can connect it to the editor of your choice, so all the files inside AZbox HD can be easily adjusted to your needs. See Edit => Settings => File Editing => Use custom editor => Browse => find the .exe file of the editor you installed on your PC => Open => OK.

Which editor? Here is my recommendation...

6) Edit them using the freeware UNIX compatible editor called Notepad++, which you can find here:

http://notepad-plus-plus.org/release/5.9

7) Once you finish editing the files you need to edit, right click on them => Rename => delete only the "example-" bit and hit the 'Enter' button on your keyboard.

8) OK, I will post each file in a separate post, so that it is easier to refer to it or even quote it, without having to delete all others files and a long text that speaks of other parts...

Lastly, please, keep to the point and use the least amount of technical jargon possible!

I will attach all the files discussed in this thread here, as well, just in case it may help somebody...

Gracias! B)

 

[gorski]

There are various “plug-ins”. Some are Emulators, emulating Original Smart Cards [OSC], decrypting encrypted satellite, terrestrial or cable channels, if those encryption systems are hacked and so those cards can be “read” and “emulated”. Some other “plug-ins” are a mixture of camd and CS SW [= Card Sharing SW].

One of them is MultiCAS camd, reading many cards but also opening many channels thanx to its Emulator. By incorporating various bits from various hacked CAS [= encryption systems], as well as by Card Sharing [CS] protocols that are built into it one can have a lot of fun exploring it... :D In other words, the hacked encryptions systems are opened either:

-by using keys incorporated in MultiCAS or

-by connecting to your colleagues' cards, which are in their own machines [those are your 'virtual' cards, as opposed to your own, 'local' card(s)], by utilising the internet, that is to say by Card Sharing [CS].

Now, CS has various pieces of SW to accomplish those tasks.

1) Card Readers/CS servers [Newcamd, NewCS, SBox, OSCam and so on] = allowing other people to hook onto their cards by "broadcasting" to them...

2) CS Clients [Mbox, for instance, is only a client, whereas some others are both severs and clients, like OSCam], which allow you to connect to other people's smartcards and open channels you do not have a smartcard to open...

3) Both servers and clients [GBox, OSCam, CCcam etc.]

But what about MultiCAS?

Well, it has it all!

-an emulator, as I explained

-card reader

-server

-various client protocols...

However, there are several questions we need ask and find answers to them, in order to explain what is going on inside MultiCAS...

1) Which protocol does it utilise for its Server? Its own or...?

2) How do they all connect/communicate?

3) How does one configure all those parts, so it all functions together, if possible?

4) What exactly is possible with MultiCAS alone? What can it do without any other CS SW?

Now, my limited understanding of MultiCAS is as follows [and this will be written as series of QUESTIONS FOR DEBATE, so we can all be a little bit more INFORMED by the end of this discussion]:

1) It has its own protocol - for the server part - we are told. I am not at all sure it this protocol is compatible with Newcamd protocol, arguably the most widely used protocol these days, when it comes to CS servers. Or any other widely used protocol, like CCcam or... Is it?!?

2) Allegedly, the Newcamd and CCcam Client protocols can now work together. I'm sure they can but I haven't tested them together [successfully] yet...

3) Well, I can show you how to configure the CCcam and Newcamd client parts. More than that - I would have to experiment and maybe even ask for some help, from people who already tried it and succeeded, so I don't waste time, which a young dad, like myself, has very little...

4) I hope it can be:

-card reader [which it is, for most original smartcards]
-a Newcamd server [not sure it can do this or if it needs another CS SW for this function]
-CCcam and Newcamd client [which it is, as mentioned]
-Emulator, opening the hacked systems with publicly known keys [which it is]...

To be continued...

 

[gorski]

The devil lies in the details, so....

Here are the "example" files I mentioned. Once you are done editing them according to your needs you must rename them, as explained above. This one:

example-cardkeydata.txt should become cardkeydata.txt

once you put the details of your original smartcard [OSC] and/or official receiver in...

This is done in order to "marry" the card with the AZbox HD receiver, so it can function as if it is in the original receiver, which usually came with the card...

You get these details by either

-reading them out or from your card or

-from your receiver.

This can be technically very challenging, needless to say, as opening of the box/or connecting to your smartcard and reading the details from it is quite complex and requires some knowledge and skills, plus some specialised equipment. Best left to the professionals, if you can find them...

[slot 1]
boxkey = 00 00 00 00 00 00 00 00
modkey = 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

[slot 2]
boxkey = 00 00 00 00 00 00 00 00
modkey = 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00


[slot 3]
boxkey = 00 00 00 00 00 00 00 00
modkey = 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00


[slot 4]
boxkey = 00 00 00 00 00 00 00 00
modkey = 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

[nds-h]
boxid = 12 34 56 78

## if caid = 0600 or 1700 mean any CAID should be using below camdata and camkey 
[ird]
caid = 06 00
camdata = 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
camkey = 00 00 00 00 00 00 00 00

## autoPPV = 0 : Inactive / autoPPV = 1 : Active
[seca]
autoPPV = 0

OK, can we have some explanations, at least for Nagra and Seca, widely used in Spain and Portugal, from people who used it successfully...

My Conax card CAS5 does not need to be 'paired' like this. CAS7 version does. So, an older MTV Conax card would work in AZbug HD easily.

Sometimes they would work in AZbox HD anyway [without all the details] but they would not get updates/new keys sent by the providers, for which you would need to put them in the original receivers...

 

[gorski]

example-cardreader.cfg => when edited according to your needs it should be cardreader.cfg

###### Disable or Enable option for cardreader of MultiCAS
###### Disable_CardReader = 1 -> Disable-Internel CardReader / Disable_CardReader = 0 -> Enable-Internel CardReader
Disable_CardReader = 0

Now, this is inane!!! :o What the hell does that mean?!? :blink: The writer never heard of a NEW LINE?!? You enable it by 0 or 1?

I suppose that he meant:

###### Disable or Enable option for MultiCAS cardreader
#CardReader = 1 -> Disable-Internal CardReader 
#CardReader = 0 -> Enable-Internal CardReader
Disable_CardReader = 0

If you enable it by '0', as above, I suppose this means that only MultiCAS internal reader works, no other reader can work at the same time [like NewCS or OSCam, for instance]?

Also, from what is written one more thing is not completely clear, as he is not saying consistently internal reader every time, so... But I suppose it's only to do with the internal reader...

But the main question now:

If you enable internal card reader, can it work as a server and which server protocol is it?!?

MultiCAS server - as I wrote - is possibly just MultiCAS protocol and not compatible with Newcamd or CCcam server protocols... Anyone with more information???

 

[gorski]

example-ccc_version.cfg when edited to your needs ought to read ccc_version.cfg

####################################################
### CCcam Client Version x.x.x and Build
##
## 	Version   Build
##   ---------------
##	   2.0.11     2892
##	   2.1.1      2971
##	   2.1.2      3094
##	   2.1.3      3165
##	   2.1.4      3191
##
## Default 2.0.11 2892
####################################################
2.0.11 2892

You obviously choose the version of CCcam client part of MultiCAS here.

No idea why just these versions and not the latter ones... Any idea?

Which of these works best in AZbox HD, guys? Anyone?

 

[gorski]

example-cccam.cfg when edited should read cccam.cfg

## MAX Support the 16 of Serverlist by this CFG file
## example C: hostname port username password

What a stupid thing to do, if you know your English is sooooo piss-poor - why not have it checked by somebody?!?

Crap!

The file should read/what he meant is:

##MultiCAS CCcam Client supports maximum 16 C lines
##example
##C: hostname port username password

You can add up to 16 CCcam servers of your friends/colleagues, whose cards you hook onto via internet.

The format is, for example...

1) if they have dynamic IP addresses:

C: somename.dyndns.org 12000 myusername mypassword

All of those details are to be given to you by your friends/colleagues, who choose them for you and thereby allow you in their CCcam servers

2) if they have static addresses, something like this:

C: 94.128.88.113 12000 myusername mypassword

But this is a rare case, as most users have dynamic addresses, for which we use the DynDNS or some such service, so whenever it changes our AZbox HD CS clients are able to find them and hook onto their servers anyway...

3) Btw, if you have a local/home network, whereby you want to use one of your two or more receivers to hook onto the only one with a card, you will do the same between two receivers in your house/home network:

C: 192.168.x.x 12000 myusername mypassword

In this case, of course, you choose all the details... :D

 

[gorski]

example-splitterdata.txt when edited should be saved as splitterdata.txt

[splitter]
IP = 1.1.1.1
PORT = 3000
DN = Test.dyndns.tst

CCCAM_NEWCAMD_WORK_TOGETHER = 1

Now, this is criminal. No explanation of various modes of functioning whatsoever!!!

I presume it's because the person's [writer's] English is crap.

Also, developers are frequently [not always, thank fook!!!] like that: "What's to tell, what's the big deal? If I understand it - everybody should... or they are 'lamers'..." [and then inane, immature cackles follow...]

1) Which IP address? Is it:

127.0.0.1

or

192.168.x.x

Or what?!?

1a) Does port need to be opened/forwarded - for one's clients?

1b) Which protocol does server use?

1c) Is it meant just internally, for one's home network or can it work externally, over the internet, as well?

1d) If it can, is it only for AZboxes or is the protocol compatible with Newcamd or CCcam or some such server?

2) The DN line in the file suggests it can be used over the internet for CS purposes but it is not clear at all, as I wrote above, using which protocol etc. etc.

So, the DN line should be something like:

DN = somename.dyndns.org or 
DN = somename.dyndns.net or
DN = some other DynDNS service

I suppose...

However, since no username/password options are given, I am not sure at all what the purpose and nature of this part is... I mean, if you can be a server [Newcamd or CCcam or AZbox HD protocol], normally one would expect that one has options to control access to one's server by username/password combination, at the very least. Which leads me to believe that something is not quite right in here... If it is what I suspect that it is.

Otherwise, why...

3) ...the very last line???

CCCAM_NEWCAMD_WORK_TOGETHER = 1

Well, in the last version of MultiCAS it says:

ADD : Added mode 'CCCAM_NEWCAMD_WORK_TOGETHER = 2' it's using for Local Server Client + CCcam + Newcamd

WHAT?!? "It's using for..." :blink: BLOODY HELL, MAN!!! THAT'S ATROCIOUS!!! :angry:

OK, let's try to see what it is...

To my mind, it suggest that, at the very least,

-Newcamd and CCcam clients could work together, at the same time - but

-together with "only" a local server - but then they add "client"?

I beg your pardon? What on Earth would that mean?

I suppose they mean the internal AZbox HD CS server protocol, to which only other AZboxes HD can hook onto, and [mainly] in a local network? Or not?

What kind of utterly irresponsible "brain" leaves all of those possibilities unexplained?!?

The author writes a complex piece of SW - for which we are grateful!!! B) - with many functions and possibilities. But!!! He leaves us guessing, stranded, drives us to despair, as one is pulling one's hair, second-guessing oneself, one's capabilities, while trying the many combinations that could be there, as there is no documentation whatsoever, to guide you through its features...

Honestly, some people have sawdust for brains, when it comes to being social/sociable, i.e. communicating one's ideas and products to the rest of the world/others.

So, can we have some light shed on all of these issues/options in MultiCAS, that we now have, please...???

Pretty please...

 

[gorski]

Here are some images of a part of the process, I found on another forum, thanx to Jopis! It explains how one can easily get two client parts to work together.

When it comes to Newcamd Client part: maximum 12 N lines are possible. But I saw no possibility to import them from a file [see below], via a blue button, as it is possible in CCcam client, from cccam.cfg file.

In effect, one would have to put all the 12 N-lines DynDNS domains, usernames and passwords, plus ports and keys details by remote control... Swell...

Here is the last file called newcamd.cfg

## MAX Support the 12 of Serverlist by this CFG file
## N: Hostname port username password 01 02 03 04 05 06 07 08 09 10 11 12 13 14

As with the CCcam client cccam.cfg file above... but slightly different, with the added key at the end...

C und N-Linien mit der Fernbedienung eingeben

They suggest only that CCam and Newcamd Clients can work together. Nothing else.

However, we now have the option for the card reader to work as well, at the same time.

Now, since MultiCAS has a server part as well - what can be done with it all?!?

As Plato said: "Life not explored is life not worth living!"

==============================================================================================

P.S. When one has the option "Server active", in Newcamd Client part - what does it mean? Your MultiCAS server to which you hook onto in Newcamd Client part or other people's servers or what? I suppose, if you "Enable" it you will simply try to hook onto some server and that is all. But no information whatsoever... Jeezuuuusssssssssss!!!!!!!!!!!!!!! :angry:

 

[gorski]

I just tested it.

It actually works, if you put it to 1 = disable the reader, my CAS5 Conax card was not recognised/read. There was no "Card Init." message on TV screen and nothing in the Camd menu...

If I put it to 0 and restart the camd, I see "Card Initializing" and "Conax Card Init." messages on-screen and if I go to the plugins menu I see the card details...

Just testing the latest version now - properly. Finally have a bit of time, as my young son is asleep...

So, in theory, i.e. provided that MultiCAS actually performs well, with all the functions it now has, it would make it possible to:

-switch off MultiCAS embedded reader, thereby being able to

-use, for instance, OSCam server - only to read the card and pass it on to my colleagues [i.e. only be a Newcamd server, not a client to anything], then

-hook onto OSCam server, using MultiCAS Newcamd Client [via N-line] and finally,

-have MultiCAS be both CCcam and Newcamd client to external serves, as well as internal OSCam Newcamd server, I hope.

Must test, of course - but the idea seems feasible now...

Therefore, using MultiCAS we could have both C and N-lines working, together with a server [in this case OSCam], as OSCam as a client to Newcamd outside/external servers [which it needs to reach via DynDNS] is not really OK...

Back later on, after more tests...

 

[gorski]

Another example file of terrible English, which makes our efforts that much harder, since they do not respect us enough to do it at the very least correctly, by consulting others who do speak English well and making it right...

What would that be? Well, shipping MultiCAS with enough info [actually make it plenty of info!], which is correct and transparent, as in literate and readable, without much jargon.

Look at this example - which, when edited, should read priocaid.cfg

### 0100 : SECA
### 0500 : VIACCESS
### 06xx : IRDETO
### 0dxx : CRYPTOWORKS
### 0bxx : CONAX
### 09xx : NDS
### 17xx : BETACRYPT
### 18xx : NAGRA
###----------------------------------------------------
### max 16 of caid 0100 0500 0600 0900 1800 0D00 0B00 1700 and add 8 more CAID
###----------------------------------------------------
### CASE OLD #1 0600 0D00 1700 1800 0900 0B00 0100 0500     
### CASE OLD #2 0100 1800 0500 0600 0D00 1700 0B00 0900
### CASE NEW    0100 0D00 0500 0B00 0963 0961 09CD 093B 0919 09XX ... ... 1700 1800 0600
###---------------------------------------------------
0100 0500 0D00 0B00 0963 0961 09CD 093B 0919 1700 1800 0600

### Seca provider priority e.g. 6A has higher priority than 6C (Max 10).
0100 : 006A 006C 0068 0065 4101 006D 0084 0085

### Viaccess provider priority e.g. 023B00 has higher priority than 020810 (Max 10).
0500 : 023B00 020810 020820 021110 020A00 032000 032010 024410

### Pre Fix Hops for NDS e.g. 09C4 : 1 has fixed hops 1 (Max 10 NDS get 1 hops)
#09CD : 0
#09C4 : 1
#0936 : 2
#093B : 3

1) Would you just look at this illiterate genius, with a PhD in Logics:

max 16 of caid 0100 0500 0600 0900 1800 0D00 0B00 1700 and add 8 more CAID

Which one is it? Is it "max" 16 or is it 24?!? And if it is 24 - how exactly does one add another 8?

But before that, what does he mean by "16 of CAID..."? As in: "1 CAID" represents a whole encryption system, or 1 CAID per provider, which actually counts as 1?

Do various varieties of, for instance, NDS and Nagra, count as 1 per every variation within a general CAID, hence 09xx for NDS, whereby we have a few of those sub-species, as well as 18xx for Nagra, with a variety of those? In which case what counts as CAID is actually Provider ID, kinda... Because one would have to put in one per provider's variety of original Smartcards...

2) But it doesn't stop there! Oh, no! Hell no! He's just warming up...

### CASE OLD #2 0100 1800 0500 0600 0D00 1700 0B00 0900
### CASE NEW    0100 0D00 0500 0B00 0963 0961 09CD 093B 0919 09XX ... ... 1700 1800 0600

What on Earth does "CASE OLD" and "CASE NEW" mean? What is he referring to? I mean, I see the same CAIDs in both lines, the same format, so WTF?!? And how many do we put in - 16 or 24?

3) After that, individual encryption systems follow, with maximum 10 provider IDs, per encryption system [= CAID?], I guess.

So, does that mean that above, under 1), we were setting the priority of general CAIDs or was it repeated under 3)? If so, why? Should it not be 09xx under 1) and then under special section for NDS in 3), we put the individual variances of NDS smartcards? Confused and confusing, this guy seems...

No wonder MultiCAS is struggling with finding the best server and keeping it connected.

I couldn't get it to connect to even one N-line, while actually watching a channel. It connects in the Newcamd Client menu al-right but it never uses N-lines to actually decrypt channels...

I have tested it on the same channels as OSCam and OSCam v. 4906 does a much better job!!! With only C lines, as it doesn't do N-lines over DynDNS very well, yet... at least in my experience and that of some of my colleagues...