From nobody Fri Jan 20 16:07:41 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 4Nz4CP2sNVz2sthV for ; Fri, 20 Jan 2023 16:07:45 +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 4Nz4CN4zXhz44Cm; Fri, 20 Jan 2023 16:07:44 +0000 (UTC) (envelope-from grembo@freebsd.org) Authentication-Results: mx1.freebsd.org; none Received: by mail.evolve.de (OpenSMTPD) with ESMTP id d61055e7; Fri, 20 Jan 2023 16:07:42 +0000 (UTC) Received: by mail.evolve.de (OpenSMTPD) with ESMTPSA id dd145a96 (TLSv1.3:AEAD-AES256-GCM-SHA384:256:NO); Fri, 20 Jan 2023 16:07:42 +0000 (UTC) Date: Fri, 20 Jan 2023 17:07:41 +0100 From: Michael Gmelin To: freebsd@oldach.net (Helge Oldach) Cc: grembo@freebsd.org (Michael Gmelin), list_freebsd@bluerosetech.com, junchoon@dec.sakura.ne.jp, ports@freebsd.org Subject: Re: Can security/ca_root_nss be retired? Message-ID: <20230120170741.66145045.grembo@freebsd.org> In-Reply-To: <202301200815.30K8FWFq051465@nuc.oldach.net> References: <98D727E4-8E1D-435B-BEB6-22BF45B4D3F8@freebsd.org> <202301200815.30K8FWFq051465@nuc.oldach.net> X-Face: $wrgCtfdVw_H9WAY?S&9+/F"!41z'L$uo*WzT8miX?kZ~W~Lr5W7v?j0Sde\mwB&/ypo^}> +a'4xMc^^KroE~+v^&^#[B">soBo1y6(TW6#UZiC]o>C6`ej+i Face: iVBORw0KGgoAAAANSUhEUgAAADAAAAAwBAMAAAClLOS0AAAAJFBMVEWJBwe5BQDl LASZU0/LTEWEfHbyj0Txi32+sKrp1Mv944X8/fm1rS+cAAAACXBIWXMAAAsTAAAL EwEAmpwYAAAAB3RJTUUH3wESCxwC7OBhbgAAACFpVFh0Q29tbWVudAAAAAAAQ3Jl YXRlZCB3aXRoIFRoZSBHSU1QbbCXAAAAAghJREFUOMu11DFvEzEUAGCfEhBVFzuq AKkLd0O6VrIQsLXVSZXoWE5N1K3DobBBA9fQpRWc8OkWouaIjedWKiyREOKs+3PY fvalCNjgLVHeF7/3bMtBzV8C/VsQ8tecEgCcDgrzjekwKZ7TwsJZd/ywEKwwP+ZM 8P3drTsAwWn2mpWuDDuYiK1bFs6De0KUUFw0tWxm+D4AIhuuvZqtyWYeO7jQ4Aea 7jUqI+ixhQoHex4WshEvSXdood7stlv4oSuFOC4tqGcr0NjEqXgV4mMJO38nld4+ xKNxRDon7khyKVqY7YR4d+Cg0OMrkWXZOM7YDkEfKiilCn1qYv4mighZiynuHHOA Wq9QJq+BIES7lMFUtcikMnkDGHUoncA+uHgrP0ctIEqfwLHzeSo+eUA66AqzwN6n 2ZHJhw6Qh/PoyC/QENyEyC/AyNjq74Bs+3UH0xYwzDUC4B97HgLocg1QLYgDDO1v f3UX9Y307Ew4AHh67YAFFsxEpkXwpXY3eIgMhAAE3R19L919nNnuD2wlPcDE3UeT L2ytEICQib9BXgS2fU8PrD82ToYO1OEmMSnYTjSqSv9wdC0tPYC+rQRQD9ESnldF CyqfmiYW+tlALt8gH2xrMdC/youbjzPXEun+/ReXsMCDyve3dZc09fn2Oas8oXGc Jj6/fOeK5UmSMPmf/jL+GD8BEj0k/Fn6IO4AAAAASUVORK5CYII= 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 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Rspamd-Queue-Id: 4Nz4CN4zXhz44Cm 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 Fri, 20 Jan 2023 09:15:32 +0100 (CET) freebsd@oldach.net (Helge Oldach) wrote: > Michael 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. > > > > Without tooling in base to update certs independently of updating > > the OS this will be very painful. > > Cert updates are rare so my feeling is that separate tooling for this > kind of leans into overkill. > > 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. > > One could as well track source and just install from > ${SRC_BASE}/secure/caroot followed by certctl rehash. > Well, whatever is done, such a change needs to be managed properly, which includes adding an entry to UPDATING in ports (e.g., the removal of ca_root_nss from curl broke tools that relied on having certificates in /etc/ssl/certs.pem). -m -- Michael Gmelin