The information in this article applies to:
SUMMARYEarly betas of Windows NT did not require security attributes on objects such as pipes. For example, it was valid at that time to enter NULL for the last parameter of the Win32-based application programming interface (API) CreateNamedPipe(). This is no longer the case. MORE INFORMATION
Windows NT 3.1 and later require security attributes. Please note that
setting the security attributes parameter to NULL does not indicate
that you want a NULL security descriptor (SD), rather it indicates that you
want to inherit the security descriptor of the current access token. For
example, this means that any client wanting to connect to your pipe server
must have the same security attributes as the user that started the server.
If the user who started the server was the administrator of the machine,
then any client who wants to connect must also be an administrator for that
machine.
It is important to note that by specifying TRUE for the fDaclPresent
parameter and NULL for pAcl parameter of the SetSecurityDescriptorDacl()
API, a NULL access control list (ACL) is being explicitly specified.
Additional query words: 3.10 3.50
|
|
Last Reviewed: October 20, 1999 © 1999 Microsoft Corporation. All rights reserved. Terms of Use. |