Restore line whose content vanished in previous
Somehow in the previous version, the content of one line was
removed, leaving just the indentation tabs... restore that line.
While here, and inspired by that line remnant, check for trailing
whitespace, and obliterate all of it that is unintentional (there
is one space in an EDIT_ME in a here-doc which is intended).
Also, in the rarely used "zones added"/"zones removed" commit message,
for the set lists, add some vertical white space before the listings
of any zones added or removed (happens so rarely, I'm not sure that
code has ever been used).
Remove unif{8,9}
They both have serious CVEs and are no longer supported.
unifi10 is supported, wip & pkgsrc has been updated to a version with the
(known) security issues fixed, and it should be supported on any platform
which can run unifi8 or 9
Pull up following revision(s) (requested by christos in ticket #285):
external/ibm-public/postfix/dist/conf/main.cf: revision 1.13
fix so that it works out of the box (from RVP)
Pull up following revision(s) (requested by skrll in ticket #284):
sys/arch/riscv/include/vmparam.h: revision 1.16
risc-v: bump some parameter values on riscv64
Match all other 64bit platforms for
- PAGER_MAP_DEFAULT_SIZE
- UBC_WINSHIFT
- UBC_NWINS
Spotted by thorpej
PR misc/60253 (conditionally) remove CRYPTO using example
This completes the previous (2026-03-03) change, by removing an
example from the EXAMPLES section, which would only work if nc
was built with the CRYPTO option.
Like the previous, changing the definition of the number register C
in the man page source from 0 to 1 will reinstate the example, along
with all of the CRYPTO options, but makes no sense unless someone
does the required work to be able to build nc with CRYPTO defined.
No pullups required, the previous changes weren't pulled up either.
py-django5: updated to 5.2.14
Django 5.2.14 fixes three security issues with severity “low” in 5.2.13.
CVE-2026-5766: Potential denial-of-service vulnerability in ASGI requests via file upload limit bypass¶
ASGI requests with a missing or understated Content-Length header could bypass the FILE_UPLOAD_MAX_MEMORY_SIZE limit, potentially loading large files into memory and causing service degradation.
As a reminder, Django expects a limit to be configured at the web server level rather than solely relying on FILE_UPLOAD_MAX_MEMORY_SIZE.
This issue has severity “low” according to the Django security policy.
CVE-2026-35192: Session fixation via public cached pages and SESSION_SAVE_EVERY_REQUEST¶
Response headers did not vary on cookies if a session was not modified, but SESSION_SAVE_EVERY_REQUEST was True. A remote attacker could steal a user’s session after that user visits a cached public page.
This issue has severity “low” according to the Django security policy.
CVE-2026-6907: Potential exposure of private data due to incorrect handling of Vary: * in UpdateCacheMiddleware¶
[2 lines not shown]
py-django: updated to 6.0.5
6.0.5
Django 6.0.5 fixes three security issues with severity “low” and several bugs in 6.0.4.
CVE-2026-5766: Potential denial-of-service vulnerability in ASGI requests via file upload limit bypass
ASGI requests with a missing or understated Content-Length header could bypass the FILE_UPLOAD_MAX_MEMORY_SIZE limit, potentially loading large files into memory and causing service degradation.
As a reminder, Django expects a limit to be configured at the web server level rather than solely relying on FILE_UPLOAD_MAX_MEMORY_SIZE.
This issue has severity “low” according to the Django security policy.
CVE-2026-35192: Session fixation via public cached pages and SESSION_SAVE_EVERY_REQUEST
Response headers did not vary on cookies if a session was not modified, but SESSION_SAVE_EVERY_REQUEST was True. A remote attacker could steal a user’s session after that user visits a cached public page.
This issue has severity “low” according to the Django security policy.
[12 lines not shown]
freeradius: updated to 3.2.8
FreeRADIUS 3.2.8 Wed 20 Aug 2025 12:00:00 UTC urgency=low
Configuration changes
* Replace dictionary.infinera with the correct one.
* Update dictionary.alteon
Feature improvements
* Add support for automated fuzzing. This doesn't affect
normal operations, but it does allow for testing of the
RADIUS decoder.
* Allow tagged attributes to use ":V" as a tag in some cases.
The tag is then read from the value which is being assigned
to the attribute. This functionality is allowed in 'update'
sections, including 'update' in module configurations.
See mods-available/ldap for an example.
* Add kafka module. See mods-available/kafka.
* Allow &control:Packet-SRC-IP-Address to be used when
proxying needs a given source address.
[47 lines not shown]
samba4: updated to 4.24.2
Changes since 4.24.1
* BUG 16038: Samba 4.24 with cups can't get queue and shows errors about
fetch_share_cache_time
* BUG 16043: Fix a directory file descriptor leak in vfs_glusterfs that
caused unbounded memory growth on the GlusterFS brick with
persistent SMB2 connections.
* BUG 16030: Windows Offline Files fails with permission error when directory
has the readâonly attribute set
* BUG 15991: samba not triggering mount of zfs snapshot in dataset
.zfs/snapshots/<snapname> directory
* BUG 15999: net ads join still fails with multiple DCs
* BUG 16076: samba-tool shows wrong format specifiers for timestamp
attributes
* BUG 14638: restrict anonymous = 2 breaks RODC functionality
* BUG 15973: smbpasswd can crash winbindd on an AD DC
* BUG 15995: smbd does not cleanup on disconnect of the transport connection
on lease break errors
[9 lines not shown]
qtcreator: updated to 19.0.1
Qt Creator version 19.0.1 contains bug fixes.
General
Fixed
* That preferences for newly enabled plugins were only available after restart
* Various issues with marking the `Preferences` as dirty
* A possible crash when opening the `About Qt Creator` dialog multiple times
* That using the keyboard shortcut for `Advanced Find` did not raise the search
widget
* Model Context Protocol
* A crash when using the `quit` action
Editing
Fixed
[16 lines not shown]
gsed: update to 4.10.
* Noteworthy changes in release 4.10 (2026-04-21) [stable]
** Bug fixes
sed 's/a/b/g' (and other global substitutions) now works on input
lines longer than 2GB. Previously, matches beyond the 2^31 byte offset
would evoke a "panic" (exit 4).
[bug present since the beginning]
'sed --follow-symlinks -i' no longer has a TOCTOU race that could let
an attacker swap a symlink between resolution and open, causing sed to
read attacker-chosen content and write it to the original target.
[bug introduced in sed 4.1e]
sed no longer falsely matches when back-references are combined with
optional groups (.?) and the $ anchor. For example, this no longer
falsely matches the empty string at beginning of line:
[49 lines not shown]
nist_hash_drbg: Fix citation to standard.
- Note that it's Rev. 1.
- Provide a URL.
- Link also to the test vectors.
- And link to an archive of the test vectors, just in case.
virtio(4): Allow virtio 0.9 BAR0 type to be memory rather than I/O.
This matches virtio>=1.0, and can't break working `hardware': any
existing virtio devices that worked must have reported I/O-type BAR0,
so they will continue to work; this will only enable previously
unusable virtio devices, reporting memory-type BAR0, to work.
Patch from Petri Koistinen.
PR kern/60247: virtio(4): legacy attach fails when BAR0 is MMIO
