From mboxrd@z Thu Jan 1 00:00:00 1970 X-GM-THRID: 6690944878080163840 X-Received: by 2002:adf:f9c5:: with SMTP id w5mr19739933wrr.26.1558457763179; Tue, 21 May 2019 09:56:03 -0700 (PDT) X-BeenThere: isar-users@googlegroups.com Received: by 2002:a05:600c:2304:: with SMTP id 4ls1170763wmo.4.canary-gmail; Tue, 21 May 2019 09:56:02 -0700 (PDT) X-Google-Smtp-Source: APXvYqxrYlnayzk9yfK6mzBO3n1PvQKnG2Y21t1iNgnRMxH/ZuAmNbs4yY20rfa9sC1dWjvPxhbK X-Received: by 2002:a7b:c3c3:: with SMTP id t3mr4340734wmj.88.1558457762688; Tue, 21 May 2019 09:56:02 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1558457762; cv=none; d=google.com; s=arc-20160816; b=rUZeimLUeU3/tx486I5b8CElcAytizabnkxGbpRIv/EMMP4njrBkVjN0ihPhn7IwQ0 a8mFTraK05Xy/bAVi0RJefu6VD/7l6Rn1LgKLtftQ52cHKsfGTjHogZ61Q0mLjGkLX7L 6u65Rmyy1DDm/RUAxMF0LbpPCMFjWPpXUwzrGYUNWtp0aIYxWRYYO51MLs2TN9DaHsAb EFAXECS4zr5td9VAaaoXtqi1cGf/9AqFQo+wYB5+hASiyYcs+vvtWr6uOURCqkMlBoxg vSwYpObERt0Rfp+2Hu10e0jX0Us+t6hBKiP4rSC6lpHEYHpCnh+s68y8sqJNn+cnRqJo 6PuQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=content-transfer-encoding:content-language:in-reply-to:mime-version :user-agent:date:message-id:from:references:cc:to:subject; bh=vfg/KMnSlzEJ4V3kdii7eCQm9fqJk20rUydukn+6IBA=; b=qsOkfSrIaQ5RWu0qFE3CJ3MnxIbn+0SvdoK2t7q97ithmDR/TjfkgwyWf6kwdqjgrK R/GIuJujbYhEC1sgTdwBO1hDcd2pCFUPdCGkZKynYqsMDvRlMhMb5YgPO2Cn40YnHssk xyPbIf+ySZDrUJDZRLgplOiGXz9DIb3hvfQz7dlaHJeqQPe6yATZXjYwvR/8GmieZWgX 5MFDUSYRgUWItk+x0bGyCI0D/i0zE0T27MVSNyIZ9v2MFVRE3VDSJ3qK/1L2wtlkMBFs EalkEtlhFoAYhlRLINWCqwb50x1EOnSeMAU/AZO4hN4L0qloWraLwj+RgsddWoPkpPSr S7Xw== ARC-Authentication-Results: i=1; gmr-mx.google.com; spf=pass (google.com: domain of jan.kiszka@siemens.com designates 192.35.17.14 as permitted sender) smtp.mailfrom=jan.kiszka@siemens.com; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=siemens.com Return-Path: Received: from david.siemens.de (david.siemens.de. [192.35.17.14]) by gmr-mx.google.com with ESMTPS id h5si2199073wrc.1.2019.05.21.09.56.02 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 21 May 2019 09:56:02 -0700 (PDT) Received-SPF: pass (google.com: domain of jan.kiszka@siemens.com designates 192.35.17.14 as permitted sender) client-ip=192.35.17.14; Authentication-Results: gmr-mx.google.com; spf=pass (google.com: domain of jan.kiszka@siemens.com designates 192.35.17.14 as permitted sender) smtp.mailfrom=jan.kiszka@siemens.com; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=siemens.com Received: from mail1.sbs.de (mail1.sbs.de [192.129.41.35]) by david.siemens.de (8.15.2/8.15.2) with ESMTPS id x4LGu1N9013903 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK); Tue, 21 May 2019 18:56:01 +0200 Received: from [139.25.68.37] (md1q0hnc.ad001.siemens.net [139.25.68.37] (may be forged)) by mail1.sbs.de (8.15.2/8.15.2) with ESMTP id x4LGu0kq008375; Tue, 21 May 2019 18:56:00 +0200 Subject: Re: [PATCH v6 1/9] isar-bootstrap-host: disable DISTRO_BOOTSTRAP_KEYS usage To: "[ext] claudius.heine.ext@siemens.com" , isar-users@googlegroups.com Cc: Claudius Heine , "Maxim Yu . Osipov" References: <20190515101149.22187-1-claudius.heine.ext@siemens.com> <20190515101149.22187-2-claudius.heine.ext@siemens.com> From: Jan Kiszka Message-ID: <3745f4ba-e3c9-4d59-22e4-9746c6497f6b@siemens.com> Date: Tue, 21 May 2019 18:56:02 +0200 User-Agent: Mozilla/5.0 (X11; U; Linux i686 (x86_64); de; rv:1.8.1.12) Gecko/20080226 SUSE/2.0.0.12-1.1 Thunderbird/2.0.0.12 Mnenhy/0.7.5.666 MIME-Version: 1.0 In-Reply-To: <20190515101149.22187-2-claudius.heine.ext@siemens.com> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit X-TUID: v1FqMTH96Gkr On 15.05.19 12:11, [ext] claudius.heine.ext@siemens.com wrote: > From: Claudius Heine > > isar-bootstrap-host only supports bootstrapping Debian root file > systems. Therefore deactivate any DISTRO_BOOTSTRAP_KEYS from other > distributions. Actually not totally true, as I just realized: What about bootstrapping the buildchroot from a custom debian repo that was differently signed (e.g. because it is a condensed version of upstream)? Seems we do need HOST_DISTRO_BOOTSTRAP_KEYS, right? Jan > > Signed-off-by: Claudius Heine > [Maxim: rebased] > Signed-off-by: Maxim Yu. Osipov > --- > meta/recipes-core/isar-bootstrap/isar-bootstrap-host.bb | 2 ++ > 1 file changed, 2 insertions(+) > > diff --git a/meta/recipes-core/isar-bootstrap/isar-bootstrap-host.bb b/meta/recipes-core/isar-bootstrap/isar-bootstrap-host.bb > index 7ee4c61..5501e35 100644 > --- a/meta/recipes-core/isar-bootstrap/isar-bootstrap-host.bb > +++ b/meta/recipes-core/isar-bootstrap/isar-bootstrap-host.bb > @@ -12,6 +12,8 @@ DEPLOY_ISAR_BOOTSTRAP = "${DEPLOY_DIR_BOOTSTRAP}/${HOST_DISTRO}-${HOST_ARCH}" > ISAR_BOOTSTRAP_LOCK = "${DEPLOY_DIR_BOOTSTRAP}/${HOST_DISTRO}-${HOST_ARCH}.lock" > > require isar-bootstrap.inc > +# We only build debian host buildchroot environments > +DISTRO_BOOTSTRAP_KEYS = "" > inherit isar-bootstrap-helper > > do_generate_keyrings[stamp-extra-info] = "${DISTRO}-${DISTRO_ARCH}" > -- Siemens AG, Corporate Technology, CT RDA IOT SES-DE Corporate Competence Center Embedded Linux