BSD Commit Log Search

   pfctl(8) parser must not ignore error from pfctl_optimize_ruleset().
   Ignoring the error may cause pfctl(8) to load inconsistent ruleset
   preventing pf(4) to enforce desired policy.

   Issue reported and fix suggested by berts _from_ fastmail _dot_ com

   'Looks good.' @deraadt

   sync iwx(4) RX descriptor status field with firmware layout

   Same change was made in iwlwifi about 6 years ago.
   See linux.git commit e365e7de63e5b612d94fb433e38d9414de811f7d

   This matters to us now that we started looking at Rx status bits
   beyond 16 bits in order to check for duplicate subframes in A-MPDUs.

   Found by Coverity (CID 1670294)
   pointed out by and ok jsg@

   update to aspell-0.60.8.2

   Fix support for some older iwx(4) devices broken by changes for BZ support.

   Keep hardware revision info sent to firmware intact for older devices.
   BZ devices store parts of hardware revision information in a new place.
   I accidentally changed the information sent to older devices, which broke
   firmware loading on a subset of AX201/AX210 devices.

   Reported to me by several people, thanks!

   This fix is based on a patch by David Leadbeater.

   update py-holidays to 0.92

   update to py3-requests-cache-1.3.1

   update to nagstamon-3.18.1

   update to getmail-6.19.10 and fix upstream commit which broke getmail_fetch,
   reported by nick@, fix confirmed by maintainer

   update to py3-lmdb-1.8.1

   update to py3-mistune-3.2.0

   update to py3-pypandoc-1.16.2

   update to p5-Crypt-OpenSSL-PKCS10-0.37

   update to p5-Crypt-OpenSSL-RSA-0.37

   update to p5-Crypt-OpenSSL-EC-1.34

   xargs(1): bump posix spec to 2024

   The spec now documents -0 and -r.

   In addition, the spec notes that specifying both -0 and -E are mutually
   exclusive, leaving the actual behavior unspecified.

   ok deraadt@, guenther@ on the spec version bump
   ok millert@ on documenting the interaction between -0 and -E

   update to ruby-3.4.9

   Don't ship browser-preview as is depends on an old version of webkitgtk4.

   Remove www/webkitgtk4.
   It's an optional RUN_DEPENDS and the libsoup2 version of webkitgtk4 will be
   going away soon (libsoup2 is unmaintained).

   Update to apostrophe-3.4 and move to webkitgtk60.

   Move to webkitgtk41.

   rfc3779 regress: explain where the range comes from

   Update to gemini-cli-0.33.1.

   Disable gnutls support

   Update to terraform-1.14.7.

   rfc3779 regress: add an actual range

   This improves the test coverage of make_addressRange() where there is an
   annoyance with unused bits in the RFC 3779 ASN.1 encoding versus trailing
   ones in the network encoding that the X509v3_addr_add_range() API expects.

   Update to libphonenumber-9.0.26.

   Update to gtkmm40-4.22.0.

   Update to epiphany-49.4.

   Update to harfbuzz-13.1.1.

   When pledged, if a process receives a bad descriptor the receiver should
   not be killed.  The EPERM approach used for other conditions is good enough.
   Report from Henry Ford
   this will be errata 7.8/022_recvfd.patch and 7.7/028_recvfd.patch