From nobody Thu Jul 3 05:38:28 2025 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 4bXltL0msKz61Twk for ; Thu, 03 Jul 2025 05:38:34 +0000 (UTC) (envelope-from gordon@tetlows.org) Received: from outbound.mr.icloud.com (p-west2-cluster5-host2-snip4-4.eps.apple.com [57.103.71.117]) (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 4bXltK3xxRz3x1s for ; Thu, 03 Jul 2025 05:38:33 +0000 (UTC) (envelope-from gordon@tetlows.org) Authentication-Results: mx1.freebsd.org; none DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=tetlows.org; s=sig1; bh=dcaOi7bN3MOaJgAQUbVGcZ/bSyeTK544yeglmfcY3mI=; h=From:To:Subject:Date:Message-ID:MIME-Version:Content-Type:x-icloud-hme; b=IIewmTYnAj3jeMUDe8UfCW+Vu6yYMNL0g4ROlYSxUkA5EdZEIR2CP/5YHWjiiKkBU eIwRKG1DXKB/BH03kx5rsk+IFr7vk9yTs3xMMpgFPk+amB7SSWkCTwM5gSqW6Pcwug KmFI1NTk7soCjcbmGTcTgrqcoNXuCKl00UkmGzxaYpcZKfXmV4T++oqjoPGW5ilE2D 1Ew70FKuRS2opDoumd8q2xYLRPtQQew6OAoWo4YXz+QihFotwx8MpfdbVh1ptyZtwy VNefiuIrlQkujFYYxevrRysaXJ6aOYVx5HI9dTbBwp+QuuLzAWjA+Aq3Gvn0KuJdAK 2EsPrbhTO+SlA== Received: from outbound.mr.icloud.com (unknown [127.0.0.2]) by outbound.mr.icloud.com (Postfix) with ESMTPS id 48CB91800090; Thu, 3 Jul 2025 05:38:29 +0000 (UTC) Received: from [10.0.1.126] (mr-asmtp-me-k8s.p00.prod.me.com [17.57.152.38]) by outbound.mr.icloud.com (Postfix) with ESMTPSA id 84FAF18000B2; Thu, 3 Jul 2025 05:38:29 +0000 (UTC) From: Gordon Tetlow To: Mark Millard Cc: FreeBSD-pkgbase@freebsd.org, FreeBSD-STABLE Mailing List Subject: Re: Question: PkgBase base_latest handling for Errata-Notice updates and Security-Advisory updates? Date: Wed, 02 Jul 2025 22:38:28 -0700 X-Mailer: MailMate (2.0r6272) Message-ID: In-Reply-To: <49DF77DC-C7CB-45FC-A080-E6A2033FDEB2@yahoo.com> References: <49DF77DC-C7CB-45FC-A080-E6A2033FDEB2.ref@yahoo.com> <49DF77DC-C7CB-45FC-A080-E6A2033FDEB2@yahoo.com> 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 MIME-Version: 1.0 Content-Type: multipart/signed; boundary="=_MailMate_791A0522-C6D7-4A83-9B8C-FBDE7AC0ADF1_="; micalg=pgp-sha512; protocol="application/pgp-signature" X-Proofpoint-Spam-Details-Enc: AW1haW4tMjUwNzAzMDA0MyBTYWx0ZWRfX4tvdMGD28Inc 3HRZjzL27c4k201TYq4sbJaEFJGtmd1bSYp1RSu+vu7GATiokBW/UziZF3J2nthWR/18eqBs+ns ATy0AFhxK0Wz0tD5zjAvqX8UYTDNPqF2wsuBy5+9j4ZlTlQrBjbOUS2M1Fimq5zLaBbYH/LwYjv sqp8Ux4PaxRzeA3EYmNf2eu9s2HL+bjgVnjSwdf7EgMgoOnWEkp8sKmuPu+HcF38XZZB4biAhhI MudTNO25NOLBFDrmkpP/Q4LJ2WMfyYy1L1NVju1xGUENd/V2pfE6sb306Le8WfWgkE+2mg1NA= X-Proofpoint-GUID: Xw6CNBNWqNGg10-SRIupm1UJqy4xUWLF X-Proofpoint-ORIG-GUID: Xw6CNBNWqNGg10-SRIupm1UJqy4xUWLF X-Proofpoint-Virus-Version: vendor=baseguard engine=ICAP:2.0.293,Aquarius:18.0.1099,Hydra:6.1.7,FMLib:17.12.80.40 definitions=2025-07-03_01,2025-07-02_04,2025-03-28_01 X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 phishscore=0 malwarescore=0 adultscore=0 spamscore=0 bulkscore=0 mlxlogscore=855 mlxscore=0 suspectscore=0 clxscore=1030 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.22.0-2506060001 definitions=main-2507030043 X-Rspamd-Queue-Id: 4bXltK3xxRz3x1s X-Spamd-Bar: ---- X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:714, ipnet:57.103.68.0/22, country:US] This is an OpenPGP/MIME signed message (RFC 3156 and 4880). --=_MailMate_791A0522-C6D7-4A83-9B8C-FBDE7AC0ADF1_= Content-Type: multipart/alternative; boundary="=_MailMate_A60D3127-8AAD-4EA2-9A3C-87274A97A2A3_=" --=_MailMate_A60D3127-8AAD-4EA2-9A3C-87274A97A2A3_= Content-Type: text/plain; charset=UTF-8; markup=markdown Content-Transfer-Encoding: quoted-printable On 2 Jul 2025, at 21:57, Mark Millard wrote: > The questions, for the example contexts: (1) FreeBSD-EN-25:09.libc . . = =2E > > It lists: > > Branch/path Hash Revision > - ---------------------------------------------------------------------= ---- > stable/14/ c43ae65b4b89 stable/14-n271080 > > Note: That description is trying to document both the kernel (/usr/src/= sys/) and the world (/usr/src/ other than sys/) vintage. It turns out her= e that the errata is a world libc patch, not a kernel patch. By contrast = (2) FreeBSD-EN-25:11.ena has: > > Branch/path Hash Revision > - ---------------------------------------------------------------------= ---- > stable/14/ 3f4a674a8ee4 stable/14-n271320 > > Which is a kernel patch, not a world patch. One could imagine some patc= hes that involve both. Or neither. Maybe we publish ena or some subset of modules as sys-net-dri= vers, if we so choose. > How are PkgBase users to know the status relative to such a description= that is based on a git Hash and Revision? The format of our advisories will need to change for a pkgbase world. I d= on=E2=80=99t know how exactly that will work, but it seems reasonable tha= t we may need to include pkgbase revision information as part of an SA/EN= =2E > Another possibility is that specific FreeBSD-*-14.snap*.pkg names might= instead be listed for PkgBase identification. A PkgBase build can be mad= e up with a mix of .snap*.pkg suffixes across the various *.pkg files inv= olved. And there are hundreds of *.pkg files. So comparisons could be mes= sy to deal with. > > > Has the technique for this subject area been decided yet? If yes, what = is the intended technique? Speaking on behalf of secteam, not in the least. This is something we sho= uld probably add to our conversations, but I also think it is the kind of= thing that we may have to work out in the moment as we stumble our way t= hrough it. Ideally, this will be done with plenty of time to get everythi= ng ironed out. Best, Gordon Hat: security-officer --=_MailMate_A60D3127-8AAD-4EA2-9A3C-87274A97A2A3_= Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

On 2 Jul 2025, at 21:57, Mark Millard wrote:

The questions, for the example contexts: (1) FreeBSD-EN-2= 5:09.libc . . .

It lists:

Branch/path Hash Revision

stable/14/ c43ae65b4b89 stable/14-n271080

Note: That description is trying to document both the ker= nel (/usr/src/sys/) and the world (/usr/src/ other than sys/) vintage. It= turns out here that the errata is a world libc patch, not a kernel patch= =2E By contrast (2) FreeBSD-EN-25:11.ena has:

Branch/path Hash Revision

stable/14/ 3f4a674a8ee4 stable/14-n271320

Which is a kernel patch, not a world patch. One could ima= gine some patches that involve both.

Or neither. Maybe we publish ena or some subset of module= s as sys-net-drivers, if we so choose.

How are PkgBase users to know the status relative to such= a description that is based on a git Hash and Revision?

The format of our advisories will need to change for a pk= gbase world. I don=E2=80=99t know how exactly that will work, but it seem= s reasonable that we may need to include pkgbase revision information as = part of an SA/EN.

Another possibility is that specific FreeBSD--14.snap= .pkg names might instead be listed for PkgBase identification. A Pkg= Base build can be made up with a mix of .snap*.pkg suffixes across the va= rious *.pkg files involved. And there are hundreds of *.pkg files. So com= parisons could be messy to deal with.

Has the technique for this subject area been decided yet?= If yes, what is the intended technique?

Speaking on behalf of secteam, not in the least. This is = something we should probably add to our conversations, but I also think i= t is the kind of thing that we may have to work out in the moment as we s= tumble our way through it. Ideally, this will be done with plenty of time= to get everything ironed out.

Best,
Gordon
Hat: security-officer

--=_MailMate_A60D3127-8AAD-4EA2-9A3C-87274A97A2A3_=-- --=_MailMate_791A0522-C6D7-4A83-9B8C-FBDE7AC0ADF1_= Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename=signature.asc Content-Type: application/pgp-signature; name=signature.asc -----BEGIN PGP SIGNATURE----- iQFHBAEBCgAxFiEEuyjUCzYO7pNq7RVv5fe8y6O93fgFAmhmF1QTHGdvcmRvbkB0 ZXRsb3dzLm9yZwAKCRDl97zLo73d+PxKCACMENjot0r09aBRx3xjKrIwu6cBTxck c3CkrzpIHXa3msSwwZOC0x4Kxm3LRCJk6oNoAZ/ejedJHNVnRPPsDSOyhxwXgjeP 4tnbrGJ+MUWspf2IGmlUA4YDaYthU6B7lGgTCJLSZbI0/r6DRMIKffjI4WpUEGJN L5xb3sOOVdbyelrNQmfSkVgWHr21VoPvGV+zYmpPYi1bsUwJysEHSB4mcwJTtlLk wk90oAtMaZkZNebmGWM7LR/wEl46LG0UIDocKiRuoXk0h9WGrginltsgcVHgrxIH FBHKTGTT7//3+ESwrSzMU9RVe9Ki/n32O8mrbwaE8wFqw/Ga5v56loSX =NH8Q -----END PGP SIGNATURE----- --=_MailMate_791A0522-C6D7-4A83-9B8C-FBDE7AC0ADF1_=--