Update libexpat to version 2.8.3.
Relevant for OpenBSD are bug fixes #1297 #1300 #1286 #1305 #1306,
other changes #1303. Library bump is not necessary. CVE-2026-72522
OK deraadt@ tb@
libsndio: On the wire, identify MIDI ports by names instead of indices
This makes handling of all type of MIDI ports and audio devices
roughtly the same, which is simpler. The old scheme is still accepted by
the server for compatibility with old libraries.
libsndio: Delete support of "snd/0.foo" device syntax
Support for such syntax was dropped around 5 years ago, but the
corresponding code was forgotten.
sndiod: Associate a midithru structure to MIDI ports
Allows "midi/X" and "midithru/X" ports to be handled by the same code,
which is simpler than the current approach.
sndiod: Make midithru_ref() return 1 on success
Currently midithru_ref() never fails, but this is what all other
xxx_ref() functions do and may ease future changes.
Unpublish the segment before entering the potentially sleeping
shm_deallocate_segment() in the sys_shmat() and sys_shmctl() paths. The
remaining shm_delete_mapping() already has the right order.
From Acts1631
Put back the whitelist approach previous to 1.18, because without a
specific whitelist, arbitrary *TINY* requests can flow through here
which lack the required structure header. Issue found by gnezdo.
ok gnezdo jmatthew
Reassemble IP fragments in correct routing domain.
Fragment reassembly in pf(4) and inet(4) and inet6(4) did not respect
the routing domain. Fragments from different routing domains could
be merged together. Keep track of rdomain in pf and network stack.
Convert routing table to routing domain where necessary. Sort
struct fields by size.
report and diff from Acts1631; fixes by bluhm@; OK sashan@
iked: remove pointless call to X509_get_subject_name()
A deserialized certificate always has a subject, so this check doesn't
do anything useful. This was added in r1.7 (2010) as a mostly cosmetic
return check, and it has been useless since r1.30 (2014) when the subject
variable became unused. A subsequent removal of subject in r1.66 (2020)
made this look weird (why would you check subject but not issuer, SPKI,
...?), so garbage collect it.
ok hshoexer
Overhaul documentation of the -offset and -width arguments to make
the macro reference section easier to read and less repetitive,
and to document these arguments more precisely in a less obtrusive place.
* Move the gory details out of the descriptions of .Bd and .Bl;
only state the defaults and recommended arguments there.
* Stop documenting -offset right and -offset center. Neither is
implemented in mandoc(1), both are handled very poorly by groff
and almost never occur in the wild.
* Add a new WIDTH SPECIFICATIONS section after the macro reference.
hdestroy(3): stop freeing key values
POSIX leaves ownership of ENTRY.key with the caller. Our current behaviour
came from NetBSD when this code was imported in 2004. NetBSD and FreeBSD
both stopped freeing key values in July 2014. NetBSD in commit fe0a1a6 and
FreeBSD in commit e19f362.
Remove the call to free(3) to align ourselves with NetBSD, FreeBSD and
POSIX. Also adjust rsync for the change in semantics.
Flagged by Sortix os-test.
ok millert@, deraadt@
limits.h: bump _POSIX_THREAD_THREADS_MAX to 64
This matches POSIX and the other BSDs. The mismatch was flagged by Sortix
os-test.
ok guenther@, asou@, deraadt@
acpidmar(4): Store PCI domain in softc for segment mapping
Ensure we get a valid segement and enforce use of the IOMMU.
While there:
- tweak printf to use segment instead of PCI domain
- use ACPI provided segment instead of hardcoded 0 in ivhd_showpage()
ok kettenis@
iked: avoid parameter overload
Old ca_validate_cert() API interpreted data pointer as parsed X509
structure if len == 0 and crashed if a zero size certificate buffer
was passed instead. Now we have an explicit certifcate and key
parameter.
from hshoexer@ markus@; ok bluhm@ tb@ tobhe@
this is errata/7.9/009_iked.patch.sig
iked: avoid parameter overload
Old ca_validate_cert() API interpreted data pointer as parsed X509
structure if len == 0 and crashed if a zero size certificate buffer
was passed instead. Now we have an explicit certifcate and key
parameter.
from hshoexer@ markus@; ok bluhm@ tb@ tobhe@
this is errata/7.8/045_iked.patch.sig