|
Browse by Tags
All Tags » Named Pipes ( RSS)
-
|
My previous post looked at the Mandatory Integrity Control mechanism and what it means for named pipe communication in general. Now I turn to dealing with this issue in WCF. The scenario I particularly want to support is a WCF service hosted in a Windows...
|
-
|
The release of Windows Vista introduced a completely new dimension to the Windows operating system’s security model for determining what code executing in user mode can do. In addition to the concepts of access rights, and system privileges, user mode...
|
-
|
This is the third in a series of posts looking at the detail of how message exchanges occur over a WCF channel using the named pipe binding. In the first post of the series , we introduced the Framing Protocol. In the second we looked into the protocol...
|
-
|
This is the second in a series of posts looking at the detail of how message exchanges occur over a WCF channel using the named pipe binding. In the first post of the series , we introduced the Framing Protocol, saw how it included an upgrade phase whereby...
|
-
|
This is the first in a short series of posts looking into the detail of how message exchanges occur over a WCF channel using the named pipe binding. Although I first introduced this question in the context of a security vulnerability of this binding in...
|
-
|
I’ve mentioned previously the vulnerability to squatting attacks of WCF services using the standard NetNamedPipe binding in .NET version 3.5, and promised to show how it might be done. Let’s review the nature of the vulnerability. First, the attacker...
|
-
|
To finish where I left off last time , a quick look at the P/Invoke code we need in order to find the shared memory location where the pipe name is published, and read the pipe name from it. Shared memory is implemented by Windows using the same mechanism...
|
|
|
|