Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756620AbdGLLgB (ORCPT ); Wed, 12 Jul 2017 07:36:01 -0400 Received: from mx0b-001b2d01.pphosted.com ([148.163.158.5]:39777 "EHLO mx0a-001b2d01.pphosted.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1756332AbdGLLf6 (ORCPT ); Wed, 12 Jul 2017 07:35:58 -0400 Subject: Re: [PATCH v2] xattr: Enable security.capability in user namespaces To: "Serge E. Hallyn" References: <1499785511-17192-1-git-send-email-stefanb@linux.vnet.ibm.com> <1499785511-17192-2-git-send-email-stefanb@linux.vnet.ibm.com> <20170712034503.GA8270@mail.hallyn.com> Cc: ebiederm@xmission.com, containers@lists.linux-foundation.org, lkp@01.org, linux-kernel@vger.kernel.org, zohar@linux.vnet.ibm.com, tycho@docker.com, James.Bottomley@HansenPartnership.com, vgoyal@redhat.com, christian.brauner@mailbox.org, amir73il@gmail.com, linux-security-module@vger.kernel.org, casey@schaufler-ca.com From: Stefan Berger Date: Wed, 12 Jul 2017 07:35:49 -0400 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.4.0 MIME-Version: 1.0 In-Reply-To: <20170712034503.GA8270@mail.hallyn.com> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-TM-AS-GCONF: 00 x-cbid: 17071211-8235-0000-0000-00000BE96E92 X-IBM-SpamModules-Scores: X-IBM-SpamModules-Versions: BY=3.00007354; HX=3.00000241; KW=3.00000007; PH=3.00000004; SC=3.00000214; SDB=6.00886471; UDB=6.00442501; IPR=6.00666621; BA=6.00005468; NDR=6.00000001; ZLA=6.00000005; ZF=6.00000009; ZB=6.00000000; ZP=6.00000000; ZH=6.00000000; ZU=6.00000002; MB=3.00016195; XFM=3.00000015; UTC=2017-07-12 11:35:54 X-IBM-AV-DETECTION: SAVI=unused REMOTE=unused XFE=unused x-cbparentid: 17071211-8236-0000-0000-00003CB6496A Message-Id: <8c3e8c6f-52c5-5b04-8cad-1aeae25f0ec6@linux.vnet.ibm.com> X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:,, definitions=2017-07-12_03:,, signatures=0 X-Proofpoint-Spam-Details: rule=outbound_notspam policy=outbound score=0 spamscore=0 suspectscore=2 malwarescore=0 phishscore=0 adultscore=0 bulkscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1706020000 definitions=main-1707120189 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 3470 Lines: 108 On 07/11/2017 11:45 PM, Serge E. Hallyn wrote: > Quoting Stefan Berger (Stefan Bergerstefanb@linux.vnet.ibm.com): >> +/* >> + * xattr_list_userns_rewrite - Rewrite list of xattr names for user namespaces >> + * or determine needed size for attribute list >> + * in case size == 0 >> + * >> + * In a user namespace we do not present all extended attributes to the >> + * user. We filter out those that are in the list of userns supported xattr. >> + * Besides that we filter out those with @uid= when there is no mapping >> + * for that uid in the current user namespace. >> + * >> + * @list: list of 0-byte separated xattr names >> + * @size: the size of the list; may be 0 to determine needed list size >> + * @list_maxlen: allocated buffer size of list >> + */ >> +static ssize_t >> +xattr_list_userns_rewrite(char *list, ssize_t size, size_t list_maxlen) >> +{ >> + char *nlist = NULL; >> + size_t s_off, len, nlen; >> + ssize_t d_off; >> + char *name, *newname; >> + >> + if (!list || size < 0 || current_user_ns() == &init_user_ns) >> + return size; >> + >> + if (size) { >> + nlist = kmalloc(list_maxlen, GFP_KERNEL); >> + if (!nlist) >> + return -ENOMEM; >> + } >> + >> + s_off = d_off = 0; >> + while (s_off < size || size == 0) { >> + name = &list[s_off]; >> + >> + len = strlen(name); >> + if (!len) >> + break; >> + >> + if (xattr_is_userns_supported(name, false) >= 0) >> + newname = name; >> + else { >> + newname = xattr_rewrite_userns_xattr(name); > Why are you doing this here? If we get here it means that > xattr_is_userns_supported() returned < 0, meaning name is > not userns-supported. So xattr_rewrite_userns_xattr() will > just return name. Am I missing something? xattr_is_userns_support(name, false) does a _full string match_ rather than a prefix match and will only return >= 0 for security.capability. This case handles the hosts's security.capability which 'shines through' for read and needs to be listed. Only in this case we set newname=name. In the else branch we handle security.capability@uid=1000 and rewrite that to security.capability for root mapping to uid=1000. > >> + if (IS_ERR(newname)) { >> + d_off = PTR_ERR(newname); >> + goto out_free; >> + } >> + } >> + if (newname && !xattr_list_contains(nlist, d_off, newname)) { > Now here, if name was recalculated to @newname, and @newname is > found in the nlist, that should raise an error right? Something > fishy is going on? If security.capability is set on a file but the container doesn't have security.capability@uid=1000, we still need to list the former here. However, we end up with duplicates if security.capability is there and security.capability@uid=1000 is also there and root is mapped to uid=1000. Both would be shown as security.capability inside the container. In this case we need to filter. I think the code is correct. More problematic is a memory leak in the error case. Will fix that. > >> + nlen = strlen(newname); >> + >> + if (nlist) { >> + if (nlen + 1 > list_maxlen) > d_off needs to be set to -ERANGE here. Fixed. > >> + break; >> + strcpy(&nlist[d_off], newname); >> + } >> + >> + d_off += nlen + 1; >> + if (newname != name) >> + kfree(newname); >> + } >> + s_off += len + 1; >> + } >> + if (nlist) >> + memcpy(list, nlist, d_off); >> +out_free: >> + kfree(nlist); >> + >> + return d_off; >> +}