From nobody Mon Feb 9 16:35:13 2026 Delivered-To: importer@patchew.org Received-SPF: pass (zohomail.com: domain of redhat.com designates 170.10.133.124 as permitted sender) client-ip=170.10.133.124; envelope-from=libvir-list-bounces@redhat.com; helo=us-smtp-delivery-124.mimecast.com; Authentication-Results: mx.zohomail.com; dkim=pass; spf=pass (zohomail.com: domain of redhat.com designates 170.10.133.124 as permitted sender) smtp.mailfrom=libvir-list-bounces@redhat.com; dmarc=pass(p=none dis=none) header.from=redhat.com ARC-Seal: i=1; a=rsa-sha256; t=1654009767; cv=none; d=zohomail.com; s=zohoarc; b=DhpCkt2pz/WLoWBDLWXLnV/VlSCl4Z5YLPlhGA8Vk1CeO08IZpQsbbE8XRknAkJmQd2F3DYbSceOYKHqCxQ91MM7doc3UvyrGpaLwXAZwFbPbGjgkYFGx2J47ccZeRVrV5XCDRcSxV+dkuTo19sdq6j81aHanaYfKTZGSG++hMA= ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=zohomail.com; s=zohoarc; t=1654009767; h=Content-Type:Content-Transfer-Encoding:Date:From:In-Reply-To:List-Subscribe:List-Post:List-Id:List-Archive:List-Help:List-Unsubscribe:MIME-Version:Message-ID:References:Sender:Subject:To; bh=jz9BDBh+3t7zt+94F/JM2VKZzQhmbFP79+lxuGT8jo4=; b=HiEzrk09caYnnP+j1r4CzxnhV65TiruZcS6i7dSK/6/5APFw1lcjHYTcFDcoLxWymnUb7JkCTf43Qa4XKsXAyfKEHvjG1wHv1CJVmSH1HeshOIwL2xzxSL5BBsYcPDaTu9+yPEzO96HrJYn1wLDyOhoEG5QIer/OgnvifxF6Dk8= ARC-Authentication-Results: i=1; mx.zohomail.com; dkim=pass; spf=pass (zohomail.com: domain of redhat.com designates 170.10.133.124 as permitted sender) smtp.mailfrom=libvir-list-bounces@redhat.com; dmarc=pass header.from= (p=none dis=none) Return-Path: Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [170.10.133.124]) by mx.zohomail.com with SMTPS id 1654009767963921.375558453712; Tue, 31 May 2022 08:09:27 -0700 (PDT) Received: from mimecast-mx02.redhat.com (mimecast-mx02.redhat.com [66.187.233.88]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id us-mta-358-0T5jHrplOE-vgjQ4BnK5Mg-1; Tue, 31 May 2022 11:09:06 -0400 Received: from smtp.corp.redhat.com (int-mx09.intmail.prod.int.rdu2.redhat.com [10.11.54.9]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx02.redhat.com (Postfix) with ESMTPS id EFA2F8630C0; Tue, 31 May 2022 15:07:42 +0000 (UTC) Received: from mm-prod-listman-01.mail-001.prod.us-east-1.aws.redhat.com (unknown [10.30.29.100]) by smtp.corp.redhat.com (Postfix) with ESMTP id CF802492CA4; Tue, 31 May 2022 15:07:42 +0000 (UTC) Received: from mm-prod-listman-01.mail-001.prod.us-east-1.aws.redhat.com (localhost [IPv6:::1]) by mm-prod-listman-01.mail-001.prod.us-east-1.aws.redhat.com (Postfix) with ESMTP id 8D07D1947065; Tue, 31 May 2022 15:07:42 +0000 (UTC) Received: from smtp.corp.redhat.com (int-mx05.intmail.prod.int.rdu2.redhat.com [10.11.54.5]) by mm-prod-listman-01.mail-001.prod.us-east-1.aws.redhat.com (Postfix) with ESMTP id 26FAD194707F for ; Tue, 31 May 2022 15:07:37 +0000 (UTC) Received: by smtp.corp.redhat.com (Postfix) id 0479E10725; Tue, 31 May 2022 15:07:37 +0000 (UTC) Received: from speedmetal.lan (unknown [10.40.208.21]) by smtp.corp.redhat.com (Postfix) with ESMTP id 755611131A for ; Tue, 31 May 2022 15:07:36 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1654009766; h=from:from:sender:sender:reply-to:subject:subject:date:date: message-id:message-id:to:to:cc:mime-version:mime-version: content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references:list-id:list-help: list-unsubscribe:list-subscribe:list-post; bh=jz9BDBh+3t7zt+94F/JM2VKZzQhmbFP79+lxuGT8jo4=; b=ZEyV1Y0+VHVCenQuf9Oyrd9/IV65xZydbPJvc8xrkmH2pSHqOXloDyPSi81LerTOzufWdH ouj9G+7xLta7KSOSodd039KvGg4lDdkoAEsGZKhvHvbpKnLilEeqAJLfkSACXSWFLKNHX7 sv1t41NZ8mBdV7lmSICjxhTq6WDbXWQ= X-MC-Unique: 0T5jHrplOE-vgjQ4BnK5Mg-1 X-Original-To: libvir-list@listman.corp.redhat.com From: Peter Krempa To: libvir-list@redhat.com Subject: [PATCH 63/67] docs: kbase/tlscerts: Fix links Date: Tue, 31 May 2022 17:06:38 +0200 Message-Id: <0604cafc2a749b737f6f92128ad287d19848ae26.1654008136.git.pkrempa@redhat.com> In-Reply-To: References: MIME-Version: 1.0 X-Scanned-By: MIMEDefang 2.79 on 10.11.54.5 X-BeenThere: libvir-list@redhat.com X-Mailman-Version: 2.1.29 Precedence: list List-Id: Development discussions about the libvirt library & tools List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: libvir-list-bounces@redhat.com Sender: "libvir-list" X-Scanned-By: MIMEDefang 2.85 on 10.11.54.9 Authentication-Results: relay.mimecast.com; auth=pass smtp.auth=CUSA124A263 smtp.mailfrom=libvir-list-bounces@redhat.com X-Mimecast-Spam-Score: 0 X-Mimecast-Originator: redhat.com Content-Transfer-Encoding: quoted-printable X-ZohoMail-DKIM: pass (identity @redhat.com) X-ZM-MESSAGEID: 1654009769678100005 Content-Type: text/plain; charset="utf-8" Most of the links were broken by moving the article into kbase, but in this case we need to also fix the anchor names. Signed-off-by: Peter Krempa Reviewed-by: J=C3=A1n Tomko --- docs/kbase/tlscerts.rst | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/docs/kbase/tlscerts.rst b/docs/kbase/tlscerts.rst index 962253e853..e4aa5bb3c9 100644 --- a/docs/kbase/tlscerts.rst +++ b/docs/kbase/tlscerts.rst @@ -84,12 +84,12 @@ clients. There are two distinct checks involved: - The client should know that it is connecting to the right server. Check= ing done by client by matching the certificate that the server sends to the server's hostname. May be disabled by adding ``?no_verify=3D1`` to the = `remote - URI `__. + URI <../uri.html#tls-transport>`__. - The server should know that only permitted clients are connecting. This= can be done based on client's IP address, or on client's IP address and cli= ent's certificate. Checking done by the server. May be enabled and disabled i= n the - `libvirtd.conf file `__. + `libvirtd.conf file <../remote.html#libvirtd-configuration-file>`__. For full certificate checking you will need to have certificates issued by= a recognised `Certificate Authority @@ -99,7 +99,7 @@ CA, you can set up your own CA and tell your server(s) an= d clients to trust certificates issues by your own CA. Follow the instructions in the next se= ction. Be aware that the `default configuration for -libvirtd `__ allows any client to +libvirtd <../remote.html#libvirtd-configuration-file>`__ allows any client= to connect provided they have a valid certificate issued by the CA for their = own IP address. You may want to change this to make it less (or more) permissive, depending on your needs. @@ -180,7 +180,7 @@ for validation may be discontinued entirely, so it is s= trongly recommended to include the SAN fields. In the example below, clients will be connecting to the server using a -`URI `__ of ``qemu://compute1.libvirt.org/system``, s= o the +`URI <../uri.html#remote-uris>`__ of ``qemu://compute1.libvirt.org/system`= `, so the CN must be "``compute1.libvirt.org``". Make a private key for the server: --=20 2.35.3