DCE to be released under the LGPL
From: | e.kostelkova-AT-opengroup.org | |
To: | lwn-AT-lwn.net | |
Subject: | The Open Group Debuts Open Source Licensing of DCE Source Code - release | |
Date: | Wed, 12 Jan 2005 18:01:11 EST |
The Open Group Debuts Open Source Licensing of DCE Source Code Sponsors Include IBM, Hewlett-Packard, Entegrity, Penn State and Chalmers San Francisco, CA January 12, 2005 The Open Group announced that the source code of the Distributed Computing Environment (DCE), an industry-standard, vendor-neutral set of distributed computing technologies, is being made available under an Open Source license. The Open Group's initiative will broaden the use of DCE concepts and components as a vendor-neutral interoperability infrastructure. "The Open Group's members are committed to working with the open source community to promote interoperability," said Allen Brown, President and CEO of The Open Group. "Secure, scalable interoperability is the foundation of exchange and usability of data within and across organizational boundaries - the key to Boundaryless Information Flow(TM)." Previously, the DCE source was only available under a traditional license. Making it available under a recognized open source license (LGPL) both increases the accessibility of DCE as an interoperability technology, and permits a broader community to work on the source to expand its features and keep it current. The Open Group will work with the DCE community to make DCE available to the open source development community, as well as continuing to offer the source through The Open Group's web site at: http://www.opengroup.org/dce/ "I am pleased to hear the DCE 1.2 program sponsors have agreed to contribute the DCE source code to the open source community," said William Estrem, Principal of Metaplexity Associates and former chairman of the Open Software Foundation End User Forum, who had served as the customer representative on the DCE 1.2 program steering committee. "This is a long anticipated event. I know of several developers who are very interested in working with the code to provide better implementations of existing DCE applications and to create new distributed systems." "It's great to see DCE -- the first secure secure enterprise computing platform -- finally available for development by the OSS community," said Rich Salz, Chief Security Architect at Data Power Technology. "Its size alone makes it both a formidable challenge to, and testament in the belief of, the open source community. I look forward to seeing new release of DCE used to solve real-world enterprise computing problems." Jeremy Allison from the Samba Team, noted: "DCE is one of the core infrastructure technologies used in computing today. I'm delighted to see it being made available under a Free Software licence. This will promote the wider adoption of DCE in the Open Source/Free Software community" About DCE The Distributed Computing Environment (DCE) is an industry-standard, vendor-neutral set of distributed computing technologies. It provides a complete Distributed Computing Environment infrastructure, including security services to protect and control access to data, name services that make it easy to find distributed resources, and a scalable model for organizing widely scattered users, services, and data. DCE runs on all major computing platforms and is designed to support distributed applications in heterogeneous hardware and software environments. As a mature product with three major releases and the only middleware system with a comprehensive security model, it is deployed worldwide in critical business environments. For more information, visit http://www.opengroup.org/dce/introduction.htm About The Open Group The Open Group is a vendor-neutral and technology-neutral consortium, which drives the creation of Boundaryless Information Flow(TM) that will enable access to integrated information within and between enterprises based on open standards and global interoperability. The Open Group works with customers, suppliers, consortia and other standard bodies. Its role is to capture, understand and address current and emerging requirements, establish policies and share best practices; to facilitate interoperability, develop consensus, and evolve and integrate specifications and open source technologies; to offer a comprehensive set of services to enhance the operational efficiency of consortia; and to operate the industry's premier certification service. Further information on The Open Group can be found at http://www.opengroup.org. Note to Editors: Boundaryless Information Flow is a trademark of The Open Group. ###
Posted Jan 13, 2005 1:09 UTC (Thu)
by mightyduck (guest, #23760)
[Link] (4 responses)
Posted Jan 13, 2005 6:33 UTC (Thu)
by XERC (guest, #14626)
[Link] (3 responses)
Posted Jan 13, 2005 10:16 UTC (Thu)
by ayeomans (guest, #1848)
[Link] (2 responses)
By the way, the definition of "commercial use" in the older licence only referred to commercial distribution. Commercial organisations were still freely allowed to use it for internal business purposes.
Certainly Good News!
Posted Jan 14, 2005 7:08 UTC (Fri)
by Ross (guest, #4065)
[Link] (1 responses)
What is the difference between MS DCE and Unix DCE anyway? Is it another
Actually I have lots of questions about DCE. If someone could write up a
Posted Jan 23, 2005 23:28 UTC (Sun)
by miallen (guest, #10195)
[Link]
Kerberos - Third party authentication system. You ask the KDC for a "ticket" for a particular target server / service. Kerberos is a really great system BTW. The OSS community should be delighted MS chose to use Kerberos.
DFS - There's actually DCE DFS and MS DFS which both are acronyms for "Distributed File System" but are actually /completely/ different things. DCE DFS is a full blown filesystem like NFS or CIFS whereas MS DFS is just a trivial redirection mechanism.
RPC - Three's ONC RPC and DCE RPC which are both "Remote Procedure Call" mechanisms but are totally incompatible. DCE RPC is a little more sophisticated and MSRPC (which is DCE RPC with minor adjustments) is a little easier to use. ONC RPC is simpler and has had fewer security problems.
XDR - eXtensible Data Representation is a binary format for serialized complex strutures used by ONC RPC.
NDR - Network Data Representation is also a binary format for serialized complex structures used by DCE RPC (and thus MSRPC). It is not compatible with XDR but serves the same purpose.
UUIDs - Universally Unique IDentifiers are guaranteed unique numbers (given a unique MAC address) used to identify objects in a distributed environment.
IDL - Interface Definition Language is a very simple language used to define structures and operations that when "compiled" will generate "proxys" and "stubs" that implement the local and remote functions to make Remote Procedure Calls. ONC RPC and DCE RPC (and just about every other RPC mechanism) uses IDL to describe interfaces for remote procedure calls.
AFS - Andrew File System is what DCE DFS is based on.
DCOM - DCOM is an extension to DCE RPC also used by MS.
If you really want to know what the impact is of releasing DCE 1.2 I would have to say not much. The code is actually a little too big and complicated for a few weekend warrior guys to pick up and maintain. For example if you look at the IDL compiler it's around 30,000 lines of crazily complex code.
As is, the DCE version released won't even compile on a Linux machine. Someone will probably convert it to use autoconf and get to compile on a modern *nix but I doubt the result will be used seriously in a production environment. There just isn't enought support. There would have to be a huge community response before people would even consider it. Some pieces might be sucessful if they're broken out - like DFS maybe.
Posted Jan 13, 2005 3:28 UTC (Thu)
by busterb (subscriber, #560)
[Link]
Great! I always liked DCE. DCE to be released under the LGPL
Great! ...
DCE to be released under the LGPL
May be You are just "speaking too soon".
From DCE portal:
... The Open Group is currently making available the following
versions of Distributed Computing Environment (DCE) available for
non-commercial use:...
Give them a chance to update the web site. The OpenDCE Project has been doing the work on LGPL licencing for many years. See the announcement in the mailing list.
DCE to be released under the LGPL
Wasn't there another open DCE project that was geared more towardDCE to be released under the LGPL
interoperability with Windows?
"embrace and extend" situation? Are any of the extensions useful enough
to port back into the Open Group's version?
short overview explaining the various technologies and terms (Kerberos,
RFS, DFS, RPC, XDR, NDR, UUIDs, IDL, etc. I would be grateful :) Also: How
are the protocols layered? Which parts are considered part of DCE and which
aren't? Are the various implementations compatible? How does AFS fit in?
How do Microsoft's protocols (Kerberos, MSRPC, MSDCE, DCOM) fit in -- for
example, I have seen DCOM mentioned as an OpenGroup standard.
MS just uses the RPC runtime of DCE so there isn't a lot of incentive to mix the two implementations. MS uses a custom ncacn_np named pipe transport for a lot of remote management functions. The RPC tool chain is a little different itself but is mostly compatible. I would say this is a case of "embrace and extend" but IMHO I don't really see it as a big deal (and there are cases that have been characterized as "embrace and extend" that are not -- the use of the Kerbros authorization-data field for the PAC was used as anyone familiar with Kerberos would expect).DCE to be released under the LGPL
Not to mention that it is the precursor of DCOM. I wonder if we might DCE to be released under the LGPL
finally get DCOM interoperability in Unix, as there is still a lot of
stuff in the Win32 world that uses it. I would be interested in
communicating with WMI via a Unix box.