Hi Colin,
Perhaps have a look at the CCB (client control block) of the pipe.
If ClientSession is NULL the client is the local machine.
Else you might look at the Process pointer and work it from there.
The CCB is initialized in NpCreateClientEnd.
Struct _EPROCESS is declared eg. in pstypes.h.
HT
You literally wrote " but this is neither supported under Windows
Server 2003", so yes, there's your answer :)
Best regards,
Alex Ionescu
On Tue, Oct 11, 2016 at 1:18 PM, Colin Finck wrote:
> Am 10.10.2016 um 23:22 schrieb Timo Kreuzer:
>> #define FSCTL_PIPE_GET_CONNECTION_ATTRIBUTE
>> CTL_CODE(
Am 10.10.2016 um 23:22 schrieb Timo Kreuzer:
> #define FSCTL_PIPE_GET_CONNECTION_ATTRIBUTE
> CTL_CODE(FILE_DEVICE_NAMED_PIPE, 12, METHOD_BUFFERED, FILE_ANY_ACCESS)
>
> static const char AttributeName[] = "ClientComputerName";
>
> Status = NtFsControlFile(NamedPipeHandle,
Are you sure thi
You need to send an FSCTL to the named pipe file system driver.
// defined in ntifs.h
#define FSCTL_PIPE_GET_CONNECTION_ATTRIBUTE
CTL_CODE(FILE_DEVICE_NAMED_PIPE, 12, METHOD_BUFFERED, FILE_ANY_ACCESS)
static const char AttributeName[] = "ClientComputerName";
Status = NtFsControlFile(
