On Sun, Jan 16, 2005 at 05:51:54PM -0600, Rob Shearman wrote:
A DCOM implementation is more than a header file containing a few comments and a few declarations of Win32 functions that are randomly placed in there.
perhaps it would be best for me to provide a reference to something i found on The Open Group's site.
i assume that you (rob) are familiar with and aware of these documents, but for the benefit of those people who are not or might not be, i found these in some [accidental!] research last week and tonight.
http://archive.opengroup.org/dce/meetings/july98/FrankHayes/index.htm http://www.opengroup.org/comsource/ http://www.opengroup.org/pubs/catalog/ax01.htm
in the latter, you may obtain access to the online docs by agreeing to TOG's access conditions.
in the latter, you fill find full information sufficient to implement DCOM.
description of MSRPC, use of NTLM, the works.
note the heavy dependence on DCE/RPC.
one of the services required is a "Registry" and there is full documentation on the registry API.
it is possible to recreate the winreg.idl file from this documentation.
alternatively, you will find one already recreated by matty chapman's "muddle" compiler, available from http://hands.com/~lkcl.
i am attaching it here for your convenience.
FreeDCE is capable of turning this into _useful_ NT-compatible code
FreeDCE has the plugins required to perform NTLM authenticated registry management.
... registry service, anyone? courtesy of wine's present code as a FreeDCE server?
according to the TOG docs, another service required is the "secure service provider".
wow.
l.