lighttpd: update to 1.4.83. Changes:
Highlights
- add PQC hybrid KEM X25519MLKEM768 to default TLS groups
- mod_sockproxy can now route connections based on TLS SNI
- mod_proxy proxy.header enhanced config for url-path mapping of response headers
- HTTP Incremental header support
- portability/compatibility with library updates (lighttpd dependencies)
BEHAVIOR CHANGES
- add PQC hybrid KEM X25519MLKEM768 to default TLS groups
- HTTP/1.1 Upgrade: h2c has been deprecated; set default to disabled
in lighttpd, but can still be enabled in config, and http2 prior
knowledge is still enabled
* [systemd] add RestrictAddressFamilies AF_NETLINK
* [TLS] skip cert_is_active warnings for unset clock
[102 lines not shown]
filesystems/py-fuse-bindings: Change back to egg.mk to accomodate unmaintained fuse filesystems
wheel.mk does not allow 2.7 and there are 3 2.7-only filesystems
still. While they are probably ripe for removal, I don't want to
couple that.
Tested with python 3.13 and bup.
Update to john-jumbo to bleeding-jumbo as of 20260613
Move from the 1.8.0-jumbo-1 release to the bleeding-jumbo development
branch, which tracks ongoing jumbo development past 1.9.0-jumbo-1
(May 2019) -- ~4.5 years and 6000+ jumbo commits beyond 1.8.0-jumbo-1.
Notable changes since 1.8.0-jumbo-1:
- New 1.9.0 core base; bcrypt interleaving on x86-64 raised 2x -> 3x
for a major speedup on CPUs without SMT
- Extended bitslice DES with more SIMD sets: AVX2, AVX-512 (incl.
2nd-gen Xeon Phi) and MIC (1st-gen Xeon Phi) on x86(-64); ASIMD
on Aarch64
- AVX-512 ternary-logic (3-input LUT) DES S-box expressions, also
used via OpenCL on NVIDIA Maxwell and above
- FPGA support for 7 hash types on ZTEX 1.15y boards
- Many new format/hash types, OpenCL improvements, bugfixes and
portability updates
Full release notes at https://www.openwall.com/lists/announce/2019/05/14/1
netpbm: Various build fixes.
Firstly, this fails to build with a compiler that defaults to C23,
due to "old-style function definitions" in getopt.c. So force it to
build with the gnu89 standard.
Secondly, we want to force all function definitions to be visible.
They hardcore XOPEN_SOURCE all over the codebase, so we need to
override their decision. This eliminates the need to compile with
-Wno-implicit-function-declaration.
Why do we want to avoid doing that? Because older GCC versions error
when they encounter a warning flag that they don't support, and that
is one of them that GCC 4.x does not support.
