NEW! CCcam 2.3.0 RELEASED!

[unadkat]

Cccam 2.3.0

Changelog:


-add seca tunneled nagra card support (may need card reset to see new revision after updating)
-add SID LIMIT (see CCcam.cfg for details)
-several smartcard fixes
-several network fixes

ORF ICE HD+ schwarz

On linux boxes u can do a upgrade from the TS panel!

For manual install - FTP the file to your tmp folder and do a manual installation.

[jimbo]

have found this info. SO BEWARE
Taken from another forum. (chinese dream box)
Quelle: Cccamforum

Zitat:
CCCAM 2.3.0 is taking the backdoor crap even a step further.

The lowest scum of the earth, UVADI TEAM, have done it even better this time. Making sure sharing will die for sure if they keep this crap up.

Before I continue, I would urge people with BRAINS and PROGRAMMING SKILLS, to download IDA PRO (torrent) and decompile it for themselfs to find the ******** remotely triggered backdoor.

How it works.

When you install CCcam 2.3.0 , nothing special is happening at first, and cccam will check for input activity on the pc or box to make sure nobody is watching. When it finds itself comfortably alone, it will start sending your ENTIRE CCCAM.CFG info to this IP 176.9.242.159 (a rented root server in germany).
Now I recompiled a version so I could trigger the backdoor myself, and TADA, some ******** ITALIAN dialup asswipe connected to the server I just set up , IP : 2.32.190.9. So traffic on my card started. THIS THEY CAN NOT HIDE in Cccam, it shows as a CONNECTED CLIENT from one of your clients in cccam.cfg where the dyndns has been removed (still lack of cccam, if dyndns is non-existing) the security feature doesn't work anymore and everybody can connect on that user.

I have 2 words for UVADI TEAM -> YOU SUCK !!!!!!

The future of CCcam is dead thanks to these low life asswipes , just after free sharing and making their own "spidernetwork" on your card.

BLOCK ALL CLIENTS that have 2.3.0 connected to your server as it will still read all connected clients from the server, trough the client !!

latest original CCcam 2.1.3 and 2.1.4 which are secure and don't have this backdoor code.


ps: AGAIN , if you don't want to take the warning for granted, decompile and look for yourself !!!!!!! "

__________________________________________________ _____________

Test these commands with Telnet :

netstat (will work also on dreambox, as well as PC Linux)

tcpdump (PC Linux)

[cable man]

Al stick with 2.1.4.....................

[unadkat]

Originally Posted by jimbo

have found this info. SO BEWARE
Taken from another forum. (chinese dream box)
Quelle: Cccamforum

Zitat:
CCCAM 2.3.0 is taking the backdoor crap even a step further.

The lowest scum of the earth, UVADI TEAM, have done it even better this time. Making sure sharing will die for sure if they keep this crap up.

Before I continue, I would urge people with BRAINS and PROGRAMMING SKILLS, to download IDA PRO (torrent) and decompile it for themselfs to find the ******** remotely triggered backdoor.

How it works.

When you install CCcam 2.3.0 , nothing special is happening at first, and cccam will check for input activity on the pc or box to make sure nobody is watching. When it finds itself comfortably alone, it will start sending your ENTIRE CCCAM.CFG info to this IP 176.9.242.159 (a rented root server in germany).
Now I recompiled a version so I could trigger the backdoor myself, and TADA, some ******** ITALIAN dialup asswipe connected to the server I just set up , IP : 2.32.190.9. So traffic on my card started. THIS THEY CAN NOT HIDE in Cccam, it shows as a CONNECTED CLIENT from one of your clients in cccam.cfg where the dyndns has been removed (still lack of cccam, if dyndns is non-existing) the security feature doesn't work anymore and everybody can connect on that user.

I have 2 words for UVADI TEAM -> YOU SUCK !!!!!!

The future of CCcam is dead thanks to these low life asswipes , just after free sharing and making their own "spidernetwork" on your card.

BLOCK ALL CLIENTS that have 2.3.0 connected to your server as it will still read all connected clients from the server, trough the client !!

latest original CCcam 2.1.3 and 2.1.4 which are secure and don't have this backdoor code.


ps: AGAIN , if you don't want to take the warning for granted, decompile and look for yourself !!!!!!! "

__________________________________________________ _____________

Test these commands with Telnet :

netstat (will work also on dreambox, as well as PC Linux)

tcpdump (PC Linux)

This is only related to the server and not the client from my understanding according to the article above.


If what is said above in regards to the cam connecting to an alternative server and sending your config file is true then am sure alot of the clients would have been blocked for sharing lines.

Also yes the soft-cam does have a exploit as I have been told before in the past but again its only if you have a server. Other then that there is nothing to worry about and perfectly safe to use as a client.

it shows as a CONNECTED CLIENT from one of your clients in cccam.cfg where the dyndns has been removed (still lack of cccam, if dyndns is non-existing) the security feature doesn't work anymore and everybody can connect on that user.

Not sure how this is possible because if your connected to a server which uses cccam then you cant re share that line. What am trying to say is that a client would not be able to re share the line, how is it possible for other people to connect through you?

[jimbo]

only posting what i found, have no idea how it works unadkat, just warning ppl that there might be a risk, but ur saying theres not then?

[unadkat]

Originally Posted by jimbo

only posting what i found, have no idea how it works unadkat, just warning ppl that there might be a risk, but ur saying theres not then?

Hi mate

don't get me wrong, I know you got the info from somewhere else and was just pasting it on the forum.

I personally don't know how it all works but considering that alot of the folks do use cccam of all versions in the new one and seeing as there has been no reports of so called sharing issues reported in regards to clients being banned for ''sharing'' which is why it seems all so strange on what that article reports specially where they state that the config file is being so called stolen from the clients box and then in return allowing the other people to connect to the clients box ? The way I see it is that it all sounds fake then anything else

if the individual owns a server then yes it is understanable where one can have his her server details being hacked and then allowing peeps to connect to it for free and so on.

But on the client side the idea seems way to impossible, specially when a client is unable to share the line when he or she does not have the re share permission.

I don't know how to explain it but to be honest its perfectly safe to use cccam 2.2.1 or even 2.3.0 as a client.

Plus after speaking to someone he also stated that the issue is related to the server side and nothing to the client side mate.

the above article is more for server owners then for clients. Which is why server owners only use either cccam 2.1.3 or 2.1.4.

[lincsat]

I think what they are trying to say is the CAM sends your config file to the remote server so others can use your C Lines, naturally when you try to use the C Line in 2 places at once, it will get kicked off both.

However, when using CCcam as a server rather than a client, they could see lines that are not currently in use and make use of them.

If I understand the article it's best to tie each line to an IP address or Domain to prevent un-authorised use.

I think that makes sense

[unadkat]

Originally Posted by lincsat

I think what they are trying to say is the CAM sends your config file to the remote server so others can use your C Lines, naturally when you try to use the C Line in 2 places at once, it will get kicked off both.

However, when using CCcam as a server rather than a client, they could see lines that are not currently in use and make use of them.

If I understand the article it's best to tie each line to an IP address or Domain to prevent un-authorised use.

I think that makes sense

I think what you have stated is spot on mate!

[jimbo]

well it seems from what ive been told its poppy cock what i posted, but heyho i wasnt to know lol

[River-Rat]

read on over 12 sites to stay away from 2.3 so still on 2.011