Re: Remoting security
From: Ken Kolda (ken.kolda_at_elliemae-nospamplease.com)
Date: 11/29/04
- Next message: Ken Kolda: "Re: How to handle exceptions from RemotingObject?"
- Previous message: Ken Kolda: "Re: Calling a OneWay method on a remoted object that is not alive"
- In reply to: dr: "Remoting security"
- Messages sorted by: [ date ] [ thread ]
Date: Mon, 29 Nov 2004 08:49:01 -0800
Remoting is "insecure" in that it does not provide built-in authnetication
or authorization mechanisms. So, it's up to you to write your own depending
on the needs of your application. The same would apply to any sockets-based
app you wrote yourself. Remoting just provides a nice layer over top of
sockets for transporting method calls between client and server.
Ken
"dr" <dr@discussions.microsoft.com> wrote in message
news:3C1B8CC5-6498-40B8-97CB-E2E7C9E7A414@microsoft.com...
> I want to use remoting to communicate between 2 applications on the same
PC
> but I keep hearing about how remoting is insecure. What are the security
> implications of using remoting locally? Is this any more insecure than
using
> sockets?
- Next message: Ken Kolda: "Re: How to handle exceptions from RemotingObject?"
- Previous message: Ken Kolda: "Re: Calling a OneWay method on a remoted object that is not alive"
- In reply to: dr: "Remoting security"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|