From nobody Fri Jan 20 08:45:20 2023 X-Original-To: ports@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 4NytP44jhJz2swVq for ; Fri, 20 Jan 2023 08:45:28 +0000 (UTC) (envelope-from grembo@freebsd.org) Received: from mail.evolve.de (mail.evolve.de [213.239.217.29]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA512 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mail.evolve.de", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4NytP42D0Cz4Vv2; Fri, 20 Jan 2023 08:45:28 +0000 (UTC) (envelope-from grembo@freebsd.org) Authentication-Results: mx1.freebsd.org; none Received: by mail.evolve.de (OpenSMTPD) with ESMTP id 5bc5ab4f; Fri, 20 Jan 2023 08:45:21 +0000 (UTC) Received: by mail.evolve.de (OpenSMTPD) with ESMTPSA id 7ec037aa (TLSv1.3:AEAD-AES256-GCM-SHA384:256:NO); Fri, 20 Jan 2023 08:45:21 +0000 (UTC) Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable List-Id: Porting software to FreeBSD List-Archive: https://lists.freebsd.org/archives/freebsd-ports List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-ports@freebsd.org X-BeenThere: freebsd-ports@freebsd.org Mime-Version: 1.0 (1.0) Subject: Re: Can security/ca_root_nss be retired? From: Michael Gmelin In-Reply-To: <202301200815.30K8FWFq051465@nuc.oldach.net> Date: Fri, 20 Jan 2023 09:45:20 +0100 Cc: list_freebsd@bluerosetech.com, junchoon@dec.sakura.ne.jp, ports@freebsd.org Message-Id: <2A3836DC-E9E3-4AF4-81BD-48E52C695B43@freebsd.org> References: <202301200815.30K8FWFq051465@nuc.oldach.net> To: freebsd@oldach.net X-Mailer: iPhone Mail (20B110) X-Rspamd-Queue-Id: 4NytP42D0Cz4Vv2 X-Spamd-Bar: ---- X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:24940, ipnet:213.239.192.0/18, country:DE] X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-ThisMailContainsUnwantedMimeParts: N > On 20. Jan 2023, at 09:15, freebsd@oldach.net wrote: >=20 > =EF=BB=BFMichael Gmelin wrote on Fri, 20 Jan 2023 08:51:31 +0100 (CET): >>>> On 20. Jan 2023, at 07:45, freebsd@oldach.net wrote: >>> Definitely however ca_root_nss should go away in favor of the built-in >>> cert infrastructure and the ports still referring to this legacy should >>> be updated. >>=20 >> Without tooling in base to update certs independently of updating the OS t= his will be very painful. >=20 > Cert updates are rare so my feeling is that separate tooling for this > kind of leans into overkill. >=20 > The other OS with the colorful tiles will update certs through an OS > update (and reboot usually). Along the same paradigm, freebsd-update > would do the job. >=20 > One could as well track source and just install from > ${SRC_BASE}/secure/caroot followed by certctl rehash. On a single system that works just fine, but when you have many servers, vms= , containers/jails (including automatic ones in CI, e.g., GitHub actions) th= is gets tedious. In our local cluster I would probably end up creating a pri= vate package based on what is in current (think security/freebsd-caroot).