From mboxrd@z Thu Jan 1 00:00:00 1970 From: Mimi Zohar Subject: Re: [PATCH v2 0/3] initramfs: add support for xattrs in the initial ram disk Date: Fri, 10 May 2019 07:49:31 -0400 Message-ID: <1557488971.10635.102.camel@linux.ibm.com> References: <20190509112420.15671-1-roberto.sassu@huawei.com> Mime-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 8bit Return-path: In-Reply-To: Sender: linux-kernel-owner@vger.kernel.org To: Roberto Sassu , Rob Landley , viro@zeniv.linux.org.uk Cc: linux-security-module@vger.kernel.org, linux-integrity@vger.kernel.org, initramfs@vger.kernel.org, linux-api@vger.kernel.org, linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org, zohar@linux.vnet.ibm.com, silviu.vlasceanu@huawei.com, dmitry.kasatkin@huawei.com, takondra@cisco.com, kamensky@cisco.com, hpa@zytor.com, arnd@arndb.de, james.w.mcmechan@gmail.com List-Id: linux-api@vger.kernel.org On Fri, 2019-05-10 at 08:56 +0200, Roberto Sassu wrote: > On 5/9/2019 8:34 PM, Rob Landley wrote: > > On 5/9/19 6:24 AM, Roberto Sassu wrote: > >> The difference with another proposal > >> (https://lore.kernel.org/patchwork/cover/888071/) is that xattrs can be > >> included in an image without changing the image format, as opposed to > >> defining a new one. As seen from the discussion, if a new format has to be > >> defined, it should fix the issues of the existing format, which requires > >> more time. > > > > So you've explicitly chosen _not_ to address Y2038 while you're there. > > Can you be more specific? Right, this patch set avoids incrementing the CPIO magic number and the resulting changes required (eg. increasing the timestamp field size), by including a file with the security xattrs in the CPIO.  In either case, including the security xattrs in the initramfs header or as a separate file, the initramfs, itself, needs to be signed. Mimi