From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [170.10.133.124]) by mx.groups.io with SMTP id smtpd.web11.5424.1643364877682271977 for ; Fri, 28 Jan 2022 02:14:38 -0800 Authentication-Results: mx.groups.io; dkim=pass header.i=@redhat.com header.s=mimecast20190719 header.b=jGIkkbWI; spf=pass (domain: redhat.com, ip: 170.10.133.124, mailfrom: kraxel@redhat.com) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1643364876; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=6OrGRlFRpCqbTSq/Unsut47UnJDIV8wlJKY5YT8+G3c=; b=jGIkkbWICIOO5JCy8GjJfnKoVEK6YiGn5ME8/XESSZiXViiAXllYlv+Kh+6ia3xYNx6iit eLtaNrjP4nujRofUW09JTs5zBMrcjYbXulIp95nL22vcwEAJn+RhAFBXmmhtWj6eku9FwJ 0bU642zmOyoXVHlK52hCYolyaOHfn5g= Received: from mimecast-mx01.redhat.com (mimecast-mx01.redhat.com [209.132.183.4]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id us-mta-532-S0p1wXWjO4KPdL_6lFSNzQ-1; Fri, 28 Jan 2022 05:14:33 -0500 X-MC-Unique: S0p1wXWjO4KPdL_6lFSNzQ-1 Received: from smtp.corp.redhat.com (int-mx02.intmail.prod.int.phx2.redhat.com [10.5.11.12]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx01.redhat.com (Postfix) with ESMTPS id 7E5661083F61; Fri, 28 Jan 2022 10:14:31 +0000 (UTC) Received: from sirius.home.kraxel.org (unknown [10.39.193.47]) by smtp.corp.redhat.com (Postfix) with ESMTPS id 1F2E778DA2; Fri, 28 Jan 2022 10:14:31 +0000 (UTC) Received: by sirius.home.kraxel.org (Postfix, from userid 1000) id 6B6321800608; Fri, 28 Jan 2022 11:14:29 +0100 (CET) Date: Fri, 28 Jan 2022 11:14:29 +0100 From: "Gerd Hoffmann" To: Pedro Falcato Cc: edk2-devel-groups-io , Andrew Fish , "KILIAN_KEGEL@outlook.com" , Mike Kinney , "Yao, Jiewen" , Sean Brogan , Bret Barkelew , "Wang, Jian J" , "Jiang, Guomin" , Pawel Polawski , "Lu, XiaoyuX" Subject: Re: [edk2-devel] [PATCH 00/24] CryptoPkg/openssl: update openssl submodule to v3.0 Message-ID: <20220128101429.s7sop6wz2ictnmuw@sirius.home.kraxel.org> References: <20220121083035.dsqzu3akshonliza@sirius.home.kraxel.org> <20220126110244.klk24znojvdtirzw@sirius.home.kraxel.org> <71737233-2840-42CE-A65E-1895E936B4CB@apple.com> MIME-Version: 1.0 In-Reply-To: X-Scanned-By: MIMEDefang 2.79 on 10.5.11.12 Authentication-Results: relay.mimecast.com; auth=pass smtp.auth=CUSA124A263 smtp.mailfrom=kraxel@redhat.com X-Mimecast-Spam-Score: 0 X-Mimecast-Originator: redhat.com Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Hi, > I think that maybe "Why are we bringing in so much third-party code to > firmware?" is a way better question than "is it feasible to implement all > the required builtins?". Why can my firmware speak TLS, and why does it > have a whole copy of *OpenSSL*, which is a huge library with a big attack > surface and was never written to be run in a firmware/kernel/bare metal > environment like UEFI. crypto is needed for: (1) network boot (tls for https) (2) iscsi (tls too). (3) secure boot. (4) tpm support. (5) secure firmware updates. And possibly more. > Note: If there's a big need for something like internal TLS I would > recommend BearSSL as a very small TLS implementation that was actually > written for embedded systems. Well, that doesn't look like an actively maintained project. One commit in 2021. Four commits in 2020. Features like TLS-1.3 support on the TODO-List but apparently nobody working on it. take care, Gerd