CHANGELOG
2.1.0
-keep persistant ecm counts for clients
-i2 emu
-IGNORE NODE option (see CCcam.cfg)
-emm caid tunneling
-Added seca handler to prefer or ignore SECA2 or SECA3 (see CCcam.cfg)
ofcourse we like to keep you informed when we get new versions
Look Here -> |
Any one have any info on the i2 emu? could this be used to run the details from a legit au* card in a dream? I have a Legit sub but dont like the way they make me use there box.
Thanks
When did the non standard IR2 come out? did it happen when they did the card marrying?
In AUS what would I2 emu be good for?
Is it true that CCcam 2.1.0 is causing problems for clone dreamboxes ?
from another forum
The CCcam 2.1.0 is a "clone killer"
So, the ONLY 2.1.0 connects to CCcam on Dream boxes. None Flyccam, no Diablo, no IncubusCamd, no clone boxes (they recognize) and of course they are not running at Clones.
The 2.1.0 is a "clone killer"
Response from another member.
It doesn't actually kill clones...
They _have_ changed the protocol obfuscation to prevent the open (reverse-engineered) alternatives from interacting with the "official" version, but this is done to maintain the illusion/deception necessary for large scale pay-schemes.
As long as the only thing that can talk to cccam is cccam, a cccam server can impose arbitrary limitations on the cccam clients... whereas a 3rd party cccam-compatible client could choose to ignore any such restrictions, making pay shares harder (since users could band together and "reshare" infinitely, for no charge).
They can never fully avoid the approach used by emubox and emudrag however... anyone interested in opening up cccam should look at that source
Bookmarks