Build date: 1776031203 - Sun Apr 12 22:00:03 UTC 2026 Build cvs date: 1776023543 - Sun Apr 12 19:52:23 UTC 2026 Build id: 2026-04-13.1 Build tags: amd64-regress ports sysupgrade Applied the following diff(s): /home/anton/tmp/robsd/src-sys-em.diff /home/anton/tmp/robsd/src-sys-ramdisk-diet.diff /home/anton/tmp/robsd/src-sys-uhidev-sispm.diff /home/anton/tmp/robsd/src-sysupgrade.diff P lib/libc/gen/getpagesize.3 P sbin/disklabel/disklabel.8 P share/man/man4/pfsync.4 P share/man/man4/wsmouse.4 P share/man/man4/man4.riscv64/smtcomphy.4 P share/man/man4/man4.riscv64/smtpmic.4 M sys/arch/amd64/conf/RAMDISK P sys/arch/amd64/stand/boot/boot.8 P sys/arch/sparc64/sparc64/locore.s P sys/arch/sparc64/sparc64/trap.c P sys/dev/ic/qwz.c P sys/dev/ic/qwzreg.h P sys/dev/ic/qwzvar.h P sys/dev/pci/if_qwz_pci.c M sys/dev/usb/uhidev.c P sys/net/if_pfsync.c P sys/net/if_pfsync.h M usr.sbin/bgpd/session.c P usr.sbin/fw_update/fw_update.8 U usr.sbin/rpki-client/version.h P usr.sbin/sensorsd/sensorsd.c commit nRwayu9Me07ep5LD Author: kirill Date: 2026/04/12 19:52:23 sys/qwz: fixed some missmatched against ATH12k It fully parse SERVICE_READY_EXT2 peer-metadata capability and fill wmi_resource_config's tail. It also fixes a crash/free of null, and adjusted buffer and timeouts to match Linux to actually get full RDDM. It uses world regulatory domain. Plus a few small typos. qwz now loads, but firmware crashes on scan. OK: mglocker@ sys/dev/ic/qwz.c sys/dev/ic/qwzreg.h sys/dev/ic/qwzvar.h sys/dev/pci/if_qwz_pci.c commit PAjp2BhdS6rDTnbe Author: job Date: 2026/04/12 18:31:16 Prepare for rpki-client 9.8 usr.sbin/rpki-client/version.h commit SEHU9mEDcw8Gu1iI Author: deraadt Date: 2026/04/12 13:29:46 Fix a memory leak on configuration reload, and incorrect termination when a sensor fails to read. From James J. Lippard ok tb usr.sbin/sensorsd/sensorsd.c commit tnKGQbhFmNvyfEIq Author: claudio Date: 2026/04/12 13:22:16 Fix possible reace in ipi_drop_fpstate() ipi_drop_fpstate() needs to check if the current fpu context matches the expected one sent via IPI. Only after that %fprs should be cleared. Use the same asm in ipi_drop_fpstate() as in the start of ipi_save_fpstate(). Also simplify ipi_drop_fpstate() and clearfpstate() since there is no need to enable the FPU before clearing %fprs. OK miod@ kettenis@ deraadt@ sys/arch/sparc64/sparc64/locore.s commit MeNbzfDPZqHNiX0z Author: claudio Date: 2026/04/12 13:17:39 Initialize all FPU registers to all 1 (or -NaN) not only the lower 32. OK miod@ kettenis@ deraadt@ sys/arch/sparc64/sparc64/trap.c commit q28bBrLv7MpjgZWd Author: jsg Date: 2026/04/12 12:48:14 remove unneeded escape; \^@\\10GB -> \^HGB sbin/disklabel/disklabel.8 commit v9d8E9p1jielL6sS Author: jsg Date: 2026/04/12 12:35:06 remove whitespace at eol share/man/man4/wsmouse.4 usr.sbin/fw_update/fw_update.8 commit rAXFaB4mtuDTOvmh Author: jsg Date: 2026/04/12 09:40:30 add back leading . required for roff comments sys/arch/amd64/stand/boot/boot.8 commit aaRSyg6qYW12K0z4 Author: jsg Date: 2026/04/12 09:31:01 remove .Bf matching .Ef removed in previous; fixes unintended bold lib/libc/gen/getpagesize.3 commit Bxv5GGodSfESTRku Author: jsg Date: 2026/04/12 09:17:04 sort SEE ALSO share/man/man4/man4.riscv64/smtcomphy.4 commit 3Gv0x4cOWiRCQ7dx Author: jsg Date: 2026/04/12 09:10:03 SNTPMIC -> SMTPMIC share/man/man4/man4.riscv64/smtpmic.4 commit axKf6qFJvVqlcqoO Author: deraadt Date: 2026/04/12 03:19:26 The pfsync manual page has no mention about safety of this protocol. Furthermore there are no configuration options for "key negotation", so we believe everyone knows to run this on a dedicated wire or on L2 inside some sort of encryption tunnel (it is the natural way to do it in anycase). Books do mention this detail, because books enjoy being more wordy. But the AI's can't figure it out, so put in some words to stop future AI's from sending us slop. share/man/man4/pfsync.4 commit DG5zBksz3GGJWRrY Author: deraadt Date: 2026/04/12 03:16:04 The pfcksum[] field in the pfsync packet header is not a hash of the packet. It provides absolutely no security benefits, keep reading to find out. According to dlg, during early development this field was hopefully going to be a hash related to the ruleset for optimizing state match. That approach was abandoned (I guess because ruleset drift between firewalls happens too often during normal practice). As is usual in protocol development, at least 6 people were already using pfsync in production, so for compatibility the field was not removed... and forgotten. On send, it was left as zero, due to the full-header zero initialization code. So there is no useful checksum or hash stored in this field called 'pfcksum[PF_MD5_DIGEST_LENGTH]'. Actually there isn't a single line of code in the entire tree which writes to this array. Besides the field definition in the structure, there is 1 comment elsewhere mentioning the field. So no code at all. I said no code, which is why there is no code checking it on receive, not even checking if it is still zero. An (obviously) AI-assisted report (which I do not intend to share) arrived which tells us FOR SURE that field is being computed on send, but not checked on arrival which is a security risk!!!! It goes into extensive detail saying where various parts of this subsystem are and how it all fits together but apparently it is all an elaborate fiction built upon two words 'pfcksum' and 'PF_MD5_DIGEST_LENGTH'. No words about security principles are found anywhere in the code or in the manual page because everyone uses this on a dedicated wire between firewall boxes. The human who caused an AI to generate that report did not "peer-review" the result (hint: the command is grep) before sending it to us, and has caused David to pull a muscle when his eyes rolled back too far. To avoid future confusion by AI+humans, rename the field from pfcksum[PF_MD5_DIGEST_LENGTH] to spare[16]. ok dlg sys/net/if_pfsync.c sys/net/if_pfsync.h