Jump to content

Distributed Component Object Model

From Wikipedia, the free encyclopedia

This is an old revision of this page, as edited by Mr.weedle (talk | contribs) at 06:31, 3 August 2022 (Added sources template). The present address (URL) is a permanent link to this revision, which may differ significantly from the current revision.

"Dcom" redirects here. For the doctoral degree, see Doctor of Commerce. For other uses, see DCOM (disambiguation).

Distributed Component Object Model (DCOM) is a proprietary Microsoft technology for communication between software components on networked computers. DCOM, which originally was called "Network OLE", extends Microsoft's COM, and provides the communication substrate under Microsoft's COM+ application server infrastructure.

The addition of the "D" to COM was due to extensive use of DCE/RPC (Distributed Computing Environment/Remote Procedure Calls) – more specifically Microsoft's enhanced version, known as MSRPC.

In terms of the extensions it added to COM, DCOM had to solve the problems of:

  • Marshalling – serializing and deserializing the arguments and return values of method calls "over the wire".
  • Distributed garbage collection – ensuring that references held by clients of interfaces are released when, for example, the client process crashed, or the network connection was lost.
  • Combining significant numbers of objects in the client's browser into a single transmission in order to minimize bandwidth utilization.

One of the key factors in solving these problems is the use of DCE/RPC as the underlying RPC mechanism behind DCOM. DCE/RPC has strictly defined rules regarding marshalling and who is responsible for freeing memory.

DCOM was a major competitor to CORBA. Proponents of both of these technologies saw them as one day becoming the model for code and service-reuse over the Internet. However, the difficulties involved in getting either of these technologies to work over Internet firewalls, and on unknown and insecure machines, meant that normal HTTP requests in combination with web browsers won out over both of them. Microsoft, at one point, attempted and failed to head this off by adding an extra http transport to DCE/RPC called ncacn_http (Network Computing Architecture connection-oriented protocol). This was later resurrected to support a Microsoft Exchange 2003 connection over HTTP.

DCOM was publicly launched as a beta for Windows 95 September 18, 1996.[1]

DCOM is supported natively in Windows NT 4.0, Windows 2000, Windows XP, and Windows Server 2003, as well as Windows 7, Windows 8, Windows 10, Windows 11, Windows Server 2008, Windows Server 2008 R2, Windows Server 2012, Windows Server 2012 R2, Windows Server 2016, Windows Server 2019, Windows Server 2022.

Hardening

As part of the initiative that began at Microsoft as part of Secure Development Lifecycle to re-architect insecure code, DCOM saw some significant security-focused changes in Windows XP Service Pack 2.[2]

In response to a security vulnerability reported by Tencent Security Xuanwu Lab in June of 2021 [3], Microsoft released security updates for several versions of Windows and Windows Server, hardening access to DCOM.[4]

Alternative versions and implementations

COMsource is a Unix based implementation of DCOM, allowing interoperability between different platforms. Its source code is available, along with full and complete documentation, sufficient to use and also implement an interoperable version of DCOM. COMsource comes directly from the Windows NT 4.0 source code, and includes the source code for a Windows NT Registry Service. [5]

In 1995, Digital and Microsoft announced Affinity for OpenVMS (also known as NT Affinity) which was intended to allow OpenVMS to serve as the persistence layer for Windows NT client-server applications.[6] As part of this initiative, an implementation of the Distributed Component Object Model (DCOM) was added to OpenVMS Alpha.[7] In order to support DCOM, VMS was provided with implementations of the Windows Registry, NTLM authentication, and a subset of Win32 APIs needed to support COM.[8] DCOM was first added to OpenVMS V7.2-1 for the Alpha.[9] A similar implementation of DCOM was added to Digital Unix as part of the AllConnect program.[7]

TangramCOM was a separate project from Wine, focusing on implementing DCOM on Linux-based smartphones.[10]

See also

References

  1. ^ Press Release Announcing DCOM Beta
  2. ^ DCOM Security Enhancements
  3. ^ "Security Update Guide - Microsoft Security Response Center". msrc.microsoft.com. Retrieved 2022-08-03.
  4. ^ "KB5004442—Manage changes for Windows DCOM Server Security Feature Bypass (CVE-2021-26414)". support.microsoft.com. Retrieved 2022-08-03.
  5. ^ "DataSheet COMsource for Solaris, Tru64 UNIX and other Platforms". DataSheet COMsource for Solaris, Tru64 UNIX and other Platforms.{{cite web}}: CS1 maint: url-status (link)
  6. ^ "OpenVMS at 20 Nothing stops it" (PDF). Digital. October 1997. Retrieved 2021-02-12.
  7. ^ a b Gene Cronin, Terence P. Sherlock (2000). COM Beyond Microsoft: Designing and Implementing COM Servers on Compaq Platforms. ISBN 1555582265.
  8. ^ "OpenVMS Connectivity Developer Guide". hpe.com. July 2000. Retrieved 2021-01-01.
  9. ^ "OpenVMS Alpha V7.2-1 Release Notes". odl.sysworks.biz. January 1999. Retrieved 2021-01-01.
  10. ^ "Home - TangramCOM". www.andjoin.com. Retrieved 2022-08-03.
Retrieved from "https://en.wikipedia.org/w/index.php?title=Distributed_Component_Object_Model&oldid=1102066391"