Re: Is there anyway to limit .NET remoting TCP port access to local access only?
From: Keith Patrick (richard_keith_patrick_at_nospam.hotmail.com)
Date: 07/29/03
- Next message: spider: "Re: .NET and buffer overruns"
- Previous message: andrew lowe: "Re: RSACryptoServiceProvider"
- In reply to: Ken Varn: "Is there anyway to limit .NET remoting TCP port access to local access only?"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Date: Mon, 28 Jul 2003 19:16:56 -0500
This may be a bit much, but it would be cool to play with nonetheless: you
could (unless 2K Pro lacks it) use IPv6, couldn't you? It supports
intranet-only sockets, so you'd get very low-level security like the kind
you mention. I haven't touched it yet, so I can't provide much more than
what I've heard about it, though.
- Next message: spider: "Re: .NET and buffer overruns"
- Previous message: andrew lowe: "Re: RSACryptoServiceProvider"
- In reply to: Ken Varn: "Is there anyway to limit .NET remoting TCP port access to local access only?"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Relevant Pages
|
