This patch fixes a bug in radosgw swift compatibility code,
that is, if a not-owner but authorized user access a non-existing
object in a container, he wiil receive unexpected error code,
to repeat this bug, do the following steps,
1 User1 creates a container, and grants the read/write permission to user2
curl -X PUT -i -k -H "X-Auth-Token: $user1_token" $url/$container
curl -X POST -i -k -H "X-Auth-Token: $user1_token" -H "X-Container-Read:
$user2" -H "X-Container-Write: $user2" $url/$container
2 User2 queries the object 'obj' in the newly created container
by using HEAD instruction, note the container currently is empty
curl -X HEAD -i -k -H "X-Auth-Token: $user2_token" $url/$container/obj
3 The response received by user2 is '401 Authorization Required',
rather than the expected '404 Not Found', the details are as follows,
HTTP/1.1 401 Authorization Required
Date: Tue, 16 Apr 2013 01:52:49 GMT
Server: Apache/2.2.22 (Ubuntu)
Accept-Ranges: bytes
Content-Length: 12
Vary: Accept-Encoding
Signed-off-by: Yunchuan Wen <yunchuanwen@ubuntukylin.com>
Signed-off-by: Li Wang <liwang@ubuntukylin.com>
Reviewed-by: Yehuda Sadeh <yehuda@inktank.com>
bool RGWAccessControlPolicy::verify_permission(string& uid, int user_perm_mask, int perm)
{
- int test_perm = perm;
+ int test_perm = perm | RGW_PERM_READ_OBJS | RGW_PERM_WRITE_OBJS;
int policy_perm = get_perm(uid, test_perm);
policy_perm |= (RGW_PERM_READ | RGW_PERM_READ_ACP);
}
- int acl_perm = policy_perm & user_perm_mask;
+ int acl_perm = policy_perm & perm & user_perm_mask;
ldout(cct, 10) << " uid=" << uid << " requested perm (type)=" << perm << ", policy perm=" << policy_perm << ", user_perm_mask=" << user_perm_mask << ", acl perm=" << acl_perm << dendl;
if ((perm & (int)s->perm_mask) != perm)
return false;
- if (s->bucket_acl->verify_permission(s->user.user_id, perm, perm))
- return true;
-
- if (perm & (RGW_PERM_READ | RGW_PERM_READ_ACP))
- perm |= RGW_PERM_READ_OBJS;
- if (perm & RGW_PERM_WRITE)
- perm |= RGW_PERM_WRITE_OBJS;
-
return s->bucket_acl->verify_permission(s->user.user_id, perm, perm);
}