From nobody Sun May 5 05:32:47 2024 Delivered-To: importer@patchew.org Received-SPF: pass (zoho.com: domain of gnu.org designates 208.118.235.17 as permitted sender) client-ip=208.118.235.17; envelope-from=qemu-devel-bounces+importer=patchew.org@nongnu.org; helo=lists.gnu.org; Authentication-Results: mx.zohomail.com; spf=pass (zoho.com: domain of gnu.org designates 208.118.235.17 as permitted sender) smtp.mailfrom=qemu-devel-bounces+importer=patchew.org@nongnu.org; dmarc=fail(p=none dis=none) header.from=redhat.com Return-Path: Received: from lists.gnu.org (lists.gnu.org [208.118.235.17]) by mx.zohomail.com with SMTPS id 1528366346389397.000761397794; Thu, 7 Jun 2018 03:12:26 -0700 (PDT) Received: from localhost ([::1]:56656 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1fQru5-00048N-Jz for importer@patchew.org; Thu, 07 Jun 2018 06:12:25 -0400 Received: from eggs.gnu.org ([2001:4830:134:3::10]:36595) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1fQrsA-00036w-SM for qemu-devel@nongnu.org; Thu, 07 Jun 2018 06:10:30 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1fQrs7-0007eu-L9 for qemu-devel@nongnu.org; Thu, 07 Jun 2018 06:10:26 -0400 Received: from mx3-rdu2.redhat.com ([66.187.233.73]:34676 helo=mx1.redhat.com) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1fQrs7-0007eT-Eh for qemu-devel@nongnu.org; Thu, 07 Jun 2018 06:10:23 -0400 Received: from smtp.corp.redhat.com (int-mx03.intmail.prod.int.rdu2.redhat.com [10.11.54.3]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.redhat.com (Postfix) with ESMTPS id 35C14401EF21 for ; Thu, 7 Jun 2018 10:10:22 +0000 (UTC) Received: from t460.redhat.com (unknown [10.33.36.52]) by smtp.corp.redhat.com (Postfix) with ESMTP id 9D02710F1BF9; Thu, 7 Jun 2018 10:10:21 +0000 (UTC) From: =?UTF-8?q?Daniel=20P=2E=20Berrang=C3=A9?= To: qemu-devel@nongnu.org Date: Thu, 7 Jun 2018 11:10:19 +0100 Message-Id: <20180607101019.14958-1-berrange@redhat.com> MIME-Version: 1.0 X-Scanned-By: MIMEDefang 2.78 on 10.11.54.3 X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.5.16 (mx1.redhat.com [10.11.55.5]); Thu, 07 Jun 2018 10:10:22 +0000 (UTC) X-Greylist: inspected by milter-greylist-4.5.16 (mx1.redhat.com [10.11.55.5]); Thu, 07 Jun 2018 10:10:22 +0000 (UTC) for IP:'10.11.54.3' DOMAIN:'int-mx03.intmail.prod.int.rdu2.redhat.com' HELO:'smtp.corp.redhat.com' FROM:'berrange@redhat.com' RCPT:'' Content-Transfer-Encoding: quoted-printable X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] [fuzzy] X-Received-From: 66.187.233.73 Subject: [Qemu-devel] [PATCH] doc: switch to modern syntx for VNC TLS setup X-BeenThere: qemu-devel@nongnu.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: qemu-devel-bounces+importer=patchew.org@nongnu.org Sender: "Qemu-devel" X-ZohoMail: RSF_0 Z_629925259 SPT_0 Content-Type: text/plain; charset="utf-8" The use of 'tls', 'x509' and 'x509verify' properties is the legacy backcompat syntx, replaced by use of TLS creds objects. Signed-off-by: Daniel P. Berrang=C3=A9 --- qemu-doc.texi | 20 +++++++++++++++----- 1 file changed, 15 insertions(+), 5 deletions(-) diff --git a/qemu-doc.texi b/qemu-doc.texi index f00706b999..d526870479 100644 --- a/qemu-doc.texi +++ b/qemu-doc.texi @@ -1097,7 +1097,9 @@ support provides a secure session, but no authenticat= ion. This allows any client to connect, and provides an encrypted session. =20 @example -qemu-system-i386 [...OPTIONS...] -vnc :1,tls,x509=3D/etc/pki/qemu -monitor= stdio +qemu-system-i386 [...OPTIONS...] \ + -object tls-creds-x509,id=3Dtls0,dir=3D/etc/pki/qemu,endpoint=3Dserver,v= erify-peer=3Dno \ + -vnc :1,tls-creds=3Dtls0 -monitor stdio @end example =20 In the above example @code{/etc/pki/qemu} should contain at least three fi= les, @@ -1112,10 +1114,14 @@ only be readable by the user owning it. Certificates can also provide a means to authenticate the client connectin= g. The server will request that the client provide a certificate, which it wi= ll then validate against the CA certificate. This is a good choice if deployi= ng -in an environment with a private internal certificate authority. +in an environment with a private internal certificate authority. It uses t= he +same syntax as previously, but with @code{verify-peer} set to @code{yes} +instead. =20 @example -qemu-system-i386 [...OPTIONS...] -vnc :1,tls,x509verify=3D/etc/pki/qemu -m= onitor stdio +qemu-system-i386 [...OPTIONS...] \ + -object tls-creds-x509,id=3Dtls0,dir=3D/etc/pki/qemu,endpoint=3Dserver,v= erify-peer=3Dyes \ + -vnc :1,tls-creds=3Dtls0 -monitor stdio @end example =20 =20 @@ -1126,7 +1132,9 @@ Finally, the previous method can be combined with VNC= password authentication to provide two layers of authentication for clients. =20 @example -qemu-system-i386 [...OPTIONS...] -vnc :1,password,tls,x509verify=3D/etc/pk= i/qemu -monitor stdio +qemu-system-i386 [...OPTIONS...] \ + -object tls-creds-x509,id=3Dtls0,dir=3D/etc/pki/qemu,endpoint=3Dserver,v= erify-peer=3Dyes \ + -vnc :1,tls-creds=3Dtls0,password -monitor stdio (qemu) change vnc password Password: ******** (qemu) @@ -1163,7 +1171,9 @@ credentials. This can be enabled, by combining the 's= asl' option with the aforementioned TLS + x509 options: =20 @example -qemu-system-i386 [...OPTIONS...] -vnc :1,tls,x509,sasl -monitor stdio +qemu-system-i386 [...OPTIONS...] \ + -object tls-creds-x509,id=3Dtls0,dir=3D/etc/pki/qemu,endpoint=3Dserver,v= erify-peer=3Dyes \ + -vnc :1,tls-creds=3Dtls0,sasl -monitor stdio @end example =20 @node vnc_setup_sasl --=20 2.17.0