BSD Commit Log Search

   tweak comment, gmake -j (with 0 or no argument) doesn't care about the
   number of cpus, it just runs as much as it can in parallel

   fix distinfo for a re-rolled tarball

   +fonts/adobe-fonts/source-han-{mono,sans,serif}

   afl++: pass proc in MAKE_FLAGS, to avoid running sub-makes with "-j" (which
   uses all cores).

   there is also an issue with this port picking up ports llvm if present,
   if someone wants to take a look..

   Don't build "haptic" support code to avoid missing symbol on sparc64

   That code uses ioctls that we don't implement and end up as unresolved
   symbols in the shared library on sparc64 where base-gcc and ld.bfd are
   used.  ok tb@ thfr@ (maintainer)

   While here, also disable warnings about documentation comments, which
   clutter build logs (from tb@).

   Initial revision

   fonts/adobe-fonts/source-han-sans: import (version 2.005)

   Source Han Sans is Adobe's Pan-CJK sans-serif typeface family,
   developed with Google for Simplified Chinese, Traditional Chinese,
   Japanese, and Korean text.

   OK: bentley@

   fonts/adobe-fonts/source-han-mono: import (version 1.002)

   Source Han Mono is Adobe's Pan-CJK monospaced typeface family, based on
   Source Han Sans and Source Code Pro. It supports Simplified Chinese,
   Traditional Chinese, Japanese, and Korean text in a unified monospace
   design.

   OK: bentley@

   don't include stray __pycache__ dir, that is present in the sdist, in the
   package. py-installer 1.0.0 will strip that ("Do not install __pycache__
   from wheels")

   remove obsolete file

   update to 2026.03.146.4

   revert the stupid decision to not pre-selecting accept buttons in file dialogs

   now my precious enter key is working again in the file dialogs

   Yes, you read it right:
   // GTK's internal response IDs use negative integers (eg. GTK_RESPONSE_CANCEL),
   // leaving zero and positive integers for application-defined response IDs. Use
   // zero for the accept response type since GTK will preselect
   // GTK_RESPONSE_ACCEPT as the default button, which should be avoided to prevent
   // an exploit where the user is instructed to hold Enter before the dialog
   // appears.

   When in copy mode with a large scroll offset and the window is resized
   so that history shrinks, data->oy can exceed screen_hsize causing an
   unsigned integer underflow in the py computation. Clamp data->oy in
   window_copy_resize and window_copy_cmd_refresh_from_pane before the
   subtraction. From futpib at gmail dot com in GitHub issue 4958.

   zap stray _, spotted by stsp

   update to roundcubemail-1.6.15

   update to roundcubemail-1.6.15

   Fix regression where mail search would fail on non-ascii search criteria
   Fix regression where some data url images could get ignored/lost
   Fix SVG Animate FUNCIRI Attribute Bypass - Remote Image Loading via fill/filter/stroke

   Update to cyrus-imapd-3.12.2.

   Update to cargo insta 1.47.1

   https://github.com/mitsuhiko/insta/releases/tag/1.47.1

   Update to ngtcp2 1.22.0

   https://github.com/ngtcp2/ngtcp2/releases/tag/v1.22.0

   add a regression test for ProxyJump/-J; ok dtucker

   apply the same validity rules to usernames and hostnames set for
   ProxyJump/-J on the commandline as we do for destination user/host
   names.

   Specifically, they are no longer allowed to contain most characters
   that have special meaning for common shells. Special characters are
   still allowed in ProxyJump commands that are specified in the config
   files.

   This _reduces_ the chance that shell characters from a hostile -J
   option from ending up in a shell execution context.

   Don't pass untrusted stuff to the ssh commandline, it's not intended
   to be a security boundary. We try to make it safe where we can, but
   we can't make guarantees, because we can't know the parsing rules
   and special characters for all the shells in the world, nor can we
   know what the user does with this data in their ssh_config wrt
   percent expansion, LocalCommand, match exec, etc.


    [4 lines not shown]

   Update to py3-git2-1.19.2.

   Update to bstring-1.1.0.

   libssl regress: adjust golden numbers for RSASSA-PSS

   Add the three RSASSA-PSS SignatureScheme 0x080b, 0x080a, 0x0809 in the
   appropriate spots in (components of) the ClientHello and adjust various
   length octets by adding 6.

   libssl: announce support for RSASSA-PSS signature schemes

   Announce the signature schemes for RSASSA-PSS with pubkey OID RSASSA-PSS
   between RSASSA-PSS with pubkey OID rsaEncryption and RSASSA-PKCS1-v1_5.

   This is the last step in the everlasting saga for making these signature
   schemes and certificates with RSASSA-PSS OID work. Fortunately, these are
   rarely used since they are extremely complex and inefficient also due to
   the large size of the parameters. This addresses bug reports by Steffen
   Ullrich and Tom Lane.

   Tested by bluhm.

   ok djm jsing kenjiro

   ssl_sigalg_pkey_ok: allow RSASSA-PSS with pubkey OID RSASSA-PSS

   This fixes a long-standing logic error that hasn't been noticed because
   we never announced the rsa_pss_pss_sha{256,384,512} SignatureScheme. The
   EVP_PKEY_id() of a RSA-PSS pubkey is EVP_PKEY_RSA_PSS, not EVP_PKEY_RSA.

   Thanks to beck for helping me figure out how to fix this correctly. It
   drove me nuts for a very long time. Problem also noticed by Tom Lane
   due to some PostgreSQL regress failures.

   ok djm jsing kenjiro

   ssl_sigalgs: whitespace tweak

   sync

   stop installing libgbm.a everything should be using libgbm.so
   ok tb@ matthieu@

   Improve OpenBSD::Unveil POD

   The choice of variable names made it somewhat unclear what arguments
   to pass and made it seem the interface might differ from unveil(2).

   ok dgl@