Commit fixes provided by Chuck Cranor, thank you very much.
The fixes correct color handling glitches which were the result of
the terminal colour incorrectly being reset to the original pair not
the default color that had been set.
prusaslicer: update to 2.9.7
Changes with respect to 2.9.6.
* Fixed an out-of-bounds write when loading a 3MF with a negative bed index.
* Fixed a stack buffer overflow in the digits() / zdigits() placeholder
functions.
* Fixed several issues in the downloader from Printables.
* Fixed couple of potencionally exploitable vulnerabilities in libbgcode
library when loading malformed binary G-code files.
Install the manhtml obsolete set.
While here, remove some files from it that are not actually obsolete,
but in the comp set.
I don't understand the logic for putting files in one or the other,
someone who does: please review them.
p5-SQL-Abstract: update to 2.000003.
2.000003 - 2026-11-06
- SECURITY, CVE-2026-121265: generate() (and so AUTOLOAD with
allow_autoload) also treats an arrayref in its hashref or arrayref
as one bind value. 2.000002 fixed only insert(), update() and
values(): generate('update t', { name => [ "(SELECT ...)" ] })
still gave UPDATE T SET name = (SELECT ...). \[ $sql, @bind ] is
literal SQL in generate() too; array_datatypes => 0 restores the
old behaviour.
- every module has a $VERSION, the same as SQL::Abstract
2.000002 - 2026-11-05
- SECURITY, CVE-2026-121265: array_datatypes is on by default, so an
arrayref as a column value in insert() or update() (and values())
is one bind value. Before, it was literal SQL and its first element
went into the SQL text: a JSON array or a repeated form field like
{ name => [ "x, is_admin = 1" ] } gave
UPDATE t SET name = x, is_admin = 1. Literal SQL is
[170 lines not shown]
qt6: update comment
qt6 needs recursive bumps for _every_ version change, not only major
versions, otherwise we see
/usr/pkg/qt6/lib/libQt6Svg.so.6: Undefined PLT symbol "_ZN14QObjectPrivateC2E16QtPrivate_6_11_2" (symnum = 958)
Pass a number of bpf_insn to npf_bpf_compile, this should fix kern/60975.
Contrary to what the PR says, it broke loudly only in -current
when I tightened checks in bpfjit_generate_code on July 5th, 2026.
In stable releases it reads past the end of allocations but it generates
valid jitted code.
Why it works in stable releases:
- bpf_validate() checks that a rule ends with a valid RET and
that jumps don't jump past the last RET,
- bpfjit in stable releases doesn't check for a valid RET, it
relies on bpf_validate().
- bpfjit starts by (over)allocating a shadow bpfjit_insn array,
then scans (and goes past the end) instructions, builds CFG
and sets the "unreachable" flag in the shadow array. All
instructions after the last RET have unreachable set to true.
- bpfjit skips emitting any code when unreachable is true
[5 lines not shown]
Use proper naming for registering ether filtering hooks
get_etherpfil_head function name doesn't make sense in that context.
use register_etherpfil_hooks (plural) which registers one hook
(by calling the singular form (register_etherpfil_hook)
per interface at the ether layer.
No functional change intended
Thanks Edgar Fub
