NewsAndHistory
March 15th, 2009, 04:21 PM
Would any of you please tell me how to disable DComLaunch? I have Windows XP SP3. I don't want DComLaunch to be running because it's a security-risk. I know it's possible to remove DCOMLaunch, but I don't know what application I should use to securely disable it and/or block the port, by which it's accessed. It's a waste because I don't plan to get any updates from Microsoft, and DCom is known to be exploited by viruses.
Quote about DCOM at DCOMBulator page: http://www.softpedia.com/get/Security/Security-Related/DCOMbobulator.shtml
-{ Quote: "Windows employs a component-based system to help programmers manage Windows' complexity. This system is called COM for "Component Object Model."
Much of Windows itself, and many Windows programs, are assembled from individual COM components. Microsoft thought it would be "cool" if these COM components could find and use each other from different machines across a network, so Distributed COM (DCOM) was created to allow this.
DCOM uses an existing networking protocol known as Remote Procedure Call (RPC), usually over Internet port 135, to host COM's distributed operation across a network.
What's the problem?
The problem is that this very powerful DCOM system, which allows pieces of your computer to be remotely activated and used from across a network -- even by any stranger across the Internet -- is always enabled in Windows systems by default.
Microsoft's most recent DCOM patch, which fixes another (not the first) remotely exploitable vulnerability in this complex system, continues to defiantly leave the whole DCOM system exposed and enabled . . . and waiting for the next vulnerability to be discovered." }-
Quote about DCOM at DCOMBulator page: http://www.softpedia.com/get/Security/Security-Related/DCOMbobulator.shtml
-{ Quote: "Windows employs a component-based system to help programmers manage Windows' complexity. This system is called COM for "Component Object Model."
Much of Windows itself, and many Windows programs, are assembled from individual COM components. Microsoft thought it would be "cool" if these COM components could find and use each other from different machines across a network, so Distributed COM (DCOM) was created to allow this.
DCOM uses an existing networking protocol known as Remote Procedure Call (RPC), usually over Internet port 135, to host COM's distributed operation across a network.
What's the problem?
The problem is that this very powerful DCOM system, which allows pieces of your computer to be remotely activated and used from across a network -- even by any stranger across the Internet -- is always enabled in Windows systems by default.
Microsoft's most recent DCOM patch, which fixes another (not the first) remotely exploitable vulnerability in this complex system, continues to defiantly leave the whole DCOM system exposed and enabled . . . and waiting for the next vulnerability to be discovered." }-