Commit 221e01ab authored by Rob Shearman's avatar Rob Shearman Committed by Alexandre Julliard

server: A general solution for handling MAXIMUM_ALLOWED access right has been…

server: A general solution for handling MAXIMUM_ALLOWED access right has been implemented so remove the workarounds.
parent 81aeae32
......@@ -1713,7 +1713,6 @@ DECL_HANDLER(create_key)
struct unicode_str name, class;
unsigned int access = req->access;
if (access & MAXIMUM_ALLOWED) access = KEY_ALL_ACCESS; /* FIXME: needs general solution */
reply->hkey = 0;
if (req->namelen > get_req_data_size())
......@@ -1752,7 +1751,6 @@ DECL_HANDLER(open_key)
struct unicode_str name;
unsigned int access = req->access;
if (access & MAXIMUM_ALLOWED) access = KEY_ALL_ACCESS; /* FIXME: needs general solution */
reply->hkey = 0;
/* NOTE: no access rights are required to open the parent key, only the child key */
if ((parent = get_parent_hkey_obj( req->parent )))
......
......@@ -1208,7 +1208,6 @@ DECL_HANDLER(duplicate_token)
privilege_add( token, &privilege->luid, privilege->enabled );
access = req->access;
if (access & MAXIMUM_ALLOWED) access = TOKEN_ALL_ACCESS; /* FIXME: needs general solution */
reply->new_handle = alloc_handle( current->process, token, access, req->attributes);
release_object( token );
}
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment