From nobody Tue Jun 30 20:44:34 2026 X-Original-To: freebsd-pkgbase@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 4gqZrs4hkFz6jwqy for ; Tue, 30 Jun 2026 20:44:45 +0000 (UTC) (envelope-from ziaee@FreeBSD.org) Received: from mailtransmit05.runbox.com (mailtransmit05.runbox.com [IPv6:2a0c:5a00:149::26]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (prime256v1) server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4gqZrr6rPSz3Gsm for ; Tue, 30 Jun 2026 20:44:44 +0000 (UTC) (envelope-from ziaee@FreeBSD.org) Authentication-Results: mx1.freebsd.org; none Received: from mailtransmit03.runbox ([10.9.9.163] helo=aibo.runbox.com) by mailtransmit05.runbox.com with esmtps (TLS1.2) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.93) (envelope-from ) id 1wefJr-00742S-7o; Tue, 30 Jun 2026 22:44:35 +0200 Received: from [10.9.9.128] (helo=rmmprod06.runbox) by mailtransmit03.runbox with esmtp (Exim 4.86_2) (envelope-from ) id 1wefJq-0004B1-Hh; Tue, 30 Jun 2026 22:44:34 +0200 Received: from mail by rmmprod06.runbox with local (Exim 4.86_2) (envelope-from ) id 1wefJq-000633-G1; Tue, 30 Jun 2026 22:44:34 +0200 Content-Type: text/plain; charset="utf-8" Content-Disposition: inline Content-Transfer-Encoding: quoted-printable List-Id: Packaging the FreeBSD base system List-Archive: https://lists.freebsd.org/archives/freebsd-pkgbase List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-pkgbase@FreeBSD.org List-Id: List-Post: List-Help: List-Subscribe: List-Unsubscribe: List-Owner: Precedence: list MIME-Version: 1.0 Received: from [Authenticated alias (960477)] by runbox.com with http (RMM6); Tue, 30 Jun 2026 20:44:34 GMT From: "Alexander Ziaee" To: "Roger Marquis" CC: "freebsd-pkgbase" Subject: Re: None of "man freebsd-base" (or "man pkgbase"), "man pkg-upgrade", or "man pkg-install" deal with documenting .pkgsave and/or .pkgnew behavior or how to handle such Date: Tue, 30 Jun 2026 20:44:34 +0000 (UTC) X-RMM-Aliasid: 960477 X-Mailer: RMM6 In-Reply-To: <6nrn78o7-0448-qoq3-6681-n5qoq07n3n6r@> Message-Id: X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:50304, ipnet:2a0c:5a00::/29, country:NO] X-Rspamd-Queue-Id: 4gqZrr6rPSz3Gsm X-Spamd-Bar: ---- X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated On 2026-06-30 13:48 -04:00 EDT, "Roger Marquis" wrote:= =20 > Any CVE-related .pkgsave is a ticking time bomb in so far as it > unnecessarily increases the OS' attack surface. These files are not > only easy to find but in the path (shell and lib). Would you please share any specific examples of .pkgsave or equivalent stas= hed new upstream configuration files created by a package manager after fai= led merge in any ecosystem that would have cured any specific CVE in a syst= em that was deployed correctly before the CVE? I have never heard of that, but that would be good information to come to l= ight. > IMO any Ops, SecOps or DevSecOps worth their salary will detect and > encrypt or remove these files from their systems. I think we all agree that operators should always do all of their chores pr= omptly, so we put an entire section on this in the official FreeBSD 15.1 up= grading docs :) One of the principles in the doc project is that the docs are always buggy.= In this case, I'm struggling with how to make it clearer without making it= less accessible. If we put a tip box at the bottom of the section saying "tip: other operati= ng systems also do this, they just don't tell you", I think that would be a= bit condescending and also outside the scope of the doc. People get fatigued easily when they detect irrelevant information or hit p= atches of much higher information density. Then they start skipping and mis= s important stuff, and the ecosystem is much worse off. Again, this is the same behavior I see in all other similar operating syste= ms, the only difference I see is that we are instructing all operators to a= ddress it during the scheduled downtime as part of the approved upgrade pro= cess, and we are documenting files in the reference manual. But the docs ce= rtainly have massive room for improvement! Best, Alex=