|
Neohapsis is currently accepting applications for employment. For more information, please visit our website www.neohapsis.com or email hr@neohapsis.com |
Re: DCOM Authentication acrosss NT Domains?
From: Pratyusa M (pratyu22
YAHOO.COM)
Date: Fri Mar 21 2003 - 00:39:50 CST
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
I think this is a very dangerous practice to turn off security in a cross
domain communication. But as you have said, it has to be considered on a
case by case basis.
-Pratyusa
On Thu, 20 Mar 2003 14:49:54 +0100, Yoann DARCHE <y.darcheCEGI.FR> wrote:
>I've resolved this problem by using
>
>CoInitializeSecurity(Nil,
> -1,
> Nil,
> Nil,
> RPC_C_AUTHN_LEVEL_NONE,
> RPC_C_IMP_LEVEL_ANONYMOUS,
>//RPC_C_IMP_LEVEL_IMPERSONATE,
> Nil,
> EOAC_NONE,
> Nil
> );
>
>just after the CoInitialize(Ex) function. This instruction put down all the
>security of the DCOM protocol. I've done this on the server side (your
>object) and the client side (the caller). If the security of your protocol
>don't mind, you can choose this solution, that's work from w98 to XP.
>
>Regards.
>Yoann DARCHE
>(not yet an expert)
>
----------------------------------------------------------------
Users Guide http://discuss.microsoft.com/archives/mailfaq.asp
contains important info. Save time, search the archives at
http://discuss.microsoft.com/archives/index.html .
To unsubscribe, mailto:DCOM-signoff-requestDISCUSS.MICROSOFT.COM
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]