BSD Commit Log Search

   Update to CookCLI 0.28.1.

   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@

   Initialize all FPU registers to all 1 (or -NaN) not only the lower 32.

   OK miod@ kettenis@ deraadt@

   Missing version bump

   Update KDE Plasma 6.6.4, Bugfix Releases for March and April

   https://kde.org/announcements/changelogs/plasma/6/6.6.2-6.6.3/
   https://kde.org/announcements/changelogs/plasma/6/6.6.3-6.6.4/

   remove unneeded escape; \0\10GB -> \010GB

   remove whitespace at eol

   Update to xan 0.57.0.

   add back leading . required for roff comments

   Update to parallel 20260322.

   remove .Bf matching .Ef removed in previous; fixes unintended bold

   sort SEE ALSO

   SNTPMIC -> SMTPMIC

   lang/gleam: Update to 1.15.3

   Remove BROKEN-sparc64 since GCC 15 does support C++20

   Update py-supermercado to 0.4.0.

   Update to rclone-1.73.4

   Changes: https://rclone.org/changelog/#v1-73-4-2026-04-08

   libclock: add POSIX-compatible AlignedTimer for OpenBSD

   https://invent.kde.org/plasma/plasma-workspace/-/merge_requests/6487

   timerfd_create(2) and timerfd_settime(2) are Linux-specific and not available
   on OpenBSD. This alternative implementation uses a single-shot QTimer that
   reschedules itself.

   The next expiry is computed by rounding the current CLOCK_REALTIME down to the
   last interval boundary and stepping forward by one interval.

   Now that ports-gcc is GCC 15, C++20 is available on sparc64

   Remove BROKEN-sparc64

   This was marked BROKEN-sparc64 back when PHP 8.1 was still in the tree.

   The issues then no longer apply, it builds fine on sparc64.

   Remove BROKEN-sparc64

   GCC 15 has the needed bit.h file that was missing when this
   was marked BROKEN-sparc64 (like openttd, which was pointed out
   by gkoehler).

   Remove BROKEN-sparc64 now that it builds again.

   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.

   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

    [19 lines not shown]

   First step to fixing build on sparc64 from Brad Smith

   Update biopython 1.87.

   Update nco to 5.3.8.

   Prompted by maintainer Marco van Hulten

   Update to rust-openssl-tests 20260411

   Add patch to allow libressl 4.3.x

   Before it is disabled, unveil allows you to override the settings on
   any vnode.  A block of #if 0 code suggests this might be different.
   That can be deleted.  This also shows one word "other" in the manual
   page is misleading.
   question asked by Stuart Thomas
   ok beck

   wrap the ; on a single while() line

   A binary without a PT_LOAD exec segment would later read a pinsyscall table
   and damage it strangely.  Such a binary cannot actually run, but we should
   avoid the internal pinsyscall table damage, and fail the execve with EINVAL.
   reported by Stuart Thomas
   ok guenther