Re: Securing socket communications
- From: "Sharon" <nothing@xxxxxxxxx>
- Date: Sun, 22 Jan 2006 14:16:00 +0200
Thanks for your reply David.
This means that with every installation of my server, i will have to install
IIS,
and possibly a certificate.
I guess i can use IIS only in the login phase, and send back a secret key,
which
will be used to encrypt further socket communications.
But i will use this option only as a last resort.
Regards,
Sharon.
"David Hernandez Diez" <dhdiez@xxxxxxxxxxxxxxxxx> wrote in message
news:ur1xzr0HGHA.2444@xxxxxxxxxxxxxxxxxxxxxxx
> If you are using .NET Remoting you could use an HTTP Channel and benefit
> from the IIS security. You will get "out of the box" security, the
> drawbacks are that you will need to istall IIS and host the remote objects
> in ASP.NET of course the there is always a drawback: performance.
>
>
> Here is an article about .net remoting security:
> http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnnetsec/html/SecNetch11.asp
>
>
> --
> Regards,
> David Hernández Díez
> MCDBA MCSD vs6 & .NET
> DCE5 .Net1.1 & DCE2 .NET 2.0
>
>
>
> Sharon wrote:
>> Hi all.
>> How can i secure socket communications?
>> Is it possible to use ssl?
>> Thanks,
>> Sharon.
.
- Follow-Ups:
- Re: Securing socket communications
- From: Nicholas Paldino [.NET/C# MVP]
- Re: Securing socket communications
- References:
- Securing socket communications
- From: Sharon
- Re: Securing socket communications
- From: David Hernandez Diez
- Securing socket communications
- Prev by Date: Re: Securing socket communications
- Next by Date: A common architectural problem
- Previous by thread: Re: Securing socket communications
- Next by thread: Re: Securing socket communications
- Index(es):
Relevant Pages
|
