From nobody Mon Oct 14 12:32:36 2024 X-Original-To: freebsd-current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4XRxT33v9zz5YVn4 for ; Mon, 14 Oct 2024 12:32:39 +0000 (UTC) (envelope-from void@f-m.fm) Received: from fhigh-a8-smtp.messagingengine.com (fhigh-a8-smtp.messagingengine.com [103.168.172.159]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4XRxT2644gz45GV for ; Mon, 14 Oct 2024 12:32:38 +0000 (UTC) (envelope-from void@f-m.fm) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=f-m.fm header.s=fm2 header.b=vf7dS6FJ; dkim=pass header.d=messagingengine.com header.s=fm2 header.b="Y bSnDwI"; spf=pass (mx1.freebsd.org: domain of void@f-m.fm designates 103.168.172.159 as permitted sender) smtp.mailfrom=void@f-m.fm; dmarc=pass (policy=none) header.from=f-m.fm Received: from phl-compute-09.internal (phl-compute-09.phl.internal [10.202.2.49]) by mailfhigh.phl.internal (Postfix) with ESMTP id 4E35B1140112 for ; Mon, 14 Oct 2024 08:32:38 -0400 (EDT) Received: from phl-mailfrontend-02 ([10.202.2.163]) by phl-compute-09.internal (MEProxy); Mon, 14 Oct 2024 08:32:38 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=f-m.fm; h=cc :content-transfer-encoding:content-type:content-type:date:date :from:from:in-reply-to:in-reply-to:message-id:mime-version :references:reply-to:subject:subject:to:to; s=fm2; t=1728909158; x=1728995558; bh=kz3yxJmvthg6h59GUlpNxemqDAqHojxbQMDAPFj+7co=; b= vf7dS6FJ1GCsVfvpcCQTMt+c9dlGl11HnkXgpe3IOBCo0rlUETliVKtx+8Tvmns1 UJuyNVDmCDrEaOo6QjgL56fAtSJeRp1TJTbXKCZX/t8A6kpDL1xi4bbEsRIqF+rq LkU0lKa6bdnwAzXtL7rpa2onn3t1TKWo7qXp1R7qSR/QEqWvyspPT3UeTMJ4ZfNu wMH8kRM6aoH76yAOqE7V7TZIoznV8FoBV4UeahouMRaTV2uYqeL5IDrlNUqLsFGu AdS/s9IONILbL2ejn+DuCWnJsc5WrfOd8ohiQw/P6jDSe0/tsfqRtc0gfyTXMTrp WBAjmz1C7YUP69GB95s5nw== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :content-type:date:date:feedback-id:feedback-id:from:from :in-reply-to:in-reply-to:message-id:mime-version:references :reply-to:subject:subject:to:to:x-me-proxy:x-me-proxy :x-me-sender:x-me-sender:x-sasl-enc; s=fm2; t=1728909158; x= 1728995558; bh=kz3yxJmvthg6h59GUlpNxemqDAqHojxbQMDAPFj+7co=; b=Y bSnDwIkTes15Hw4EKvo1xykeQK7ohnUK7tAF1T+km4Xxqe8tEi6+E+VCQqOEj5vN crMdRgMIzKBanac5I9uboT2H9K2pdl94D6LfJhVyFDjRs5pJCjDqByFcVkvqBztU 4egaymbX+2HALv3QvPpZUcJN0g/j+C6opxJgdE7aDE0ycpqnYssMbxo+gqK33v00 AgWlxKd9S98I5ppr+T0wip+OkuxnEpQUIa3WSb2nXiVDmc3fSlIzVfwCiEiCK+aQ tyj4IrlHSY0Fg17YG+Owesjm2KQuep/UVkb5LUkpYTFpFGyPTGs+NXfWK+e/6xSc +nlGIU+8/s0I34fzFX+Iw== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeeftddrvdeghedghedvucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdggtfgfnhhsuhgsshgtrhhisggvpdfu rfetoffkrfgpnffqhgenuceurghilhhouhhtmecufedttdenucenucfjughrpeffhffvuf fkfhggtggugfgjsehtkeertddttddunecuhfhrohhmpehvohhiugcuoehvohhiugesfhdq mhdrfhhmqeenucggtffrrghtthgvrhhnpeekvdejiedtjeehkeeikeekiedutdffvddute ehveegieejhedtffefgeegkedtfeenucevlhhushhtvghrufhiiigvpedtnecurfgrrhgr mhepmhgrihhlfhhrohhmpehvohhiugesfhdqmhdrfhhmpdhnsggprhgtphhtthhopedupd hmohguvgepshhmthhpohhuthdprhgtphhtthhopehfrhgvvggsshguqdgtuhhrrhgvnhht sehfrhgvvggsshgurdhorhhg X-ME-Proxy: Feedback-ID: i2541463c:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA for ; Mon, 14 Oct 2024 08:32:37 -0400 (EDT) Date: Mon, 14 Oct 2024 13:32:36 +0100 From: void To: freebsd-current@freebsd.org Subject: Re: new tls-cert-store and cert-bundle methods Message-ID: Mail-Followup-To: freebsd-current@freebsd.org References: <864j5fuo7d.fsf@ltc.des.dev> List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@FreeBSD.org MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1; format=flowed Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <864j5fuo7d.fsf@ltc.des.dev> X-Spamd-Result: default: False [-3.80 / 15.00]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_SHORT(-1.00)[-0.999]; DMARC_POLICY_ALLOW(-0.50)[f-m.fm,none]; MID_RHS_NOT_FQDN(0.50)[]; R_DKIM_ALLOW(-0.20)[f-m.fm:s=fm2,messagingengine.com:s=fm2]; RWL_MAILSPIKE_VERYGOOD(-0.20)[103.168.172.159:from]; R_SPF_ALLOW(-0.20)[+ip4:103.168.172.128/27:c]; MIME_GOOD(-0.10)[text/plain]; RCVD_IN_DNSWL_LOW(-0.10)[103.168.172.159:from]; TO_MATCH_ENVRCPT_ALL(0.00)[]; RCVD_TLS_LAST(0.00)[]; RCPT_COUNT_ONE(0.00)[1]; ARC_NA(0.00)[]; FREEMAIL_FROM(0.00)[f-m.fm]; RCVD_COUNT_THREE(0.00)[3]; MIME_TRACE(0.00)[0:+]; FROM_HAS_DN(0.00)[]; FREEMAIL_ENVFROM(0.00)[f-m.fm]; PREVIOUSLY_DELIVERED(0.00)[freebsd-current@freebsd.org]; TO_DN_NONE(0.00)[]; FROM_EQ_ENVFROM(0.00)[]; DKIM_TRACE(0.00)[f-m.fm:+,messagingengine.com:+]; MLMMJ_DEST(0.00)[freebsd-current@freebsd.org]; ASN(0.00)[asn:209242, ipnet:103.168.172.0/24, country:US]; RCVD_VIA_SMTP_AUTH(0.00)[]; MISSING_XM_UA(0.00)[]; DWL_DNSWL_NONE(0.00)[messagingengine.com:dkim] X-Rspamd-Queue-Id: 4XRxT2644gz45GV X-Spamd-Bar: --- On Mon, Oct 14, 2024 at 09:40:38AM +0200, Dag-Erling Smørgrav wrote: >void writes: >> Now that we have system tls-cert-store, if one needs to reference >> a tls-cert-bundle like provided by ca_root_nss, do we need >> to concatenate all of the certs listed in /usr/share/certs/trusted >> into, for example cert.pem then symlink /etc/ssl/cert.pem to >> that concatenated file? > >This is being worked on. For now, if you need a bundle, just install >ca_root_nss, which has the same contents as the system store but in >bundle form. Thank you for this info. I have encountered one consequence of the above situation very recently that stopped a port from initially functioning: deskutils/nextcloudclient . It gave "The issuer certificate of a locally looked up certificate could not be found" with the cloud's letsencrypt cert. Installation of ca_root-nss allowed syncing up to the cloud to proceed via nextcloudclient. Access via web browser was never an issue. --