Whats' with Cli.exe?

  • Thread starter Thread starter Jimmy
  • Start date Start date
J

Jimmy

I am trying to learn more about this application. Google doesn't help much.
It seems to be part of CCC but I want to know why it is always asking to
connect to internet. I have blocked it with ZoneAlarm but it still shows it
is listening on ports 1027,1040 and 1049.

J.
 
Jimmy said:
It doesn't seem to want to work unless I allow internet access. I
wonder what it is listening to and reporting home about?
Click to expand...


What addresses does it look at?

If its 127.0.0.1 it looking at a server on your machine. It's quite
possible that the CCC has a server/client architecture and accesses some
information over "the internet", but in fact it's just doing an internal
loopback in your machine and the information never even touches your network
device.

If you were me, you'd give up on the CCC and get "ye olde skool" Control
Panel drivers, they're smaller, faster and come without cli.exe.

Ben
 
Ben said:
What addresses does it look at?

If its 127.0.0.1 it looking at a server on your machine. It's quite
possible that the CCC has a server/client architecture and accesses
some information over "the internet", but in fact it's just doing an
internal loopback in your machine and the information never even
touches your network device.

If you were me, you'd give up on the CCC and get "ye olde skool"
Control Panel drivers, they're smaller, faster and come without
cli.exe.
Ben
Click to expand...

I have been reading of many that are not using CCC so I guess I will do the
same and remove it. I was curious about this new application and why it was
acting like it is.

J.
 
Jimmy said:
I have been reading of many that are not using CCC so I guess I will
do the same and remove it. I was curious about this new application
and why it was acting like it is.
Click to expand...

..NET (which the CCC is built on), makes it easy to use web based
technologies to transfer data, I suspect that they have done that and this
is why your firewall is telling you it's trying to access the net.

If you set your firewall up so that anything with a source address of
127.0.0.1 can access anything with a destination address of 127.0.0.1, then
it probably won't complain any more. The security implications are
minimal - if there is a process running on your machine then it doesn't need
to access the local machine via IP to do nasty things. It's probably more
secure than saying "yes, always" to a program when it accesses 127.0.0.1 and
then having it access external addresses later.

Ben
 
Ben said:
.NET (which the CCC is built on), makes it easy to use web based
technologies to transfer data, I suspect that they have done that and
this is why your firewall is telling you it's trying to access the
net.
If you set your firewall up so that anything with a source address of
127.0.0.1 can access anything with a destination address of
127.0.0.1, then it probably won't complain any more. The security
implications are minimal - if there is a process running on your machine
then it
doesn't need to access the local machine via IP to do nasty things. It's
probably more secure than saying "yes, always" to a program when
it accesses 127.0.0.1 and then having it access external addresses
later.
Ben
Click to expand...
Well then maybe I will not remove it until I try it out.

J.
 
Jimmy said:
Well then maybe I will not remove it until I try it out.
Click to expand...

The thing that bugs me is all of this .NET use in stuff that has no need for
any kind of network access.
 
J. Clarke said:
The thing that bugs me is all of this .NET use in stuff that has no
need for any kind of network access.
Click to expand...

Ya, so where is all this going anyway? I sure can't keep up. SP2 - SATA
drives - HT - HDTV - .NET....?

J.
 
J. Clarke said:
The thing that bugs me is all of this .NET use in stuff that has no
need for any kind of network access.
Click to expand...


Yeah, but .NET is more about the common language infrastructure (CLI) and
managed code than network access. I was pretty sceptical until I looked
into it, CLI is actually a pretty useful idea. http://www.mono-project.com
is an effort to make this all work in Linux, and since the standards that
..NET sit on are open, it shouldn't be as hard is could be. In this light,
it makes more sense, and seems to be able to take on Java face on.

Ben
 
Ben said:
Yeah, but .NET is more about the common language infrastructure (CLI) and
managed code than network access. I was pretty sceptical until I looked
into it, CLI is actually a pretty useful idea.
http://www.mono-project.com is an effort to make this all work in Linux,
and since the standards that
.NET sit on are open, it shouldn't be as hard is could be. In this light,
it makes more sense, and seems to be able to take on Java face on.
Click to expand...

If it's being used in stuff that doesn't need Internet access then it seems
to me that it's more Microsoft cleverness that will blow up in their faces.
Tried to open a help file the other day, wouldn't open until I tweaked some
registry settings, because Microsoft, having fixed their system so that
local files get opened in the same application that is used to open files
over the Internet, found it necessary to then prevent that application from
opening local files. I saw that one coming ages ago.
 
Back
Top