From: Ken Brown <kbrown@cornell.edu>
To: "cygwin-developers@cygwin.com" <cygwin-developers@cygwin.com>
Subject: Re: MC no longer working with cygwin 3.1.x
Date: Sat, 21 Dec 2019 21:18:00 -0000 [thread overview]
Message-ID: <11931d17-efe4-5b1b-b95a-9651c0844e08@cornell.edu> (raw)
In-Reply-To: <20191221192602.GE3628@calimero.vinschen.de>
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
prev parent reply other threads:[~2019-12-21 21:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <DB8PR01MB5996973955794728D12078E6BC530@DB8PR01MB5996.eurprd01.prod.exchangelabs.com>
[not found] ` <97c8a719-73b9-e0ec-9651-97c2c684a086@gmail.com>
[not found] ` <20191218193205.GP10310@calimero.vinschen.de>
[not found] ` <c3809f52-1842-83d6-6692-53f6caec3491@cornell.edu>
[not found] ` <e79cd247-c573-3c27-6636-c6d9a32447a4@towo.net>
[not found] ` <1f5d0151-51c4-bd89-4fa9-137b88a543c8@cornell.edu>
[not found] ` <20191219092409.GS10310@calimero.vinschen.de>
2019-12-21 15:48 ` Ken Brown
2019-12-21 19:26 ` Corinna Vinschen
2019-12-21 21:18 ` Ken Brown [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=11931d17-efe4-5b1b-b95a-9651c0844e08@cornell.edu \
--to=kbrown@cornell.edu \
--cc=cygwin-developers@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).