Re: MC no longer working with cygwin 3.1.x

Re: MC no longer working with cygwin 3.1.x

[Ken Brown]

[Moving from cygwin to cygwin-developers.]

Hi Corinna,

On 12/19/2019 4:24 AM, Corinna Vinschen wrote:
> Ken, btw., we should add a PIPE_REJECT_REMOTE_CLIENTS flag, just for
> paranoia.

Should this be FILE_PIPE_REJECT_REMOTE_CLIENTS?  It seems that most of the flags 
for NtCreateNamedPipeFile start with "FILE_".

And which argument of NtCreateNamedPipeFile should that flag be in?  None of 
them seem quite right to me.  Or is there some other function that should be 
called after NtCreateNamedPipeFile to set that flag?

Last question: The only documentation I found for NtCreateNamedPipeFile is here:

 
http://undocumented.ntinternals.net/index.html?page=UserMode%2FUndocumented%20Functions%2FNT%20Objects%2FFile%2FNtCreateFile.html

Is there anything better?

Thanks.

Ken

Re: MC no longer working with cygwin 3.1.x

[Corinna Vinschen]

[-- Attachment #1: Type: text/plain, Size: 1178 bytes --]

Hi Ken,

On Dec 21 15:48, Ken Brown wrote:
> [Moving from cygwin to cygwin-developers.]
> 
> Hi Corinna,
> 
> On 12/19/2019 4:24 AM, Corinna Vinschen wrote:
> > Ken, btw., we should add a PIPE_REJECT_REMOTE_CLIENTS flag, just for
> > paranoia.
> 
> Should this be FILE_PIPE_REJECT_REMOTE_CLIENTS?  It seems that most of the flags 
> for NtCreateNamedPipeFile start with "FILE_".

Right, it's FILE_PIPE_REJECT_REMOTE_CLIENTS, sorry about that.

> And which argument of NtCreateNamedPipeFile should that flag be in?  None of 
> them seem quite right to me.  Or is there some other function that should be 
> called after NtCreateNamedPipeFile to set that flag?

AFAICS it's a flag added to the message type, i.e.

  FILE_PIPE_MESSAGE_TYPE | FILE_PIPE_REJECT_REMOTE_CLIENTS

> Last question: The only documentation I found for NtCreateNamedPipeFile is here:
>  
> http://undocumented.ntinternals.net/index.html?page=UserMode%2FUndocumented%20Functions%2FNT%20Objects%2FFile%2FNtCreateFile.html
> 
> Is there anything better?

Not that I'm aware of.   There's only this and the Reactos source.


Corinna

-- 
Corinna Vinschen
Cygwin Maintainer

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

Re: MC no longer working with cygwin 3.1.x

[Ken Brown]

On 12/21/2019 2:26 PM, Corinna Vinschen wrote:
> Hi Ken,
> 
> On Dec 21 15:48, Ken Brown wrote:
>> [Moving from cygwin to cygwin-developers.]
>>
>> Hi Corinna,
>>
>> On 12/19/2019 4:24 AM, Corinna Vinschen wrote:
>>> Ken, btw., we should add a PIPE_REJECT_REMOTE_CLIENTS flag, just for
>>> paranoia.
>>
>> Should this be FILE_PIPE_REJECT_REMOTE_CLIENTS?  It seems that most of the flags
>> for NtCreateNamedPipeFile start with "FILE_".
> 
> Right, it's FILE_PIPE_REJECT_REMOTE_CLIENTS, sorry about that.
> 
>> And which argument of NtCreateNamedPipeFile should that flag be in?  None of
>> them seem quite right to me.  Or is there some other function that should be
>> called after NtCreateNamedPipeFile to set that flag?
> 
> AFAICS it's a flag added to the message type, i.e.
> 
>    FILE_PIPE_MESSAGE_TYPE | FILE_PIPE_REJECT_REMOTE_CLIENTS

OK, I'll give that a try.  I wouldn't have guessed that from the documentation, 
which suggests that the pipe type argument is BOOLEAN and is supposed to be 
FILE_PIPE_MESSAGE_TYPE == 1 or FILE_PIPE_BYTE_STREAM_MODE == 0.  On the other 
hand, the defines in /usr/include/w32api/ddk/ntifs.h show that

FILE_PIPE_TYPE_VALID_MASK == FILE_PIPE_MESSAGE_TYPE | 
FILE_PIPE_REJECT_REMOTE_CLIENTS,

which is consistent with what you said.

>> Last question: The only documentation I found for NtCreateNamedPipeFile is here:
>>   
>> http://undocumented.ntinternals.net/index.html?page=UserMode%2FUndocumented%20Functions%2FNT%20Objects%2FFile%2FNtCreateFile.html
>>
>> Is there anything better?
> 
> Not that I'm aware of.   There's only this and the Reactos source.

Thanks, I didn't know about Reactos.

Ken