WCF named pipe service security

Question

4.00/5 (1 vote)

See more:

Hi I've coded a named pipe application, i'd like to protect my named pipe service so that no one can just write a client to connect to the named pipe and start calling methods on the server, how can i do this in WCF? I know that WCF Named pipes don't support message security but they do support transport security

Posted 25-Feb-11 9:52am

Member 7654832

Updated 27-Feb-11 13:00pm

v2

Add a Solution

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

Patrick Kalkman · Answer 1 · 2011-03-01T08:52:00

The binding NetNamedPipeBinding that you are using is compatible with NTLM or Kerberos authentication. You have to enable it on the transport layer. This could be done through a configuration file. For example:

XML

<security mode="Transport">
   <transport clientCredentialType="Windows" />
</security>

Hope this helps.