BSD Commit Log Search

   drop ONLY_FOR_ARCHS = ${GCC49_ARCHS}, it's doing nothing because COMPILER
   already sets it

   move COMPILER lines to subdirs so that it's included before bsd.port.mk,
   drop the ONLY_FOR_ARCHS in Makefile.inc.

   www/hugo: 0.168.0

   mention that the h3 flavour includes YAML config support too (both need rust)
   prompted by a mail from Russell Sutherland, ok otto

   ... In programs compiled with reduced visibility, this variable may need
   visibility forced using __attribute__((visibility("default"))).

   devel/sbt: update to 2.0.11

   security/nss: backport the diff from 3.131 & 3.131.1

   Bug 2083709 - Remove eMudhra emSign Root CA - C1 and emSign ECC Root CA - C3 from NSS
   Bug 2084101 - Remove eMudhra emSign Root CA - G3 from NSS

   i'd gladly backport the 3.131 update but it added symbols..

   discussed with/requested by tb@

   deve/sbt: update to 2.0.10

   drop the RDEP on clamav on !rust archs

   drop the RDEP on clamav for !rust archs

   add OpenBSD to #ifdefs for parse_mount_entries

   Update to yosys-0.70 from Thomas Dettbarn.

   security/nss: update to 3.131.1, prodded by tb@.

   - Bug 2084101 - Remove eMudhra emSign Root CA - G3 from NSS.
   - Bug 2083709 - Remove eMudhra emSign Root CA - C1 and emSign ECC Root CA - C3 from NSS.
   see https://firefox-source-docs.mozilla.org/security/nss/releases/nss_3_131_1.html

   add missing python BDEP, and switch from pandoc to lowdown to allow
   building on archs that aren't amd64/aarch64.

   add missing python BDEP, and switch from pandoc to lowdown to allow
   building on archs that aren't amd64/aarch64.

   Bump _MODGO_SYSTEM_VERSION for lang/go update.

   Update lang/go to 1.27.3.

   This rejects certificate chains that include a number of intermediates
   issued by eMudhra Technologies Limited.

   Discussed with tb@

   games/dopewars: add _permit_setugid S_ISGID marker

   www/firefox-esr: MFC update to 153.5.1.

   see https://www.firefox.com/en-US/firefox/153.5.1/releasenotes/
   fixes https://www.mozilla.org/en-US/security/advisories/mfsa2026-112/

   www/firefox-esr: update to 153.5.1.

   see https://www.firefox.com/en-US/firefox/153.5.1/releasenotes/
   fixes https://www.mozilla.org/en-US/security/advisories/mfsa2026-112/

   www/mozilla-firefox: MFC update to 158.0.1.

   see https://www.firefox.com/en-US/firefox/158.0.1/releasenotes/
   fixes https://www.mozilla.org/en-US/security/advisories/mfsa2026-111/

   www/mozilla-firefox: update to 158.0.1.

   see https://www.firefox.com/en-US/firefox/158.0.1/releasenotes/
   fixes https://www.mozilla.org/en-US/security/advisories/mfsa2026-111/

   Clear tabs and wide characters changed by ICH, DCH and ECH and insert
   mode, based on change in GitHub issue 5779 from neocat at neocat dot jp.

   Add -P to display-panes to print the selected pane ID.

   Provide out-of-band information about firmware events to bwfm_rx().

   This allows the driver to ignore firmware events which did not actually
   arrive on a firmware event Rx ring. An exception are USB devices which
   seem to only offer a single Rx pipe across which data frames and firmware
   events are multiplexed.

   Previously, firmware events were detected purely based on attributes of
   the ethernet header in a received frame, which could potentially be a
   crafted header in frames received on the air, injecting firmware events
   into the driver from the outside.
   I am unsure if such injection can happen on real hardware. It will depend
   on the firmware being careful enough about filtering out event frames it
   did not generate itself. The corresponding report by Acts1631 was triggering
   the problem by calling bwfm_rx() manually with crafted ethernet packets.

   But this is worth hardening nonetheless, and the Linux brcmfmac driver
   has a similar check in place.

   Tested by martijn@ on PCI in hostap mode and by myself on USB on client mode.

   add bitmap_find_next_zero_area() for xe

   do not blindly trust bss->length in bwfm scan results; pointed out by Acts1631

   A proposed diff to fix the issue was provided by Acts1631, but I wrote my own.

   avoid overflow while bounds-checking bwfm_bss_info messages; from Acts1631

   drop bwfm firmware event packets which report a bad data length; from Acts1631

   add missing bounds checks for data length reported by two bwfm firmware events

   Tested in hostap mode by martijn@