CCcam 2.3.0 Backdoor

[gpaolobvt]

Re: CCcam 2.3.0 Backdoor

For those who doubt this, the auther has given you a the way to find out for yourself.

He wrote:
Dis-assemble the CCcam 2.30 file and find out for yourself.

My question is simply: is it possible to download the source code of CCcam2.30 instead of decompile it?

If yes, from where?

[sqazilou]

Re: CCcam 2.3.0 Backdoor

the thread isnt closed yet so i wonder if its really a hoax or a danger ???

[BM300]

Re: CCcam 2.3.0 Backdoor

My question is simply: is it possible to download the source code of CCcam2.30 instead of decompile it?

If yes, from where?

The auther recommends using TsiLang to decompile it yourself.
Sorry, I do not know if the source code is available for download.
You can use Delphi or C++Builder.

-http://www.tsilang.com/download.html

[gpaolobvt]

Re: CCcam 2.3.0 Backdoor

The auther recommends using TsiLang to decompile it yourself.
Sorry, I do not know if the source code is available for download.
You can use Delphi or C++Builder.

-http://www.tsilang.com/download.html

I feel very confortable using Delphi or C++Builder.
I take a look at the url indicated...
In these web pages are described Tsilang Components Suite, that are component to install inside IDE (Delphi or Builder) to build multilanguage application...

I didn't find nothing to decompile an exe.

Am i wrong?


CIAO

[chris9672]

Re: CCcam 2.3.0 Backdoor

I feel very confortable using Delphi or C++Builder.
I take a look at the url indicated...
In these web pages are described Tsilang Components Suite, that are component to install inside IDE (Delphi or Builder) to build multilanguage application...

I didn't find nothing to decompile an exe.

Am i wrong?


CIAO

You can't decompile "exe" with Delphi therefor you need a decompiler, by the way cccam isn't available for
Windows, but at the moment you can only compile windows and Mac OS X/iOSX apps with Delphi!!!

[pirrup]

Re: CCcam 2.3.0 Backdoor

I feel very confortable using Delphi or C++Builder.
I take a look at the url indicated...
In these web pages are described Tsilang Components Suite, that are component to install inside IDE (Delphi or Builder) to build multilanguage application...

I didn't find nothing to decompile an exe.

Am i wrong?


CIAO

you will need to get Ollydbg or IDA pro

[gpaolobvt]

Re: CCcam 2.3.0 Backdoor

You can't decompile "exe" with Delphi therefor you need a decompiler, by the way cccam isn't available for
Windows, but at the moment you can only compile windows and Mac OS X/iOSX apps with Delphi!!!

Thanks, but the post from B300 talked about to use a Tsilang component to decompile. Then it may be possible to study the code generated by using Delphi or Builder. I checked the web tsilang.com/download.html and i didn't see nothing about "decompiler".

you will need to get Ollydbg or IDA pro

I checked on ****** about these "decompiler", and I saw they are basically disassemblers for windows.
I will study about them, but I wonder if it may be correct to use decompiler for windows to decompile a linux binary.

My object is to study the CCa* for my DM800 to see if there are some backdoor inside.....

Ciao

[Triad]

Re: CCcam 2.3.0 Backdoor

If someone knows how to do and interpret it ( Dis-assemble the CCcam 2.30 file ) could he done it and give us info please.

Ppl here are asking how to disassemble Ccam when nobody have tools, and if there are some like mentioned here above than there's no coding knowledge to use it, so nothng real is posted anywayz!!!

There's shorter way to check behaviour of Cccam in log files which you can make.\

Like: WARNINGS when someone connects to your Cline in /tmp

Other files created by CCcam itself while running

warnings.txt ---> /tmp ---->
Here you will find attempted logins to CCcam without your authorization , this file will be shown only if you have this line in CCcam.cfg

LOG WARNINGS : /tmp/warnings.txt

be careful with this file as if you enable it and you have a lot of warnings you will run out of memory in your box.

There's a way for this script to be put in timeline in order to delete itself after some memory consumption so that your Dream doesn't freez itself!

[e_hal9000]

Re: CCcam 2.3.0 Backdoor

the only way is install without any configuration and verify if send or not in the net the informations with a ip trace.

[kalpazanov]

Re: CCcam 2.3.0 Backdoor

I amd using CCcam 2.3.0.

I set logging on my router that traces all activities to and from 176.9.242.159.

Nothing.

Now I should probably mention that I have dm800se with Open Pli 2.1

I installed cccam 2.3.0-r0 via the Plugins menu.

Of course it is always possible to get the cccam package from unsecured source and never know if it has been modified or not.

[piterro]

Re: CCcam 2.3.0 Backdoor

Ppl here are asking how to disassemble Ccam when nobody have tools, and if there are some like mentioned here above than there's no coding knowledge to use it, so nothng real is posted anywayz!!!

There's shorter way to check behaviour of Cccam in log files which you can make.\

Like: WARNINGS when someone connects to your Cline in /tmp

Other files created by CCcam itself while running

warnings.txt ---> /tmp ---->
Here you will find attempted logins to CCcam without your authorization , this file will be shown only if you have this line in CCcam.cfg

LOG WARNINGS : /tmp/warnings.txt

be careful with this file as if you enable it and you have a lot of warnings you will run out of memory in your box.

There's a way for this script to be put in timeline in order to delete itself after some memory consumption so that your Dream doesn't freez itself!

frezz is stop i start use cccam 2.2.1

[dniestre]

Re: CCcam 2.3.0 Backdoor

What version of cccam do you recommend? 2.2.1 is safe? Thanks

[mirny]

Re: CCcam 2.3.0 Backdoor

2.1.3, 2.1.4

[sucan]

Re: CCcam 2.3.0 Backdoor

What version of cccam do you recommend? 2.2.1 is safe? Thanks

Hi, dniestre I'm using 2.2.1. and 2.1.4 without any problems. Try one of them.

[uragano47812]

Re: CCcam 2.3.0 Backdoor

i'm using 2.2.1 i installed also the last one but when i read about the possible malicious code... i returned to 2.2.1.