Socket security like HttpWebRequest

[Mubashir Khan]

We have noticed that HttpWebRequest uses the Credentials property and Proxy
property to perform security checks. Could any one help us that we subclass
socket with these properties. we have used SSLStream but that uses SSL not
the security techniques used by HttpWebRequest. Can anyone help us on how we
could provide the same functionality on the sockets.

[Joe Kaplan]

NegotiateStream will allow you to use Negotiate authentication (integrated
auth). You can also supply plaintext creds. Otherwise similar to SslStream.

--
Joe Kaplan-MS MVP Directory Services Programming
Co-author of "The .NET Developer's Guide to Directory Services Programming"
http://www.directoryprogramming.net
"Mubashir Khan" <Mubash...@discussions.microsoft.com> wrote in message
news:47B6F881-C268-4713...@microsoft.com...

[Mubashir Khan]

ok one more question can we use both NegotiateStream and SSLStream together.
Means we pass NetworkStream of TcpipClient into NegotiateStream and
NegotiateStream into SSLStream. can this be done.

Thanks
Mubashir

"Joe Kaplan" wrote:

> .
>

[Joe Kaplan]

I'm not sure. Try it and see if you can get it to work.

I think you would probably have SSL on the "outside" of the stream if you
were to do that but I don't know. If you do try it, I suggest you avoid
using the features on NegotiateStream to add channel encryption and signing.
You don't want that done twice.

My other suggestion would be to not do this. Since NegotiateStream has
channel encryption and signing features built in, you really don't need SSL
at that point. You can get all the same benefits by just using
NegotiateStream.

--
Joe Kaplan-MS MVP Directory Services Programming
Co-author of "The .NET Developer's Guide to Directory Services Programming"
http://www.directoryprogramming.net
"Mubashir Khan" <Mubash...@discussions.microsoft.com> wrote in message

news:7AAAC968-EC4B-4EE8...@microsoft.com...