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.129.124]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 443F72594 for ; Thu, 26 Jan 2023 14:58:44 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1674745124; 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: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=l4P3EekWE0wh4v7Y6JRDBM+Ls4fIcP2CQOrYJI/TUYM=; b=DbFSrA4YgucYOC7Jc5zzsl1hBtLqrrXRwmbCRAbEgGnM+O3L0vZWeJ8wZr8pfFZN2WNzWf 0h33fFKUujXw+2v62YZ5kfnEc/lNXGaoKoJ7Fia4TuYcI7cSkRwpUzWlQqrW98nYKW+tuW 3L8ljezPnSp+tzrwPcup1HKIqKAT1fY= Received: from mail-wm1-f72.google.com (mail-wm1-f72.google.com [209.85.128.72]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.3, cipher=TLS_AES_128_GCM_SHA256) id us-mta-59-s8FhLPJkOLCR39L30gOsyA-1; Thu, 26 Jan 2023 09:58:43 -0500 X-MC-Unique: s8FhLPJkOLCR39L30gOsyA-1 Received: by mail-wm1-f72.google.com with SMTP id z22-20020a05600c0a1600b003db00dc4b69so2938105wmp.5 for ; Thu, 26 Jan 2023 06:58:42 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=user-agent:in-reply-to:content-transfer-encoding :content-disposition:mime-version:references:message-id:subject:cc :to:from:date:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=l4P3EekWE0wh4v7Y6JRDBM+Ls4fIcP2CQOrYJI/TUYM=; b=VTUIFXxiWDu4odxZ3L7Abraub7s3GDo43u+lGJVZAZ6lc0ks+kriB2uUH/GAH1i1JH /LeoSvRUuzRRw412olDmNLcZahCq5upQAOz4eWJpPSdjEIlz4nH8Vr/41pplDMlQp7xn ZRcvIls4fGNNYpHI7z3TRxlVshVYCaMKpus3ujcxRjuRkvgIYBwBcnZjsP+lOtCXGN9I 6wBoPr9j1k6fnFPMqHePEj6edPmSx1K0rSoT8cOu/yxED/B3vxN1/+mIa/nIXzJygC5s mevbKvk884+jXaO0SZveb/G82m8xozOLNzZUUYtTUb2lVj2gpM9V8v97RdPYIBQZHibb JpaA== X-Gm-Message-State: AFqh2krl1vywi0gmVyc4erFDBfEGZAEwNx3pci4bPK3Ovl4rnQuR4JuV SOR40OpbwAfmvsHDnme/uf35Cb4QgXaCN7IFjlIux6nfQvXgiEIHXgRjP8Dg5Yy5YmLQ8dC8sIa iT4qtL1e1cMgYP+wxHOBRFA== X-Received: by 2002:a05:600c:1604:b0:3c6:e61e:ae74 with SMTP id m4-20020a05600c160400b003c6e61eae74mr37552764wmn.4.1674745121775; Thu, 26 Jan 2023 06:58:41 -0800 (PST) X-Google-Smtp-Source: AMrXdXvUHkTSF1aTLNZRATAUakPRX7lKJA20hKwBlcnoeqfg7B5Un3oBMDMpd5xsKa7o2OIjjRAhdA== X-Received: by 2002:a05:600c:1604:b0:3c6:e61e:ae74 with SMTP id m4-20020a05600c160400b003c6e61eae74mr37552740wmn.4.1674745121600; Thu, 26 Jan 2023 06:58:41 -0800 (PST) Received: from work-vm (ward-16-b2-v4wan-166627-cust863.vm18.cable.virginm.net. [81.97.203.96]) by smtp.gmail.com with ESMTPSA id l4-20020a05600c1d0400b003db2e3f2c7csm12219398wms.0.2023.01.26.06.58.40 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Thu, 26 Jan 2023 06:58:41 -0800 (PST) Date: Thu, 26 Jan 2023 14:58:38 +0000 From: "Dr. David Alan Gilbert" To: Richard Weinberger Cc: Daniel =?iso-8859-1?Q?P=2E_Berrang=E9?= , Greg Kroah-Hartman , "Reshetova, Elena" , "Shishkin, Alexander" , "Shutemov, Kirill" , "Kuppuswamy, Sathyanarayanan" , "Kleen, Andi" , "Hansen, Dave" , Thomas Gleixner , Peter Zijlstra , "Wunner, Lukas" , Mika Westerberg , "Michael S. Tsirkin" , Jason Wang , "Poimboe, Josh" , "aarcange@redhat.com" , Cfir Cohen , Marc Orr , "jbachmann@google.com" , "pgonda@google.com" , "keescook@chromium.org" , James Morris , Michael Kelley , "Lange, Jon" , "linux-coco@lists.linux.dev" , Linux Kernel Mailing List Subject: Re: Linux guest kernel threat model for Confidential Computing Message-ID: References: Precedence: bulk X-Mailing-List: linux-coco@lists.linux.dev List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 In-Reply-To: User-Agent: Mutt/2.2.9 (2022-11-12) X-Mimecast-Spam-Score: 0 X-Mimecast-Originator: redhat.com Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit * Richard Weinberger (richard.weinberger@gmail.com) wrote: > On Wed, Jan 25, 2023 at 3:22 PM Daniel P. Berrangé wrote: > > Any virtual device exposed to the guest that can transfer potentially > > sensitive data needs to have some form of guest controlled encryption > > applied. For disks this is easy with FDE like LUKS, for NICs this is > > already best practice for services by using TLS. Other devices may not > > have good existing options for applying encryption. > > I disagree wrt. LUKS. The cryptography behind LUKS protects persistent data > but not transport. If an attacker can observe all IO you better > consult a cryptographer. > LUKS has no concept of session keys or such, so the same disk sector will > always get encrypted with the very same key/iv. Are you aware of anything that you'd use instead? Are you happy with dm-verity for protection against modification? Dave > -- > Thanks, > //richard > -- Dr. David Alan Gilbert / dgilbert@redhat.com / Manchester, UK