Encryption in .NET 2.0 remoting across different domains

[timmmahh]

I want to use the new encryption capabilities in .NET 2.0 remoting
(e.g using the secure attribute).

I've got my demo to work on a single and multiple server deployment in
the same domain, but will this also work across different domains or
workgroups? I've not looked into the authenticate issues thus far, so
would appreciate it if someone could let me know!

Thanks in advance

 

[Doug Semler]

I want to use the new encryption capabilities in .NET 2.0 remoting
(e.g using the secure attribute).

I've got my demo to work on a single and multiple server deployment in
the same domain, but will this also work across different domains or
workgroups? I've not looked into the authenticate issues thus far, so
would appreciate it if someone could let me know!

Thanks in advance

As far as I know, all of the encryption capabilities of the framework rely
on the authentication methods provided by domain services. As long as there
is trust set up between two domains, I don't see that you would have an
issue with it. However, I haven't tried it.

With workgroups, you're pretty much SOL, because there is no authentication
service.

--
Doug Semler, MCPD
a.a. #705, BAAWA. EAC Guardian of the Horn of the IPU (pbuhh).
The answer is 42; DNRC o-
Gur Hfrarg unf orpbzr fb shyy bs penc gurfr qnlf, abbar rira
erpbtavmrf fvzcyr guvatf yvxr ebg13 nalzber. Fnq, vfa'g vg?