All Manuals > LispWorks User Guide and Reference Manual > 41 Miscellaneous WIN32 symbols




Interprets an access specification and generates a Security Descriptor String.




security-description-string-for-open-named-pipe access-spec => result , fail-type , fail-item



A keyword, an integer, a string or a list.



A string or nil .


Undefined, or a string.


Undefined, or a keyword, an integer, a string or a list.


The function security-description-string-for-open-named-pipe interprets access-spec and generates from it a Security Descriptor String as defined by Windows. See the MSDN for documentation of "Security Descriptor String Format".

security-description-string-for-open-named-pipe has quite limited capabilities, and the string that it generates contains only the DACL part of the descriptor.

If access-spec is a keyword, then its symbol name specifies a SID (Security Identifier). This SID gets read/write permission. The SID can be either standard representation (which looks like "S-1-.." ) or one of the aliases. The aliases are documented in the MSDN in the page titled "SID strings" (search for SDDL_ANONYMOUS ). In general they have two letters, for example :AU means authenticated users. The common standard strings are documented in the MSDN page titled "Well-known SIDs" (search for SECURITY_WORLD_RID ). For example, :S-1-15-11 means authentication users. Any standard strings is acceptable, not only the documented ones, provided that it specifies a valid SID. For example, you can find the SID of a user by user-name-to-sid-string, intern it in the keyword package and use this (but it is better to pass a list (:user) as described below).

If access-spec is an integer, it must be one of the integers in the WELL_KNOWN_SID_TYPE Enumeration as documented in the MSDN. For example, 17 means authenticated users. The corresponding SID gets read/write permission.

If access-spec is a string, it is returned as-is. In this case it is the responsibility of the programmer to ensure that the string is valid. Note that if this string is used in open-named-pipe-stream, open-named-pipe-stream does not inherit the access even if inherit-access-p is non-nil.

If access-spec is a list, then each element in the list must be one of:

A string

The string must a correct ACE (Access Control Entry) string, as described in the MSDN (search for "ACE strings"). The string must contain the opening and closing brackets, and can contain more than one ACE. security-description-string-for-open-named-pipe does not check the syntax in the string, and if the ACE is wrong the result string would be invalid.

A keyword

This is interpreted as when access-spec is a keyword, and the corresponding SID gets read/write permission.

An integer

This is interpreted as when access-spec is an integer, and the corresponding SID gets read/write permission.

A list of the form ( keyword SID-spec &rest permissions )

The first element keyword specifies how to interpret the SID-spec . The possible keywords are :user , when SID-spec must be a string and should name a user on the local machine, and :sid , when SID-spec must be a keyword, an integer or a string specifying the SID. Integers and keywords are interpreted as above, and strings are interpreted in the same way as keywords.If permissions are not supplied, they default to (:read :write) . When they are supplied, they are keywords specifying permission. Currently supported keywords are (i) one of :read or :disallow-read (ii) one of :write or :disallow-write , specifying the obvious meaning. It is an error if a keyword is repeated or if an incompatible pair is passed.

security-description-string-for-open-named-pipe returns 3 values. When successful, result is the string and the other return values are undefined. When it fails, which can be because it is given an unrecognized SID specifier, result is nil , fail-type is a short string giving the type of the item that fails, and fail-item is the item in the list that fails when access-spec is a list.

  1. When the argument is syntactically incorrect, security-description-string-for-open-named-pipe signals an error. It fails and returns nil only when a SID specifier of an acceptable type does not specify a SID.
  2. Except when given a string which is returned as-is, security-description-string-for-open-named-pipe works by generating an ACE (Access Control Entry) string for each SID giving it the read and write permission, except in the case when either :disallow-write or :disallow-read is used, when it generates an ACE string denying permission. All the ACEs are then concatenated and "D:" is prepended, thus generating a Security Descriptor String containing only the DACL.
  3. Experimentally, you can connect to a named pipe only if you have both read and write permission, even when opening it for only read or only write. Thus when this function is used from open-named-pipe-stream, the keywords :disallow-read etc are not very useful. They are useful only when you want to deny access for a specific SID, by using :disallow-read and :disallow-write .
  4. The order of the items in the list is significant: earlier items override later items.
  5. Disallowing permission, for example by using :disallow-read , is not the same as not allowing it, because in the latter case a later ACE can give the SID the permission. Disallowing prevents later ACEs from giving permission.
  6. Using a string or ACE strings in the list allows the user to generate a more elaborate string than security-description-string-for-open-named-pipe knows how to generate. In this case the returned string may be invalid. When this happens from open-named-pipe-stream, open-named-pipe-stream will get a failure and signal or return an error according to errorp .

Any of these gives permissions to all authenticated users:

    '((:SID :AU))
    '((:SID "AU")
    '((:SID 17))

Also, all of the above with AU replaced by S-1-15-11 will give permission to all authenticated users.

This gives permissions to all authorized users except the user "exclude" :

'((:use "exclude" :DISALLOW-READ :DISALLOW-WRITE) :AU)
See also


LispWorks User Guide and Reference Manual - 21 Dec 2011