Adolf Belka [Wed, 12 Mar 2025 11:03:22 +0000 (12:03 +0100)]
sources: Update ipblocklist with Threatview.io IP list
- Blocklist addition was discussed and agreed at IPFire dev conf call in March 2025.
- Tested on vm system.
- Adjusted the entry alignment for the three 3coresec entries as they had used tabs and
all the rest used spaces for alignment. Now all entries are lined up the same.
Tested-by: Adolf Belka <adolf.belka@ipfire.org> Signed-off-by: Adolf Belka <adolf.belka@ipfire.org> Signed-off-by: Michael Tremer <michael.tremer@ipfire.org>
Adolf Belka [Wed, 12 Mar 2025 14:46:10 +0000 (15:46 +0100)]
ipblocklist-functions.pl: Specify an IPFire user agent for the downloads
- As discussed at the IPFire conf call in March 2025, this patch provides an IPFire
specific User Agent string for the IP Block Lists downloads using LWP::UserAgent.
- It turned out that there was already a function in general-functions.pl that creates
an IPFire Useer Agent string. This was used for this IP Blocklist download.
- Currently it gave me the string IPFire/2.29/192.
- This was tested out with the Threatview.io IP blocklist download and it worked fine.
- If this patch is approved and merged then I will let contact Threatview.io to let them
know what our User Agent string is.
Tested-by: Adolf Belka <adolf.belka@ipfire.org> Signed-off-by: Adolf Belka <adolf.belka@ipfire.org> Signed-off-by: Michael Tremer <michael.tremer@ipfire.org>
Adolf Belka [Sat, 15 Mar 2025 20:45:31 +0000 (21:45 +0100)]
perl: uncomment the json entrries in the rootfile
- Back in Sept 2024 I supplied a patch to remove certain perl modules as they were now
available in the core perl package.
- The perl-json was one of these modules but unfortunately I missed to uncomment the json
entries in the perl rootfile so they have been unavailable to samba since then.
- This patch corrects that situation.
Suggested-by: ummeegge <ummeegge@ipfire.org> Signed-off-by: Adolf Belka <adolf.belka@ipfire.org> Signed-off-by: Michael Tremer <michael.tremer@ipfire.org>
Adolf Belka [Sat, 15 Mar 2025 12:29:26 +0000 (13:29 +0100)]
expat: Update to version 2.7.0
- Update from version 2.6.4 to 2.7.0
- Update of rootfile
- Fix for CVE-2024-8176
- Changelog
2.7.0
Security fixes:
#893 #973 CVE-2024-8176 -- Fix crash from chaining a large number
of entities caused by stack overflow by resolving use of
recursion, for all three uses of entities:
- general entities in character data ("<e>&g1;</e>")
- general entities in attribute values ("<e k1='&g1;'/>")
- parameter entities ("%p1;")
Known impact is (reliable and easy) denial of service:
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H/E:H/RL:O/RC:C
(Base Score: 7.5, Temporal Score: 7.2)
Please note that a layer of compression around XML can
significantly reduce the minimum attack payload size.
Other changes:
#935 #937 Autotools: Make generated CMake files look for
libexpat.@SO_MAJOR@.dylib on macOS
#925 Autotools: Sync CMake templates with CMake 3.29
#945 #962 #966 CMake: Drop support for CMake <3.13
#942 CMake: Small fuzzing related improvements
#921 docs: Add missing documentation of error code
XML_ERROR_NOT_STARTED that was introduced with 2.6.4
#941 docs: Document need for C++11 compiler for use from C++
#959 tests/benchmark: Fix a (harmless) TOCTTOU
#944 Windows: Fix installer target location of file xmlwf.xml
for CMake
#953 Windows: Address warning -Wunknown-warning-option
about -Wno-pedantic-ms-format from LLVM MinGW
#971 Address Cppcheck warnings
#969 #970 Mass-migrate links from http:// to https://
#947 #958 ..
#974 #975 Document changes since the previous release
#974 #975 Version info bumped from 11:0:10 (libexpat*.so.1.10.0)
to 11:1:10 (libexpat*.so.1.10.1); see https://verbump.de/
for what these numbers do
Infrastructure:
#926 tests: Increase robustness
#927 #932 ..
#930 #933 tests: Increase test coverage
#617 #950 ..
#951 #952 ..
#954 #955 .. Fuzzing: Add new fuzzer "xml_lpm_fuzzer" based on
#961 Google's libprotobuf-mutator ("LPM")
#957 Fuzzing|CI: Start producing fuzzing code coverage reports
#936 CI: Pass -q -q for LCOV >=2.1 in coverage.sh
#942 CI: Small fuzzing related improvements
#139 #203 ..
#791 #946 CI: Make GitHub Actions build using MSVC on Windows and
produce 32bit and 64bit Windows binaries
#956 CI: Get off of about-to-be-removed Ubuntu 20.04
#960 #964 CI: Start uploading to Coverity Scan for static analysis
#972 CI: Stop loading DTD from the internet to address flaky CI
#971 CI: Adapt to breaking changes in Cppcheck
Signed-off-by: Adolf Belka <adolf.belka@ipfire.org> Signed-off-by: Michael Tremer <michael.tremer@ipfire.org>
Adolf Belka [Tue, 11 Mar 2025 16:36:17 +0000 (17:36 +0100)]
libloc: Update to version 0.9.18
- Update libloc from version 0.9.17 to 0.9.18
- Update of rootfile
- Update of patch to revert installing of perl files into perl vendor directory as source
file has changed enough.
- Changelog
0.9.18
* A new Lua module has been added as announced here:
https://www.ipfire.org/blog/ipfire-location-lua-bindings-for-fun-and-profit
* The algorithm to detect bogons and duplicates in the tree have massively been
improved and should be nearing their theoretical maximum in terms of
performance.
* A large number of stability and correctness fixes have been rolled out. These
mostly affect the code generating the database.
* We now have a small Jenkins pipeline which will check if the library still
builds for a couple of major Linux distributions and various architectures.
Python:
* AS and Country objects are now hashable and support rich comparison operations
Importer:
* Exporting the database is around 200x faster due to eliminating any excessive
joins. Instead a new temporary table will be created and a temporary index
will be used to apply various updates to the data from various sources inside
the database. That allows us to create the export iteratively instead of
having one large query that runs for forever. An export that formerly took
around 17-20 hrs(!) will now take only ~5 mins.
* A new source for human-friendly names for Autonomous Systems registered with
ARIN has been added
* Importing feeds from AWS and Spamhaus has been split off into separate
database tables. This will allow us to import them separately and prioritise
our own rewrites over them.
* The ARIN parser has been refactored based on csv.DictReader(), parsers for
the AWS and Spamhaus feeds have been rewritten, too
* Geofeeds are now fetched concurrently with a unified downloader
* Certain country codes will be entirely ignored. Currently this is YU for
former Yugoslavia and ZZ which is used to say “no country”
* Country codes can now be corrected on the fly. This is used to change UK to
GB as only the latter is the valid country code for the United Kingdom.
* Countries that are not on our list will not be imported any more.
* Networks larger than /4 for IPv6, and /10 for IPv4 won’t be imported any
more. This avoids that we propagate any issues in the global routing table
into the database.
Signed-off-by: Adolf Belka <adolf.belka@ipfire.org> Signed-off-by: Michael Tremer <michael.tremer@ipfire.org>
Matthias Fischer [Tue, 11 Mar 2025 15:28:31 +0000 (16:28 +0100)]
htop: Update to 3.4.0
For details see:
https://github.com/htop-dev/htop/blob/main/ChangeLog
"What's new in version 3.4.0
* More expressive version tag generated for development versions (htop --version, help screen)
* Improve Darwin support for ARM-based systems
* Fix static linking with libsystemd
* Various build fixes for DragonFlyBSD, Darwin, NetBSD, OpenBSD & Solaris
* Fix running task display (count)
* Fix sort order handling in tree mode
* Add warning when exiting with a signal (not saving .htoprc)
* Add Disk I/O and Network I/O meter for DragonFlyBSD
* Improve handling of invalid Unicode strings
* Disable basename checking for kernel tasks
* Updated documentation for pcp-htop
* Disable FOCUS_IN/FOCUS_OUT event handling
* Add GPU meter for Linux and PCP
* Add colum for GPU time per process on Linux and PCP
* Avoid glibc FILE API voodoo
* Ignore previously unhandled signals USR1 and USR2
* Force locating the config file to only use absolute paths
* Prefer reading htoprc from ~/.config/htop/htoprc over legacy ~/.htoprc
* Force writing the configuration to a regular file
* Use distinct config files for htop and pcp-htop
* Link libnl3 at runtime
* Gather permitted capabilities via capget(2)
* Avoid fetching certain process information for each thread on Linux (speed up)
* Improved handling for invalid data in /proc/tty/drivers on Linux
* Various changes to avoid memory allocations inside signal handlers
* Add single column header layout
* Fix DivByZero bug on startup on Darwin
* Include thread information on Darwin
* Show process state on Darwin
* Update compat check for C23 compilers
* Improved detail in help screen
* Unicode support for CGROUP, CCGROUP, CONTAINER and SECATTR columns
* Mark newline characters in the process command line display
* Resolve nested derived metrics for PCP
* Make supported modes/styles specific to each meter
* Refined checks for terminals supporting to redefine keys
* Fix handling of the NICE value on FreeBSD
* Fix display of CPU utilization on FreeBSD
* Honour update interval adjustments properly without restart
* Force rebuild of display table after item removals
* Reworked handling for various temperature sensors
* Fix high CPU load when the strace'd process exits prematurely
* Document --drop-capabilities to require a compile time support
* Always call PKG_PROG_PKG_CONFIG in configure
* Make configure warn when pkg.m4 is absent
* Rewrite curses/terminfo detection code in configure
* Keep following a process when resuming process updates (Z key)
* Normalize Disk I/O usage and allow utilization above 100%
* Plug several memory leaks and improve performance for information parsing
* Allow to show or hide cache and buffers in memory usage meter
* Visibility hint and UX improvements in status bar of display options panel
* Remove IOKit / IOMainPort / IOMMasterPort logic for Darwin builds
* Replace BCC with metrics from BPF for pcp-htop"
Signed-off-by: Matthias Fischer <matthias.fischer@ipfire.org> Signed-off-by: Michael Tremer <michael.tremer@ipfire.org>
Adolf Belka [Thu, 6 Mar 2025 11:32:21 +0000 (12:32 +0100)]
en.pl: Update the wording for the check on the CA Name for upload
- This changes the wording to allowing characters and spaces.
Fixes: Bug10595 part 2 Tested-by: Adolf Belka <adolf.belka@ipfire.org> Signed-off-by: Adolf Belka <adolf.belka@ipfire.org> Signed-off-by: Michael Tremer <michael.tremer@ipfire.org>
Adolf Belka [Thu, 6 Mar 2025 11:32:20 +0000 (12:32 +0100)]
vpnmain.cgi: Fix for 2nd part of bug10595
- Bug10595 had two parts in it and was closed after the first part was fixed. The second
part was still unfixed at that time. I cam across it when checking out an open bug on
a similar issue with OpenVPN.
- I found the section that checks on the CA Name and modified it to also allow spaces.
- Having modified that then the subroutines getsubjectfromcert and getCNfromcert required
modifications otherwise the openssl statement only got a filename with the first
portion of the ca name until the first space was encountered. This v2 version of this
patch set has the safe approach suggested by @Michael. This v3 version has been
re based to another patch submission that modified lines in a similar place and
prevented a merge to work.
- I am open to any suggestions for improvements to how I implemented the use of the
&General::system_output function
- Tested this change out on my vm and it worked fine. I was able to upload a ca
certificate into IPSec and use spaces in the CA Name.
- Changed the test for the CA_NAME to allow spaces. Change also made to en.pl file
Fixes: Bug10595 part 2 Tested-by: Adolf Belka <adolf.belka@ipfire.org> Signed-off-by: Adolf Belka <adolf.belka@ipfire.org> Signed-off-by: Michael Tremer <michael.tremer@ipfire.org>
Adolf Belka [Sun, 9 Mar 2025 14:12:04 +0000 (15:12 +0100)]
language files: Update to include a message about a double quotation mark
Fixes: bug12298 Tested-by: Adolf Belka <adolf.belka@ipfire.org> Signed-off-by: Adolf Belka <adolf.belka@ipfire.org> Signed-off-by: Michael Tremer <michael.tremer@ipfire.org>
Adolf Belka [Sun, 9 Mar 2025 14:12:03 +0000 (15:12 +0100)]
vpnmain.cgi: Fixes bug12298 - IPSec password cannot use semicolon
- The password for the pkcs12 certificate is passed to the open ssl command via $opt but
it is not quoted and so the ; is taken as the end of the command rather than as part
of the password. This also means that a pkcs12 file is not created and the .pem
intermediate file is what is left in the directory.
- This patch makes the -passout option quoted in the same way as the -name and -caname
options.
- Based on being the same as the name and caname parts in $opt, I believe that this should
not give rise to a vulnerability but I am open to being corrected.
- By quoting the -passout then the password must not contain double quotation marks, ",
so a test for the password containing a " has been added.
- The message about the use of the double quotation mark has been added to the english,
dutch and german language files. Feel free to correct if what I have used is not
correct. Those are in the other patch of this patch set.
- Tested out on my testbed system. I was able to create a pkcs12 certificate with a
password containing a variety of characters, including the semicolon, and getting
a message that the password contains a double quotation mark when I used that.
Fixes: bug12298 Tested-by: Adolf Belka <adolf.belka@ipfire.org> Signed-off-by: Adolf Belka <adolf.belka@ipfire.org> Signed-off-by: Michael Tremer <michael.tremer@ipfire.org>
Adolf Belka [Sun, 2 Mar 2025 19:14:31 +0000 (20:14 +0100)]
vpnmain.cgi: Change the log name from "ipsec" to "charon"
- The use of "ipsec" currently means that none of these messages are shown in the
system log with IPSec selected as that is looking for charon.
- This patch changes all "ipsec" entries in this file to "charon"
- This results in the log messages for generation and regeneration of the root/host
certificate set being shown in the system log. Without this then the messages log
has to be searched from the command line with grep.
- Tested out on a physical IPFire system.
Tested-by: Adolf Belka <adolf.belka@ipfire.org> Signed-off-by: Adolf Belka <adolf.belka@ipfire.org> Signed-off-by: Michael Tremer <michael.tremer@ipfire.org>
Adolf Belka [Sun, 2 Mar 2025 19:14:30 +0000 (20:14 +0100)]
vpnmain.cgi: Fixes bug13737 - increments the serial number to allow cert regen
- When the regeneration is carried out the existing cert, with serial number 01, is
revoked but when the new cert is created the serial number is still 01 causing error
messages about the new cert being revoked.
- This patch increments the serial number from 01 to 02 after the initial root/host
certificate set is created.
- Then when the olf cert is revoked the new one uses serial number 02 but also
automatically increments it again. So all future regenerations work without problems.
- Tested out on a physical IPFire system.
Fixes: bug13737 Tested-by: Adolf Belka <adolf.belka@ipfire.org> Signed-off-by: Adolf Belka <adolf.belka@ipfire.org> Signed-off-by: Michael Tremer <michael.tremer@ipfire.org>
Adolf Belka [Sat, 1 Mar 2025 12:46:02 +0000 (13:46 +0100)]
exclude: Remove the urlfilter pl programs from a backup
- When dealing with the qos bug fix for backing up .pl programs I also then searched all
the /var/ipfire directory tree looking for any other .pl files that were being backed
up and found that there were two for the urlfilter.
- This patch adds the .pl files in the urlfilter/bin directory to the exclude list.
- In the same way as for the qos change the exclude addition also means that these files
will not be restorewd from any earlier backup.
- Also tested and confirmed on a physical IPFire system.
Tested-by: Adolf Belka <adolf.belka@ipfire.org> Signed-off-by: Adolf Belka <adolf.belka@ipfire.org> Signed-off-by: Michael Tremer <michael.tremer@ipfire.org>
Adolf Belka [Sat, 1 Mar 2025 12:46:01 +0000 (13:46 +0100)]
exclude: Fix bug13736 - stop backup of qos perl programs
- The exclude file only had the qos.pl file from the bin directory excluded from the
backup. This meant that 5 other perl programs were being backed up and therefore
any restore would overwrite new updated versions such as the makeqosscripts.pl file.
- This addition to the backup exclude file now excludes all .pl files from the qos/bin
directory.
- This also means that any restore from earlier backups that included the other .pl files
will not restore thosde files.
- Tested out on an IPFire physical system.
Fixes: bug13736 Tested-by: Adolf Belka <adolf.belka@ipfire.org> Signed-off-by: Adolf Belka <adolf.belka@ipfire.org> Signed-off-by: Michael Tremer <michael.tremer@ipfire.org>
Adolf Belka [Sat, 1 Mar 2025 12:01:08 +0000 (13:01 +0100)]
samba: Update to version 4.21.4
- Update from version 4.21.3 to 4.21.4
- Update of rootfiles for x86_64, aarch64 and riscv64
- Changelog
4.21.4
* BUG 15780: Increasing slowness of sharesec performance with high number of
registry shares.
* BUG 15782: winbindd shows memleak in kerberos_decode_pac.
* BUG 15738: Creation of GPOs applicable to more than one group is impossible
with Samba 4.20.0 and later.
* BUG 15756: Replace `crypt` module in
python/samba/netcmd/user/readpasswords/common.py.
* BUG 15151: vfs_gpfs silently garbles timestamps > year 2106.
* BUG 15796: Spotlight search results don't show file size and creation date.
* BUG 15703: General improvements for vfs_ceph_new module.
* BUG 15777: net offlinejoin not working correctly.
* BUG 15780: Increasing slowness of sharesec performance with high number of
registry shares.
* BUG 15759: net ads create/join/winbind producing unix dysfunctional
keytabs.
* BUG 14213: Windows Explorer crashes on S-1-22-* Unix-SIDs when accessing
security tab.
* BUG 15769: The values from hresult_errstr_const and hresult_errstr are
reversed in 4.20 and 4.21.
* BUG 15778: Kerberos referral tickets are generated for principals in our
domain if we have a trust to a top level domain.
* BUG 15783: NETLOGON_NTLMV2_ENABLED is missing in the SamLogon* user_flags
field.
* BUG 15703: General improvements for vfs_ceph_new module.
* BUG 15784: Regression: stack-use-after-return in crypt_as_best_we_can().
* BUG 15788: libreplace:readline: gcc 15 complains about incompatible pointer
types.
* BUG 15703: General improvements for vfs_ceph_new module.
* BUG 15703: General improvements for vfs_ceph_new module.
Signed-off-by: Adolf Belka <adolf.belka@ipfire.org> Signed-off-by: Michael Tremer <michael.tremer@ipfire.org>
Adolf Belka [Fri, 28 Feb 2025 16:59:46 +0000 (17:59 +0100)]
tcl: Update to version 9.0.1
- Update from version 8.6.14 to 9.0.1
- Update of rootfile
- Changelog
9.0.1
# Completed 9.0 Features and Interfaces
- [TIP 701 - Tcl_FSTildeExpand C API]
(https://core.tcl-lang.org/tips/doc/trunk/tip/701.md)
- [TIP 707 - ptrAndSize internal rep in Tcl_Obj]
(https://core.tcl-lang.org/tips/doc/trunk/tip/707.md)
- [Size modifiers j, q, z, t not implemented]
( https://core.tcl-lang.org/tcl/info/c4f365)
# Bug fixes
- [regression in tzdata, %z instead of offset TZ-name]
(https://core.tcl-lang.org/tcl/tktview/2c237b)
- [Tcl will not start properly if there is an init.tcl file in the current
dir](https://core.tcl-lang.org/tcl/tktview/43c94f)
- [clock scan "24:00", ISO-8601 compatibility]
(https://core.tcl-lang.org/tcl/tktview/aee9f2)
- [Temporary folder with file "tcl9registry13.dll" remains after "exit"]
(https://core.tcl-lang.org/tcl/tktview/6ce3c0)
- [Wrong result by "lsearch -stride -subindices -inline -all"]
(https://core.tcl-lang.org/tcl/info/5a1aaa)
- [TIP 609 - required Tcl_ThreadAlert() skipped with nested event loop]
(https://core.tcl-lang.org/tcl/info/c7e4c4)
- [buffer overwrite for non-BMP characters in utf-16]
(https://core.tcl-lang.org/tcl/tktview/66da4d)
- [zipfs info on mountpoint of executable returns zero offset in field 4"]
(https://core.tcl-lang.org/tcl/info/aaa84f)
- [zlib-8.8, zlib-8.16 fail on Fedora 40, gcc 14.1.1]
(https://core.tcl-lang.org/tcl/tktview/73d5cb)
- [install registry and dde in $INSTALL_DIR\lib always]
(https://core.tcl-lang.org/tcl/tktview/364bd9)
- [cannot build .chm help file (Windows)]
(https://core.tcl-lang.org/tcl/tktview/bb110c)
# Incompatibilities
- No known incompatibilities with the Tcl 9.0.0 public interface.
# Updated bundled packages, libraries, standards, data
- Itcl 4.3.2
- sqlite3 3.47.2
- Thread 3.0.1
- TDBC\* 1.1.10
- tcltest 2.5.9
- tzdata 2024b, corrected
9.0.0
# Major Features
## 64-bit capacity: Data values larger than 2 GB
- Strings can be any length (that fits in your available memory)
- Lists and dictionaries can have very large numbers of elements
## Internationalization of text
- Full Unicode range of codepoints
- New encodings: `utf-16`/`utf-32`/`ucs-2`(`le`|`be`), `CESU-8`, etc.
- `encoding` options `-profile`, `-failindex` manage encoding of I/O.
- `msgcat` supports custom locale search list
- `source` defaults to `-encoding utf-8`
## Zip filesystems and attached archives
- Packaging of the Tcl script library with the Tcl binary library,
meaning that the `TCL_LIBRARY` environment variable is usually not
required.
- Packaging of an application into a virtual filesystem is now a
supported
core Tcl feature.
## Unix notifiers available using `epoll()` or `kqueue()`
- This relieves limits on file descriptors imposed by legacy
`select()` and fixes a performance bottleneck.
# Incompatibilities
## Notable incompatibilities
- Unqualified varnames resolved in current namespace, not global.
Note that in almost all cases where this causes a change, the
change is actually the removal of a latent bug.
- No `--disable-threads` build option. Always thread-enabled.
- I/O malencoding default response: raise error (`-profile strict`)
- Windows platform needs Windows 7 or Windows Server 2008 R2 or later
- Ended interpretation of `~` as home directory in pathnames.
(See `file home` and `file tildeexpand` for replacements when you
need them.)
- Removed the `identity` encoding.
(There were only ever very few valid use cases for this; almost
all uses were systematically wrong.)
- Removed the encoding alias `binary` to `iso8859-1`.
- `$::tcl_precision` no longer controls string generation of doubles.
(If you need a particular precision, use `format`.)
- Removed pre-Tcl 8 legacies: `case`, `puts` and `read` variant
syntaxes.
- Removed subcommands [`trace variable`|`vdelete`|`vinfo`]
- Removed `-eofchar` option for write channels.
- On Windows 10+ (Version 1903 or higher), system encoding is always
utf-8.
- `%b`/`%d`/`%o`/`%x` format modifiers (without size modifier) for
`format` and `scan` always truncate to 32-bits on all platforms.
- `%L` size modifier for `scan` no longer truncates to 64-bit.
- Removed command `::tcl::unsupported::inject`.
(See `coroinject` and `coroprobe` for supported commands with
significantly more comprehensible semantics.)
## Incompatibilities in C public interface
- Extensions built against Tcl 8.6 and before will not work with
Tcl 9.0;
ABI compatibility was a non-goal for 9.0. In _most_ cases,
rebuilding against Tcl 9.0 should work except when a removed API
function is used.
- Many arguments expanded type from `int` to `Tcl_Size`, a signed
integer type large enough to support 64-bit sized memory objects.
The constant `TCL_AUTO_LENGTH` is a value of that type that
indicates that the length should be obtained using an appropriate
function (typically `strlen()` for `char *` values).
- Ended support for `Tcl_ChannelTypeVersion` less than 5
- Introduced versioning of the `Tcl_ObjType` struct
- Removed macros `CONST*`: Tcl 9 support means dropping Tcl 8.3
support.
(Replaced with standard C `const` keyword going forward.)
- Removed registration of several `Tcl_ObjType`s.
- Removed API functions:
- `Tcl_Backslash()`
- `Tcl_*VA()`
- `Tcl_*MathFunc*()`
- `Tcl_MakeSafe()`
- `Tcl_(Save|Restore|Discard|Free)Result()`
- `Tcl_EvalTokens()`
- `Tcl_(Get|Set)DefaultEncodingDir()`
- `Tcl_UniCharN(case)cmp()`
- `Tcl_UniCharCaseMatch()`
- Revised many internals; beware reliance on undocumented behaviors.
# New Features
## New commands
- `array default` — Specify default values for arrays (note that
this alters the behaviour of `append`, `incr`, `lappend`).
- `array for` — Cheap iteration over an array's contents.
- `chan isbinary` — Test if a channel is configured to work with
binary data.
- `coroinject`, `coroprobe` — Interact with paused coroutines.
- `clock add weekdays` — Clock arithmetic with week days.
- `const`, `info const*` — Commands for defining constants (variables
that can't be modified).
- `dict getwithdefault` — Define a fallback value to use when
`dict get` would otherwise fail.
- `file home` — Get the user home directory.
- `file tempdir` — Create a temporary directory.
- `file tildeexpand` — Expand a file path containing a `~`.
- `info commandtype` — Introspection for the kinds of commands.
- `ledit` — Equivalent to `lreplace` but on a list in a variable.
- `lpop` — Remove an item from a list in a variable.
- `lremove` — Remove a sublist from a list in a variable.
- `lseq` — Generate a list of numbers in a sequence.
- `package files` — Describe the contents of a package.
- `string insert` — Insert a string as a substring of another string.
- `string is dict` — Test whether a string is a dictionary.
- `tcl::process` — Commands for working with subprocesses.
- `*::build-info` — Obtain information about the build of Tcl.
- `readFile`, `writeFile`, `foreachLine` — Simple procedures for
basic working with files.
- `tcl::idna::*` — Commands for working with encoded DNS names.
## New command options
- `chan configure ... -inputmode ...` — Support for raw terminal
input and reading passwords.
- `clock scan ... -validate ...`
- `info loaded ... ?prefix?`
- `lsearch ... -stride ...` — Search a list by groups of items.
- `regsub ... -command ...` — Generate the replacement for a regular
expression by calling a command.
- `socket ... -nodelay ... -keepalive ...`
- `vwait` controlled by several new options
- `expr` string comparators `lt`, `gt`, `le`, `ge`
- `expr` supports comments inside expressions
## Numbers
- <code>0<i>NNN</i></code> format is no longer octal interpretation.
Use <code>0o<i>NNN</i></code>.
- <code>0d<i>NNNN</i></code> format to compel decimal interpretation.
- <code>NN_NNN_NNN</code>, underscores in numbers for optional
readability
- Functions: `isinf()`, `isnan()`, `isnormal()`, `issubnormal()`,
`isunordered()`
- Command: `fpclassify`
- Function `int()` no longer truncates to word size
## TclOO facilities
- private variables and methods
- class variables and methods
- abstract and singleton classes
- configurable properties
- `method -export`, `method -unexport`
8.6.16
Bug fixes and corrections to erratic behavior
* Regression in [clock] timezones due to revised tzdata format
* Improper startup if [pwd] contains a file named init.tcl
* Fix crashes or hangs in...
- TclOO + coroutine, oo-1.25
- lifecycle management of the attributes of a menu entry
- [grid] and [pack] handling of half-dead argument
- Tk_DeleteErrorHandler()
- overwrite of thread data by Tk initialization in second interp
* Prevent negative zlib stream checksums, zlib-15.1
* Filesystem path efficiency from skipping unnecessary normalization
* Revised [clock scan] consistent with leap second timestamp validation
* Updated bundled packages, libraries, standards, data
- Itcl 4.3.2
- sqlite3 3.47.2
- Thread 2.8.11
- TDBC* 1.1.10
- tcltest 2.5.9
- tzdata 2024b, corrected
8.6.15
Bug fixes and corrections to erratic behavior
* [TIP 692] Deprecate Tcl_GetAlias(). Migrate to Tcl_GetAliasObj()
* Invoke binding scripts for events with detail field NotifyInferior
*** POTENTIAL INCOMPATIBILITY ***
* Tcl_NewObjectInstance() errors on namespace re-use.
*** POTENTIAL INCOMPATIBILITY -- breaks Itcl 4.2 ***
* TCL_PACKAGE_PATH change from Tcl list to platform path convention
*** POTENTIAL INCOMPATIBILITY ***
* Make [self] work inside [$obj eval]
* Fix [$obj varname] for linked varnames
* Restore access to alternate data streams (ADS) in NTFS filesystems.
* Fix crashes or hangs in...
- TclOO + coroutine, oo-22.[34]
- entangled destructor and namespace deletion, oo-35.7.*
- destruction of reflected channel, iocmd-32.3.*
- select notifier with file descriptor >= FD_SETSIZE
- [child invokehidden info frame], info-40.0
- [focus -force], focus-8.1
- [$canvas dchars], canvas-11.4
- [$menubutton destroy]
* Appearance improvements for...
- focus ring, arrows, and classic theme.
- last item in a [ttk::treeview].
- down arrow in [ttk::combobox].
* Repair [$photo read -from] flaws in GIF,PNG formats. imgPhoto-19.*
* [$photo copy] coordinate check error. See imgPhoto-12.5
* Detect corrupt GIF file and raise error. See imgPhoto-18.6.1
* Fixes to [ttk::treeview] subcommands 'see' and 'bbox'.
* Fix default font detection for high DPI
* [treeview identify] now point aware
* Fix broken undo/redo in [text] widget.
* Fix GENFUNC mode of Tcl_ParseArgsObjv(). See tests indexObj-7.*
* Fix removal of oo variable by [info exists]. See oo-19.4
* Fix byte compiled [incr] with wide int increment. See incr-1.31
* Repair encoding flaws in [info hostname] visible for non-ASCII names.
* Fix incorrect [string is control] results on some private codepoints
* Autoload of [::tcl::tm::path]
* Fix missing error message in some [interp limit] failures.
* Improved hash performance for some hash tables.
* Performance optimizations in several encoding primitives.
* Correction to rare failed startup search for system encoding
* Add encodings: koi8-ru, koi8-t
* Add keycodes ISO_Group_Shift and dead_hamza
* Updated bundled packages, libraries, standards, data
- Itcl 4.3.0 -- supports multi-thread operations
- sqlite3 3.45.3
- Thread 2.8.10
- TDBC* 1.1.9
- tcltest 2.5.8
- libtommath 1.3.0
- Unicode 16
- tzdata 2024b
Signed-off-by: Adolf Belka <adolf.belka@ipfire.org> Signed-off-by: Michael Tremer <michael.tremer@ipfire.org>
Adolf Belka [Fri, 28 Feb 2025 14:04:00 +0000 (15:04 +0100)]
dhcpcd: Update to version 10.2.2
- Update from version 10.2.1 to 10.2.2
- Update of rootfile not required
- Changelog is not provided. Details are from the commits from this linlk
https://github.com/NetworkConfiguration/dhcpcd/compare/v10.2.1...v10.2.2
Signed-off-by: Adolf Belka <adolf.belka@ipfire.org> Signed-off-by: Michael Tremer <michael.tremer@ipfire.org>
Adolf Belka [Fri, 28 Feb 2025 11:27:31 +0000 (12:27 +0100)]
firewallog.dat: Fix bug13068 - remove blocklist entries from firewall log
- The blocklist log entries are also under kernel: and so currently also show up in the
firewall logs as well as in the ip blocklist logs menus. If there are a lot of
blocklist entries it can make it very difficult to go through the firewall logs.
- This bugfix excxludes any kernel: log entries that have a chain starting with BLKLST.
- Tested out on physical and vm IPFire systems.
Fixes: bug13068 Tested-by: Adolf Belka <adolf.belka@ipfire.org> Signed-off-by: Adolf Belka <adolf.belka@ipfire.org> Signed-off-by: Michael Tremer <michael.tremer@ipfire.org>
Adolf Belka [Thu, 27 Feb 2025 15:52:48 +0000 (16:52 +0100)]
vim: Update to version 9.1.1153
- Update from version 9.1.0886 to 9.1.1153
- Update of rootfile
- Changelog is not available. Generally each patch version number update is related to
a commit entry in the git repository. The details for all the commit changes can be
found at https://github.com/vim/vim/commits/master/
Signed-off-by: Adolf Belka <adolf.belka@ipfire.org> Signed-off-by: Michael Tremer <michael.tremer@ipfire.org>
Adolf Belka [Thu, 27 Feb 2025 13:27:53 +0000 (14:27 +0100)]
kmod: Update to version 34
- Update from version 33 to 34
- Update of rootfile
- build of kmod has been moved to meson. Autotools option is still available in this
version but in the next version it will only be meson so it seemed sensible to change
it now.
- Back in version 32 they decided to automatically make the symlinks for all the tools
in the install script but to place those symlinks in /bin defined by $bindir. So the
rootfile for version 32 ended up with the tool symlinks both in /bin and /sbin.
- In this version (34) they have decided to change it to being /sbin by default. Distros
that want to have them in /bin just have to set the sbindir to /bin. So the symlink
creation lines are no longer required as the install craetes them for us. The
symlinks in /bin have been removed and I don't see any reason to put them back in as
they were only introduced in version 32 and previously the symlinks were always in
/sbin.
- The sbindir location has to be specified otherwise the deafult would end up with
/usr/sbin
- Changelog
34
- Improvements
- Drop pre-built .ko modules from git - distros/packages will need the
linux-headers to be able to run the testsuite. There was limited use
of the feature, while linters complained about "source-not-included"
or "source-contains-prebuilt-binary".
- Switch build system to meson: autotools is still supported but slated
for removal on next release. This is the transition release to help
distros and integrators to move to the new build system. Default options
target distros while developers can use the build-dev.ini configuration
file.
- Allow to load decompression libraries ondemand: liblzma.so, libz.so,
libxz.so and libzstd.so can now be loaded ondemand, only when there is
such a need. For use during early boot for loading modules, if
configured well it means none of these libraries are loaded: the
module loading logic via finit_module() will just hand over to kernel
the open file descriptor and kernel will use its own decompress routine.
If kernel doesn't handle decompression or if the module is compressed
with a different algorithm than the one configured in the kernel,
libkmod can still open the module by dynamically loading the
correspondent library.
Tools inspecting the module contents, like modinfo, will load that
single decompression library instead all of them.
For distros building with meson it's possible to choose the behavior
per library. Examples: a) -Ddlopen=all uses dlopen behavior for all
the libraries; b) -Ddlopen=xz, will make only xz to be dlopen'ed
while other enabled libraries will be linked in at build time.
The use of dlopen is annotated in the ELF file by using the ELF
Package Metadata spec as documented in
https://systemd.io/ELF_PACKAGE_METADATA/. Example:
$ dlopen-notes.py libkmod.so
# build/libkmod.so
[
{
"feature": "xz",
"description": "Support for uncompressing xz-compressed modules",
"priority": "recommended",
"soname": [
"liblzma.so.5"
]
}
]
- Add -m / --moduledir to depmod to override in runtime the module
directory that was already possible to set on build time. Document
the interaction between the dir options: base, module and output.
- Better error propagation in libkmod for its internal APIs and libc
functions up to the callers.
- Improve libkmod API documentation by adding new sections, documenting
functions previously missing, rewording existing ones, adding version
information, cross-referencing, etc.
- Remove deprecated arguments for depmod: --unresolved-error, --quiet,
--root and --map.
- Remove deprecated arguments for rmmod: -w.
- Remove deprecated arguments for insmod: -p and -s.
- Add --syslog and --force for insmod to normalize it with other tools.
- Add bash, fish and zsh shell-completion for insmod, rmmod and lsmod.
- Remove depmod_module_directory_override from .pc as the kernel side
is not making use of it and will likely not need it.
- Improve builtin module listing and retrieving information from its
modinfo index which reduces the amount of needed syscalls by 90%.
- Improve zstd decompression by using streaming bufferless mode which
reduces the amount of syscalls by 65%.
- Increase use of pread while parsing ELF and indexes in order to reduce
syscalls and improve performance.
- Improve module sorting in depmod to speedup the use of the
modules.order index and support duplicate lines in it.
- Avoid misaligned memory access while reading module signature in
libkmod.
- Add more documentation for contributing to kmod. New developers are
welcome to look at the new README.md and CONTRIBUTING.md files for
information on process, coding style, build/installation, etc.
- Overhaul man pages with multiple clarifications, section rewrites and
additional documentation.
- Drop --with-rootlibdir as it's seldom used and was partially broken.
- Drop strndupa() and alloca() for increased libc compatibility.
- Better handling of LFS for increased compatibility with libc.
- Protect kmod_get_dirname() and kmod_new() against NULL argument.
- Normalize --version / --help output across all tools.
- Always include log priority in messages, even when building with debug.
- Optimize index reading by lazily reading nodes on demand, reducing
FILE overhead and reducing code duplication wrt FILE vs mmap
implementations, etc.
- Switch index to pre-order to improve performance in both read and
write, meaning faster lookup and faster depmod. Some examples:
a) traversing all indexes via configuration dump shows a 9%
improvement on Raspberry Pi 2. b) writing the indexes takes 90% less
lseek() calls, leading to a performance gain of 13%.
- Make symlink install locations more similar to what distros are
using: by default it installs the kmod binary as bin/kmod and the
symlinks are located in e.g. `sbin/depmod -> ../bin/kmod`. Changing
the sbin location is sufficient to move the symlinks to the
appropriate place, so distros using `--sbin /usr/bin` will have them
installed in that directory. This avoids distros having to remove the
symlink and add the symlinks by themselves. (meson only)
- Install configuration directories,
/{etc,usr/lib}/{depmod,modprobe}.d/ as part of installation, matching
what several distros do during packaging. (mson only)
- Bug fixes
- Fix testsuite using when using configurable module dir.
- Fix typos on documentation and source code.
- Fix out of bound access in multiple places when using long paths,
synthetic huge files, or handling memory allocation errors, or
inconsistent variable types, particularly on 32b builds.
- Fix internal array APIs, with better error checking: improve execution on
very memory-constrained scenarios or very long paths.
- Fix absolute path handling in depmod.
- Fix libkmod memory leaks on error handling when getting builtin
module list.
- Do not crash on invalid modules.builtin.modinfo file.
- Fix link with lld resulting in empty testsuite.
- Fix testsuite build/execution with musl.
- Others
- Adopt clang-format and editorconfig for coding style and setup CI
action to keep the codebase consistent.
- Adopt codespell in CI.
- Adopt CodeQL integration in CI.
- Adopt Codecov in CI.
- Adopt SPDX copyright and license identifiers throughout the project.
- Add more distros to CI, 32b builds, clang as compiler and lld as
linker.
- Add support for clang sanitizers and squelch warnings.
- Add tests for builtin modules from modinfo index file.
- Multiple testsuite refactors and fixes to make it simpler to write tests.
- Add CI coverage for docs
- Improve strbuf implementation with more error checks and generalize
it to cover the role of scratchbuf. This allows to remove the
scratchbuf implementation.
- Use common array and strbuf code in depmod to remove duplication.
- Add abstraction and use more compiler builtins for addition and
multiplication with overflow checking.
- Normalize use of C attributes throughout the project.
Signed-off-by: Adolf Belka <adolf.belka@ipfire.org> Signed-off-by: Michael Tremer <michael.tremer@ipfire.org>
Adolf Belka [Wed, 26 Feb 2025 18:12:50 +0000 (19:12 +0100)]
zstd: Update to version 1.5.7
- Update from version 1.5.6 to 1.5.7
- Update of rootfile
- Changelog
1.5.7
fix: compression bug in 32-bit mode associated with long-lasting sessions
api: new method `ZSTD_compressSequencesAndLiterals()` (#4217, #4232)
api: `ZSTD_getFrameHeader()` works on skippable frames (#4228)
perf: substantial compression speed improvements (up to +30%) on small data,
by @TocarIP (#4144) and @cyan4973 (#4165)
perf: improved compression speed (~+5%) for dictionary compression at low
levels (#4170)
perf: much faster speed for `--patch-from` at high compression levels (#4276)
perf: higher `--patch-from` compression ratios, notably at high levels (#4288)
perf: better speed for binaries on Windows (@pps83) and when compiled with
Visual Studio (@MessyHack)
perf: slight compression ratio improvement thanks to better block boundaries
(#4136, #4176, #4178)
perf: slight compression ratio improvement for `dfast`, aka levels 3 and 4 (#4171)
perf: runtime bmi2 detection enabled on x86 32-bit mode (#4251)
cli: multi-threading as default CLI setting, by @daniellerozenblit
cli: new `--max` command (#4290)
build: improve `msbuild` version autodetection, support VS2022, by @ManuelBlanc
build: fix `meson` build by @artem and @Victor-C-Zhang, and on Windows by
@bgilbert
build: compatibility with Apple Framework, by @Treata11
build: improve icc/icx compatibility, by @josepho0918 and @luau-project
build: improve compatibility with Android NDK, by Adenilson Cavalcanti
portability: linux kernel branch, with improved support for Sequence producers
(@embg, @gcabiddu, @cyan4973)
portability: improved qnx compatibility, suggested by @rainbowball
portability: improved install script for FreeBSD, by @sunpoet
portability: fixed test suite compatibility with gnu hurd, by @diegonc
doc: clarify specification, by @elasota
misc: improved tests/decodecorpus validation tool (#4102), by antmicro
Signed-off-by: Adolf Belka <adolf.belka@ipfire.org> Signed-off-by: Michael Tremer <michael.tremer@ipfire.org>
Adolf Belka [Wed, 26 Feb 2025 18:12:49 +0000 (19:12 +0100)]
xfsprogs: Update to version 6.13.0
- Update from version 6.11.0 to 6.13.0
- Update of rootfile
- Changelog is not provided in the source tarball. Detasils can be found from the git log
https://git.kernel.org/pub/scm/fs/xfs/xfsprogs-dev.git/log/
Signed-off-by: Adolf Belka <adolf.belka@ipfire.org> Signed-off-by: Michael Tremer <michael.tremer@ipfire.org>
Adolf Belka [Wed, 26 Feb 2025 18:12:48 +0000 (19:12 +0100)]
which: Update to version 2.23
- Update from version 2.21 to 2.23
- Update of rootfile not required
- Changelog
2.23
Bug fix; cleaning up a path like "/path/a/../b/foo" before printing was broken
in 2.22.
2.22
Improved Windows support (by Mitch Capper).
The function that decides if a found path is executable (file_status)
was updated to that of bash version 5.2.
Signed-off-by: Adolf Belka <adolf.belka@ipfire.org> Signed-off-by: Michael Tremer <michael.tremer@ipfire.org>
Adolf Belka [Wed, 26 Feb 2025 18:12:47 +0000 (19:12 +0100)]
tshark: Update to version 4.4.5
- Update from version 4.4.4 to 4.4.5
- Update of rootfile
- Changelog
4.4.5
Bug Fixes
GRPC: protobuf_json only displays the truncated string value. Issue 20392.
Wireshark crashes when clicking on a column title/header. Issue 20403.
Updated Protocol Support
GNW, IPv4, NFAPI, and ProtoBuf
Signed-off-by: Adolf Belka <adolf.belka@ipfire.org> Signed-off-by: Michael Tremer <michael.tremer@ipfire.org>
Adolf Belka [Wed, 26 Feb 2025 18:12:46 +0000 (19:12 +0100)]
postfix: Update to version 3.10.1
- Update from version 3.9.1 to 3.10.1
- Update of rootfile not required
- Changelog
3.10.1
Bugfix (defect introduced: 20250210): a recent 'fix' for the default
smtp_tls_dane_insecure_mx_policy setting resulted in unnecessary 'dnssec_probe'
warnings, on systems that disable DNSSEC lookups (which is the default).
3.10.0
Changes that need a restart:
Internal protocol change: Postfix needs "postfix reload" (or "postfix stop"
and "postfix start") after upgrade, because of a change in the delivery
agent protocol. If this step is skipped, Postfix delivery agents will
log a warning:
unexpected attribute smtputf8 from xxx socket (expecting: sendopts)
where xxx is the delivery agent service name.
Changes in TLS support:
Forward compatibility: Support for OpenSSL 3.5 post-quantum cryptography.
To manage algorithm selection, OpenSSL introduces new TLS group syntax
that Postfix will not attempt to imitate. Instead, Postfix now allows
the tls_eecdh_auto_curves and tls_ffdhe_auto_groups parameter values to
have an empty value. When both are set empty, the algorithm selection
can be managed through OpenSSL configuration. For more, look for
"Post-quantum" in the postconf(5) manpage.
Support for the RFC 8689 "TLS-Required: no" message header to request
delivery of messages (such as TLSRPT summaries) even if the preferred
TLS security policy cannot be enforced. This limits the Postfix SMTP
client to "smtp_tls_security_level = may" which does not authenticate
server certificates and which allows falling back to plaintext.
Support for the REQUIRETLS SMTP service extension will evolve in Postfix 3.11.
Support for the TLSRPT protocol (defined in RFC 8460). With this, a domain
can publish a policy in DNS that requests daily summary reports for
successful and failed SMTP-over-TLS connections to that domain's MX
hosts. This supports both DANE (built-in) and MTA-STS (via an
smtp_tls_policy_maps plugin). The implementation uses a TLSRPT library
and reporting infrastructure that are maintained by sys4. For details,
see TLSRPT_README.
Miscellaneous changes:
Privacy: With "smtpd_hide_client_session = yes", the Postfix SMTP server
generates a Received: header without client session info. This setting
may be used with the MUA submission services (port 465 and 587).
Support for RFC 2047 encoding of non-ASCII "full name" information in
Postfix-generated From: message headers. Encoding non-ASCII full names
can avoid the need to use SMTPUTF8, and therefore can avoid
incompatibility with sites that do not support SMTPUTF8. See the
full_name_encoding_charset parameter description for details.
Database performance: When mysql: or pgsql: configuration specifies a
single host, assume that it is a load balancer and reconnect
immediately after a single failure, instead of failing all requests
for 60s.
Changes in logging:
The Postfix Milter implementation now logs the reason for a 'quarantine'
action, instead of "milter triggers HOLD action".
The SMTP server now logs the queue ID (or "NOQUEUE") when a connection
ends abnormally (timeout, lost connection, or too many errors), and
the cleanup server now logs "queueid: canceled" when a message
transaction is started but not completed. These changes simplify
logfile analysis.
Dovecot SASL client logging for "Invalid authentication mechanism" now
includes the name of that mechanism.
Postfix SMTP server 'reject' logging now shows the sasl_method,
sasl_username, and sasl_sender if available.
3.9.2
Forward compatibility: Support for OpenSSL 3.5 post-quantum cryptography.
To manage algorithm selection, OpenSSL introduces new TLS group syntax
that Postfix will not attempt to imitate. Instead, Postfix now allows
the tls_eecdh_auto_curves and tls_ffdhe_auto_groups parameter values
to have an empty value. When both are set empty, the algorithm
selection can be managed through OpenSSL configuration. Viktor Dukhovni.
Forward compatibility: ignore new queue file flag bits that may be used
with Postfix 3.10 and later. This is a safety in case a Postfix 3.10
upgrade needs to be rolled back, after the new TLS-Required feature
has been used.
Performance: when a mysql: or pgsql: configuration specifies a single
host, assume that it is a load balancer and reconnect immediately
after a single failure, instead of failing all requests for 60s.
Bugfix (defect introduced: Postfix 3.4, date 20181113): a server with
multiple TLS certificates could report, for a resumed TLS session, the
wrong server-signature and server-digest names in logging and
Received: message headers. Viktor Dukhovni.
Bugfix (defect introduced: Postfix 3.3, date 20180107) small memory leak
in the cleanup daemon when generating a "From: full-name " message
header. The impact is limited because the number of requests is
bounded by the "max_use" configuration parameter. Found during code
maintenance.
Bugfix (defect introduced: Postfix 3.0): the bounce daemon mangled a
non-ASCII address localpart in the "X-Postfix-Sender:" field of a
delivery status notification. It backslash-escaped each byte in a
multi-byte character. This behavior was implemented in Postfix 2.1 (no
support for UTF8 local-parts), but it became incorrect after SMTPUTF8
support was implemented in Postfix 3.0.
Bugfix (defect introduced: Postfix 3.6): Reverted the default
smtp_tls_dane_insecure_mx_policy setting to "dane" as of
Postfix 3.6.17, 3.7.13, 3.8.8, 3.9.2, and 3.10.0. By mistake the
default was dependent on the smtp_tls_security_level setting. Problem
reported by Ömer Güven.
Portability: added "include <sys_socket.h>" for a SUNOS5 workaround. Gary
R. Schmidt.
Signed-off-by: Adolf Belka <adolf.belka@ipfire.org> Signed-off-by: Michael Tremer <michael.tremer@ipfire.org>
Adolf Belka [Wed, 26 Feb 2025 18:12:45 +0000 (19:12 +0100)]
pcre2: Update to version 10.45
- Update from version 10.44 to 10.45
- Update of rootfile
- Changelog
10.45
This is a comparatively large release, incorporating new features, some
bugfixes, and a few changes with slight backwards compatibility implications.
Please see the ChangeLog and Git log for further details.
Only changes to behaviour, changes to the API, and major changes to the pattern
syntax are described here.
This release is the first to be available as a (signed) Git tag, or
alternatively as a (signed) tarball of the Git tag.
This is also the first release to be made by the new maintainers of PCRE2, and
we would like to thank Philip Hazel, creator and maintainer of PCRE and PCRE2.
* (Git change) The sljit project has been split out into a separate Git
repository. Git users must now run `git submodule init; git submodule update`
after a Git checkout.
* (Behaviour change) Update Unicode support to UCD 16.
* (Match behaviour change) Case-insensitive matching of Unicode properties
Ll, Lt, and Lu has been changed to match Perl. Previously, /\p{Ll}/i would
match only lower-case characters (even though case-insensitive matching was
specified). This also affects case-insensitive matching of POSIX classes such
as [:lower:].
* (Minor match behaviour change) Case-insensitive matching of backreferences now
respects the PCRE2_EXTRA_CASELESS_RESTRICT option.
* (Minor pattern syntax change) Parsing of the \x escape is stricter, and is
no longer parsed as an escape for the NUL character if not followed by '{' or
a hexadecimal digit. Use \x00 instead.
* (Major new feature) Add a new feature called scan substring. This is a new
type of assertion which matches the content of a capturing block to a
sub-pattern.
Example: to find a word that contains the rare (in English) sequence of
letters "rh" not at the start:
\b(\w++)(*scan_substring:(1).+rh)
The first group captures a word which is then scanned by the
(*scan_substring:(1) ... ) assertion, which tests whether the pattern ".+rh"
matches the capture group "(1)".
* (Major new feature) Add support for UTS#18 compatible character classes,
using the new option PCRE2_ALT_EXTENDED_CLASS. This adds '[' as a
metacharacter within character classes and the operators '&&', '--' and '~~',
allowing subtractions and intersections of character classes to be easily
expressed.
Example: to match Thai or Greek letters (but not letters or other characters
in those scripts), use [\p{L}&&[\p{Thai}||\p{Greek}]].
* (Major new feature) Add support for Perl-style extended character classes,
using the syntax (?[...]). This also allows expressing subtractions and
intersections of character classes, but using a different syntax to UTS#18.
Example: to match Thai or Greek letters (but not letters or other characters
in those scripts), use (?[\p{L} & (\p{Thai} + \p{Greek})]).
* (Minor feature) Significant improvements to the character class match engine.
Compiled character classes are now more compact, and have faster matching
for large or complex character sets, using binary search through the set.
* JIT compilation now fails with the new error code PCRE2_ERROR_JIT_UNSUPPORTED
for patterns which use features not supported by the JIT compiler.
* (Minor feature) New options PCRE2_EXTRA_NO_BS0 (disallow \0 as an escape for
the NUL character); PCRE2_EXTRA_PYTHON_OCTAL (use Python disambiguation rules
for deciding whether \12 is a backreference or an octal escape);
PCRE2_EXTRA_NEVER_CALLOUT (disable callout syntax entirely);
PCRE2_EXTRA_TURKISH_CASING (use Turkish rules for case-insensitive matching).
* (Minor feature) Add new API function pcre2_set_optimize() for controlling
which optimizations are enabled.
* (Minor new features) A variety of extensions have been made to
pcre2_substitute() and its syntax for replacement strings. These now support:
\123 octal escapes; titlecasing \u\L; \1 backreferences; \g<1> and $<NAME>
backreferences; $& $` $' and $_; new function
pcre2_set_substitute_case_callout() to allow locale-aware case transformation.
Signed-off-by: Adolf Belka <adolf.belka@ipfire.org> Signed-off-by: Michael Tremer <michael.tremer@ipfire.org>
Adolf Belka [Wed, 26 Feb 2025 18:12:44 +0000 (19:12 +0100)]
libffi: Update to version 3.4.7
- Update from version 3.4.6 to 3.4.7
- Update of rootfile not required
- Changelog
3.4.7
Add static trampoline support for Linux on s390x.
Fix BTI support for ARM64.
Support pointer authentication for ARM64.
Fix ASAN compatibility.
Fix x86-64 calls with 6 GP registers and some SSE registers.
Miscellaneous fixes for ARC and Darwin ARM64.
Fix OpenRISC or1k and Solaris 10 builds.
Remove nios2 port.
Signed-off-by: Adolf Belka <adolf.belka@ipfire.org> Signed-off-by: Michael Tremer <michael.tremer@ipfire.org>
Adolf Belka [Wed, 26 Feb 2025 18:12:43 +0000 (19:12 +0100)]
diffutils: Update to version 3.11
- Update from version 3.10 to 3.11
- Update of rootfile not required
- Changelog
3.11
Improvements
Programs now quote file names more consistently in diagnostics.
For example; "cmp 'none of' /etc/passwd" now might output
"cmp: EOF on ‘none of’ which is empty" instead of outputting
"cmp: EOF on none of which is empty". In diagnostic messages
that traditionally omit quotes and where backward compatibility
seems to be important, programs continue to omit quotes unless
a file name contains shell metacharacters, in which case programs
use shell quoting. For example, although diff continues to output
"Only in a: b" as before for most file names, it now outputs
"Only in 'a: b': 'c: d'" instead of "Only in a: b: c: d" because the
file names 'a: b' and 'c: d' contain spaces. For compatibility
with previous practice, diff -c and -u headers continue to quote for
C rather than for the shell.
diff now outputs more information when symbolic links differ, e.g.,
"Symbolic links ‘d/f’ -> ‘a’ and ‘e/f’ -> ‘b’ differ", not just
"Symbolic links d/f and e/f differ". Special files too, e.g.,
"Character special files ‘d/f’ (1, 3) and ‘e/f’ (5, 0) differ", not
"File d/f is a character special file while file e/f is a character
special file".
diff's --ignore-case (-i) and --ignore-file-name-case options now
support multi-byte characters. For example, they treat Greek
capital Δ like small δ when input uses UTF-8.
diff now supports multi-byte characters when treating white space.
In options like --expand-tabs (-t), --ignore-space-change (-b) and
--ignore-tab-expansion (-E), diff now recognizes non-ASCII space
characters and counts columns for non-ASCII characters.
Bug fixes
cmp -bl no longer omits "M-" from bytes with the high bit set in
single-byte locales like en_US.iso8859-1. This fix causes the
behavior to be locale independent, and to be the same as the
longstanding behavior in the C locale and in locales using UTF-8.
[bug introduced in 2.9]
cmp -i N and -n N no longer fail merely because N is enormous.
[bug present since "the beginning"]
cmp -s no longer mishandles /proc files, for which the Linux kernel
reports a zero size even when nonempty. For example, the following
shell command now outputs nothing, as it should:
cp /proc/cmdline t; cmp -s /proc/cmdline t || echo files differ
[bug present since "the beginning"]
diff -E no longer mishandles some input lines containing '\a', '\b',
'\f', '\r', '\v', or '\0'.
[bug present since 2.8]
diff -ly no longer mishandles non-ASCII input.
[bug#64461 introduced in 2.9]
diff - A/B now works correctly when standard input is a directory,
by reading a file named B in that directory.
[bug present since "the beginning"]
diff no longer suffers from race conditions in some cases
when comparing files in a mutating file system.
[bug present since "the beginning"]
Release
distribute gzip-compressed tarballs once again
Signed-off-by: Adolf Belka <adolf.belka@ipfire.org> Signed-off-by: Michael Tremer <michael.tremer@ipfire.org>
Adolf Belka [Wed, 26 Feb 2025 18:12:42 +0000 (19:12 +0100)]
btrfs-progs: Update to version 6.13
- Update from version 6.11 to 6.13
- Update of rootfile not required
- Changelog
6.13
mkfs:
new option to enable compression
updated summary (subvolumes, compression)
completely remove option --leafsize, deprecated long ago
btrfstune: add option to remove squota
scrub:
start: new option --limit to set the bandwidth limit for the duration of
the run
status: fix printing of Rate unit suffix (SI/IEC)
qgroup clean-stale: check if quotas are enabled before starting filesystem sync()
print builtin features and options in --version output (mkfs, convert,
image, btrfstune)
build:
Botan minimum version is now 3.x
target to build compile_commands.json (for LSP)
other:
a bit more optimized crc32c code
sync some headers from kernel code
command help updates and fixes
build warning fixes
error message updates
cleanups and refactoring
updated tests
lots of documentation updates
6.12
subvolume delete: add new option to do recursive subvolume deletion (for
regular user delete only accessible subvolumes)
mkfs:
new option --subvol to create subvolumes in given paths, read-write,
read-only and default
add hard link detection support for --rootdir option
fixes:
receive: message verbosity fixes
check: fix false positive report of missing checksum for extent holes
check: handle compressed extents when checking tree log
when asking Y/N user questions, flush the terminal so the question is
displayed (e.g. btrfstune -S)
other
code refactoring, error handling
python packaging fixes
documentation updates
new tests
Signed-off-by: Adolf Belka <adolf.belka@ipfire.org> Signed-off-by: Michael Tremer <michael.tremer@ipfire.org>
Matthias Fischer [Sat, 22 Feb 2025 16:47:41 +0000 (17:47 +0100)]
dhcpcd: Update to 10.2.0
For details see:
https://github.com/NetworkConfiguration/dhcpcd/releases/tag/v10.2.0
"What's Changed
dhcp6: start request when advertise received after IRT by @sshambar in #376
dhcpcd: stdout output sometimes empty when redirected to a file by @diego-santacruz in #364
Fix help text formatting by @jvfranklin in #379
Apply lastlease behavior to DHCPv6 by @jvfranklin in #384
dhcpcd not ignoring source-based routes on linux by @sshambar in #372
DHCP6: lastlease behavior after Confim non-response by @jvfranklin in #387
Allow limited RLIMIT_FSIZE when dumping lease by @ColinMcInnes in #389
IPv6: Avoid uninitialized ifp state when adding address by @kensimon in #395
DHCPv6: Add support for sending Option 17 (VSIO) by @spoljak-ent in #383
Exit the timesyncd hook if not on systemd and not executable (#398) by @perkelix in #403
Add route lifetime from Router Advertisement by @ColinMcInnes in #429
revert e3c5de1 by @zacknewman in #425
Fix using multiple enterprise IDs with vendclass (Option 124 DHCP / Option 16 DHCPv6) (#328) by @spoljak-ent in #408
Update route if acquired time changes by @ColinMcInnes in #441
Always send req for InfoRefreshTime option on Inform-Req by @ColinMcInnes in #446
Increase max IPv4 clientid. by @gnaaman-dn in #442
Update build.yml to fix BSD builds by @perkelix in #456"
Signed-off-by: Matthias Fischer <matthias.fischer@ipfire.org> Signed-off-by: Michael Tremer <michael.tremer@ipfire.org>
Adolf Belka [Sun, 23 Feb 2025 18:14:19 +0000 (19:14 +0100)]
libxcrypt: Update to version 4.4.38
- Update from version 4.4.36 to 4.4.38
- Update of rootfile not required
- in version 4.4.37 pkg-config was made a dependency for building libxcrypt. This caused
user(s) a problem when libxcrypt was being built before pkg-config wasw available.
- In version 4.4.38 it was allowed that if pkg-config was not available then the build
would continue and complete but any installation of .pc files was no longer carried
out.
- moved pkg-config to before libxcrypt so that the libxcrypt.pc file is installed in the
build environment and the libcrypt.pc file linked to it, the same as used to occur in
version 4.4.36
- Changelog
4.4.38
* Fix several "-Wunterminated-string-initialization", which are seen by
upcoming GCC 15.x (issue #194).
* Fix "-Wmaybe-uninitialized" in crypt.c, which is seen by GCC 13.3.0.
* Skip test/explicit-bzero if compiling with ASAN.
* Drop hard requirement for the pkg-config binary (issue #198).
4.4.37
* Several fixes to the manpages (issue #185).
* Add binary compatibility for x86_64 GNU/Hurd (issue #189).
* Only test the needed makecontext signature during configure (issue #178).
* Fix -Werror=strict-overflow in lib/crypt-bcrypt.c, which is seen
by GCC 4.8.5 (issue #197).
Signed-off-by: Adolf Belka <adolf.belka@ipfire.org> Signed-off-by: Michael Tremer <michael.tremer@ipfire.org>
Adolf Belka [Fri, 21 Feb 2025 12:44:49 +0000 (13:44 +0100)]
pmacct: Remove autogen.sh step so it builds with autoconf-2.72
- Although the pmacct source tarball has a configure script provided, for some reason
the lfs file ran autogen.sh first and therefore re-created the configure script.
Whatever the autogen.sh script was creating it ended up with a result that the new
autoconf-2.72 didn't like. Some problem with an end of line that was not of the
expected structure.
- It seems reasonable to use the configure script that has been provided by the pmacct
developers in the source tarbal, so this patch removes the use of the autogen.sh
script and uses the configure script provided by pmacct. This then allowed a
successful build with the autoconf-2.72
Signed-off-by: Adolf Belka <adolf.belka@ipfire.org> Signed-off-by: Michael Tremer <michael.tremer@ipfire.org>
Adolf Belka [Fri, 21 Feb 2025 12:44:48 +0000 (13:44 +0100)]
autoconf: Update to version 2.72
- Update from version 2.71 to 2.72
- Update of rootfile
- The update of collectd from 4.10.9 to 5.12.0 now allows it to build with this newer
version of autoconf.
- pmacct however failed to build with it. Updated the pmacct lfs to allow it to build
with this newer version of autoconf. Fix for that is combined in this patch set.
- Changelog
2.72
Backward incompatibilities
Configure scripts no longer support pre-1989 C compilers.
Specifically, compilers that *only* implement the original “K&R”
function definition syntax, and not the newer “prototyped” syntax,
will not be able to parse the test programs now emitted by
AC_CHECK_FUNC, AC_LANG_CALL, and similar macros. AC_PROG_CC still
accepts such compilers, but this may change in the near future.
This change was necessary in order to support the upcoming 2024
edition of the C standard (often referred to as “C23”), which will
officially remove the function declaration syntax used by
AC_CHECK_FUNC in Autoconf 2.71 and earlier. We feel that support
for compilers that support only C 2024 is more useful, nowadays,
than support for compilers that don’t implement a core feature of
C 1989.
Autoconf developers now need Perl 5.10 (2007) or later.
“Autoconf developers” means specifically people hacking on Autoconf
itself. Autoconf *users*, i.e. authors of configure.ac files and
add-on M4 macros, still need only Perl 5.6 (2000) or later.
We do recommend all Autoconf users upgrade to Perl 5.10 or later if
possible, as this version significantly improves Perl’s ability to
handle files with last-modification timestamps separated by less
than a second. (Note: even in the most recent release, Perl cannot
always match the file system’s timestamp resolution.)
Generated configure scripts continue to run without Perl.
Autoconf users now need GNU M4 1.4.8 (2006) or later.
Use of GNU M4 1.4.16 or later is recommended, as all earlier versions
are known to have had serious bugs in the text-processing builtins
on some, but not all, operating systems. Autoconf’s own configure
script will attempt to find a version of M4 that is not affected by
these bugs.
Note: Autoconf 2.70 and 2.71 include code that malfunctions with
M4 1.4.6 or 1.4.7. However, the only effect of the malfunction is
that you will get a confusing error message if you run autoconf on
a configure.ac that neglects to use AC_INIT or AC_OUTPUT.
Generated 'configure' scripts continue to run without M4.
Some m4sh diversions have been renumbered.
This will only affect macros that use m4_divert with numbered rather
than named diversions, which has always been strongly discouraged
both by the documentation and with warnings.
AC_FUNC_GETGROUPS and AC_TYPE_GETGROUPS no longer run test programs.
These macros were testing for OS bugs that we believe are at least
twenty years in the past. Most operating systems are now trusted to
provide an accurate prototype for getgroups in unistd.h, and to
implement it as specified in POSIX.
AC_FUNC_GETGROUPS still includes a short block-list of OSes with
known, severe bugs in getgroups. It can be overridden using
config.site. If you encounter a mistake in this list,
please report it to bug-autoconf.
All internal uses of AC_EGREP_CPP and AC_EGREP_HEADER have been removed.
These macros look for text matching a regular expression in the
output of the C preprocessor. Their use has been discouraged for
many years, as they tend to be unreliable; it is better to find a
way to use AC_COMPILE_IFELSE or AC_PREPROC_IFELSE instead. We have
finally taken our own advice.
This change might break configure scripts that expected probes for
‘grep’ and/or the C preprocessor to happen as a side effect of an
unrelated operation. Such scripts can be fixed by adding
AC_PROG_EGREP and/or AC_PROG_CPP in an appropriate place.
The macros affected by this change are AC_C_STRINGIZE,
AC_C_VARARRAYS, AC_FUNC_GETGROUPS, AC_FUNC_GETLOADAVG,
AC_HEADER_TIOCGWINSZ, AC_PROG_GCC_TRADITIONAL, AC_TYPE_GETGROUPS,
AC_TYPE_UID_T, and AC_XENIX_DIR. Many of these macros are themselves
obsolete; if your configure script uses any of them, check whether
it is actually needed.
New features
Support for ensuring time_t is Y2038-safe
configure can now ensure that time_t can represent moments in time
after 18 January 2038, i.e. 2**31 - 1 seconds after the Unix epoch.
On most “64-bit” systems this is true by default; the new feature
is detection of systems where time_t is a 32-bit signed integer by
default, *and* there is an alternative mode in which it is larger,
in which case that mode will be enabled.
In this release, all configure scripts that use AC_SYS_LARGEFILE
gain a new command line option --enable-year2038. When this option
is used, the configure script will check for and enable support for
a large time_t.
This release also adds two new macros, AC_SYS_YEAR2038 and
AC_SYS_YEAR2038_RECOMMENDED. Both have all the effects of
AC_SYS_LARGEFILE. (This is because it is not possible to enlarge
time_t without also enlarging off_t, on any system we are aware of.)
AC_SYS_YEAR2038 additionally flips the default for --enable-year2038;
a configure script that uses this macro will check for and enable
support for a large time_t by default, but this can be turned off by
using --disable-year2038. AC_SYS_YEAR2038_RECOMMENDED goes even
further, and makes the configure script fail on systems that do not
seem to support timestamps after 18 January 2038 at all. This
failure can be suppressed by using --disable-year2038.
Changing the size of time_t can change a library’s ABI. Therefore,
application and library builders should take care that all packages
are configured with consistent use of --enable-year2038 or
--disable-year2038, to ensure binary compatibility. This is similar
to longstanding consistency requirements with --enable-largefile and
--disable-largefile.
In this release, these macros only know how to enlarge time_t on two
classes of systems: 32-bit MinGW, and any system where time_t can be
enlarged by defining the preprocessor macro _TIME_BITS with the
value 64. At the time this NEWS entry was written, only GNU libc
(version 2.34 and later) supported the latter macro. Authors of
other C libraries with a 32-bit time_t are encouraged to adopt
_TIME_BITS, rather than inventing a different way to enlarge time_t.
AC_USE_SYSTEM_EXTENSIONS now enables C23 Annex F extensions
by defining __STDC_WANT_IEC_60559_EXT__.
Obsolete features and new warnings
Autoconf now quotes 'like this' instead of `like this'.
Autoconf’s diagnostics now follow current GNU coding standards,
which say that diagnostics in the C locale should quote 'like this'
with plain apostrophes instead of the older GNU style `like this'
with grave accent and apostrophe.
AC_PROG_GCC_TRADITIONAL no longer does anything.
This macro has had no useful effect since GCC dropped support for
traditional-mode compilation in version 3.3 (released in 2003), and
the systems that needed it are also long obsolete. It is now a
compatibility synonym for AC_PROG_CC.
Notable bug fixes
autom4te now uses fine-grained file timestamps
Autoconf’s internal “autom4te” utility is now able to compare file
modification timestamps with sub-second precision, when available.
This eliminates a class of bugs where autom4te fails to regenerate
an outdated file. Automake 1.17 (forthcoming) is required for a
complete fix.
AC_HEADER_STDBOOL, AC_CHECK_HEADER_STDBOOL are obsolescent and less picky.
These macros are now obsolescent, as most programs can simply include
stdbool.h unconditionally. If you use these macros, they now accept
a stdbool.h that exists but does nothing, so long as ‘bool’, ‘true’,
and ‘false’ work anyway. This is for compatibility with C23 and
with C++.
AC_PROG_MKDIR_P now falls back on plain 'mkdir -p'.
When AC_PROG_MKDIR_P cannot find a mkdir implementation that is
known to lack race condition bugs, it now falls back on 'mkdir -p'
instead of falling back on a relative path to install-sh, as the
relative paths now seem to be a more important problem than the
problems of ancient mkdir implementations with race condition bugs.
See <https://savannah.gnu.org/support/?110740>. The only ancient
mkdir still supported is Solaris 10 /usr/bin/mkdir, and for that
platform AC_PROG_MKDIR_P falls back on /opt/sfw/bin/mkdir which
should work if it is installed; if not, you should avoid parallel
'make' on that platform.
Better diagnostics for calling m4_warn() with a bad first argument
Calling m4_warn with a first argument that doesn’t match any of the
official warning categories now produces a sensible error message,
instead of something that makes it look like there’s a bug in the
guts of autom4te. Also, the documentation has been adjusted in
several places to make it clearer what the official warning
categories are.
Note: In Autoconf 2.69 and earlier, the manual said that [] and [all]
could be used as the first argument to m4_warn. This was incorrect,
even at the time.
Improved compatibility with a wide variety of systems and tools
including CheriBSD, Darwin (macOS), GNU Guix, OS/2, z/OS, Bash 5.2,
the BusyBox shell and utilities, Clang/LLVM version 16, the upcoming
GCC version 14, etc.
Known bugs
AC_SYS_LARGEFILE and AC_SYS_YEAR2038 only work correctly in C mode.
This is only a problem for configure scripts that invoke either
macro while AC_LANG([something other than C]) is in effect, and
will only be a *visible* problem on systems where support
for large files and/or timestamps after 2038 are *available*
but not enabled by default.
This is the cause of the AC_SYS_LARGEFILE, AC_SYS_YEAR2038, and/or
AC_SYS_YEAR2038_RECOMMENDED testsuite failures on some systems.
See <https://savannah.gnu.org/support/index.php?110983> for details
and a workaround.
Signed-off-by: Adolf Belka <adolf.belka@ipfire.org> Signed-off-by: Michael Tremer <michael.tremer@ipfire.org>
Adolf Belka [Fri, 21 Feb 2025 12:21:27 +0000 (13:21 +0100)]
fmt: Update to version 11.1.3
- Update from version 11.0.2 to 11.1.3
- Update of rootfile
- Changelog
11.1.3
- Fixed compilation on GCC 9.4 (https://github.com/fmtlib/fmt/issues/4313).
- Worked around an internal compiler error when using C++20 modules with GCC
14.2 and earlier (https://github.com/fmtlib/fmt/issues/4295).
- Worked around a bug in GCC 6 (https://github.com/fmtlib/fmt/issues/4318).
- Fixed an issue caused by instantiating `formatter<const T>`
(https://github.com/fmtlib/fmt/issues/4303,
https://github.com/fmtlib/fmt/pull/4325). Thanks @timsong-cpp.
- Fixed formatting into `std::ostreambuf_iterator` when using format string
compilation (https://github.com/fmtlib/fmt/issues/4309,
https://github.com/fmtlib/fmt/pull/4312). Thanks @phprus.
- Restored a constraint on the map formatter so that it correctly reports as
unformattable when the element is (https://github.com/fmtlib/fmt/pull/4326).
Thanks @timsong-cpp.
- Reduced the size of format specs (https://github.com/fmtlib/fmt/issues/4298).
- Readded `args()` to `fmt::format_context`
(https://github.com/fmtlib/fmt/issues/4307,
https://github.com/fmtlib/fmt/pull/4310). Thanks @Erroneous1.
- Fixed a bogus MSVC warning (https://github.com/fmtlib/fmt/issues/4314,
https://github.com/fmtlib/fmt/pull/4322). Thanks @ZehMatt.
- Fixed a pedantic mode error in the CMake config
(https://github.com/fmtlib/fmt/pull/4327). Thanks @rlalik.
11.1.2
- Fixed ABI compatibility with earlier 11.x versions
(https://github.com/fmtlib/fmt/issues/4292).
- Added `wchar_t` support to the `std::bitset` formatter
(https://github.com/fmtlib/fmt/issues/4285,
https://github.com/fmtlib/fmt/pull/4286,
https://github.com/fmtlib/fmt/issues/4289,
https://github.com/fmtlib/fmt/pull/4290). Thanks @phprus.
- Prefixed CMake components with `fmt-` to simplify usage of {fmt} via
`add_subdirectory` (https://github.com/fmtlib/fmt/issues/4283).
- Updated docs for meson (https://github.com/fmtlib/fmt/pull/4291).
Thanks @trim21.
- Fixed a compilation error in chrono on nvcc
(https://github.com/fmtlib/fmt/issues/4297,
https://github.com/fmtlib/fmt/pull/4301). Thanks @breyerml.
- Fixed various warnings
(https://github.com/fmtlib/fmt/pull/4288,
https://github.com/fmtlib/fmt/pull/4299). Thanks @GamesTrap and @edo9300.
11.1.1
- Fixed ABI compatibility with earlier 11.x versions
(https://github.com/fmtlib/fmt/issues/4278).
- Defined CMake components (`core` and `doc`) to allow docs to be installed
separately (https://github.com/fmtlib/fmt/pull/4276).
Thanks @carlsmedstad.
11.1.0
- Improved C++20 module support
(https://github.com/fmtlib/fmt/issues/4081,
https://github.com/fmtlib/fmt/pull/4083,
https://github.com/fmtlib/fmt/pull/4084,
https://github.com/fmtlib/fmt/pull/4152,
https://github.com/fmtlib/fmt/issues/4153,
https://github.com/fmtlib/fmt/pull/4169,
https://github.com/fmtlib/fmt/issues/4190,
https://github.com/fmtlib/fmt/issues/4234,
https://github.com/fmtlib/fmt/pull/4239).
Thanks @kamrann and @Arghnews.
- Reduced debug (unoptimized) binary code size and the number of template
instantiations when passing formatting arguments. For example, unoptimized
binary code size for `fmt::print("{}", 42)` was reduced by ~40% on GCC and
~60% on clang (x86-64).
GCC:
- Before: 161 instructions of which 105 are in reusable functions
([godbolt](https://www.godbolt.org/z/s9bGoo4ze)).
- After: 116 instructions of which 60 are in reusable functions
([godbolt](https://www.godbolt.org/z/r7GGGxMs6)).
Clang:
- Before: 310 instructions of which 251 are in reusable functions
([godbolt](https://www.godbolt.org/z/Ts88b7M9o)).
- After: 194 instructions of which 135 are in reusable functions
([godbolt](https://www.godbolt.org/z/vcrjP8ceW)).
- Added an experimental `fmt::writer` API that can be used for writing to
different destinations such as files or strings
(https://github.com/fmtlib/fmt/issues/2354).
For example ([godbolt](https://www.godbolt.org/z/rWoKfbP7e)):
```c++
#include <fmt/os.h>
void write_text(fmt::writer w) {
w.print("The answer is {}.", 42);
}
int main() {
// Write to FILE.
write_text(stdout);
// Write to fmt::ostream.
auto f = fmt::output_file("myfile");
write_text(f);
// Write to std::string.
auto sb = fmt::string_buffer();
write_text(sb);
std::string s = sb.str();
}
```
- Added width and alignment support to the formatter of `std::error_code`.
- Made `std::expected<void, E>` formattable
(https://github.com/fmtlib/fmt/issues/4145,
https://github.com/fmtlib/fmt/pull/4148).
For example ([godbolt](https://www.godbolt.org/z/hrj5c6G86)):
```c++
fmt::print("{}", std::expected<void, int>());
```
prints
```
expected()
```
Thanks @phprus.
- Made `fmt::is_formattable<void>` SFINAE-friendly
(https://github.com/fmtlib/fmt/issues/4147).
- Added support for `_BitInt` formatting when using clang
(https://github.com/fmtlib/fmt/issues/4007,
https://github.com/fmtlib/fmt/pull/4072,
https://github.com/fmtlib/fmt/issues/4140,
https://github.com/fmtlib/fmt/issues/4173,
https://github.com/fmtlib/fmt/pull/4176).
For example ([godbolt](https://www.godbolt.org/z/KWjbWec5z)):
```c++
using int42 = _BitInt(42);
fmt::print("{}", int42(100));
```
Thanks @Arghnews.
- Added the `n` specifier for tuples and pairs
(https://github.com/fmtlib/fmt/pull/4107). Thanks @someonewithpc.
- Added support for tuple-like types to `fmt::join`
(https://github.com/fmtlib/fmt/issues/4226,
https://github.com/fmtlib/fmt/pull/4230). Thanks @phprus.
- Made more types formattable at compile time
(https://github.com/fmtlib/fmt/pull/4127). Thanks @AnthonyVH.
- Implemented a more efficient compile-time `fmt::formatted_size`
(https://github.com/fmtlib/fmt/issues/4102,
https://github.com/fmtlib/fmt/pull/4103). Thanks @phprus.
- Fixed compile-time formatting of some string types
(https://github.com/fmtlib/fmt/pull/4065). Thanks @torshepherd.
- Made compiled version of `fmt::format_to` work with
`std::back_insert_iterator<std::vector<char>>`
(https://github.com/fmtlib/fmt/issues/4206,
https://github.com/fmtlib/fmt/pull/4211). Thanks @phprus.
- Added a formatter for `std::reference_wrapper`
(https://github.com/fmtlib/fmt/pull/4163,
https://github.com/fmtlib/fmt/pull/4164). Thanks @yfeldblum and @phprus.
- Added experimental padding support (glibc `strftime` extension) to `%m`, `%j`
and `%Y` (https://github.com/fmtlib/fmt/pull/4161). Thanks @KKhanhH.
- Made microseconds formatted as `us` instead of `µs` if the Unicode support is
disabled (https://github.com/fmtlib/fmt/issues/4088).
- Fixed an unreleased regression in transcoding of surrogate pairs
(https://github.com/fmtlib/fmt/issues/4094,
https://github.com/fmtlib/fmt/pull/4095). Thanks @phprus.
- Made `fmt::appender` satisfy `std::output_iterator` concept
(https://github.com/fmtlib/fmt/issues/4092,
https://github.com/fmtlib/fmt/pull/4093). Thanks @phprus.
- Made `std::iterator_traits<fmt::appender>` standard-conforming
(https://github.com/fmtlib/fmt/pull/4185). Thanks @CaseyCarter.
- Made it easier to reuse `fmt::formatter<std::string_view>` for types with
an implicit conversion to `std::string_view`
(https://github.com/fmtlib/fmt/issues/4036,
https://github.com/fmtlib/fmt/pull/4055). Thanks @Arghnews.
- Made it possible to disable `<filesystem>` use via `FMT_CPP_LIB_FILESYSTEM`
for compatibility with some video game console SDKs, e.g. Nintendo Switch SDK
(https://github.com/fmtlib/fmt/issues/4257,
https://github.com/fmtlib/fmt/pull/4258,
https://github.com/fmtlib/fmt/pull/4259). Thanks @W4RH4WK and @phprus.
- Fixed compatibility with platforms that use 80-bit `long double`
(https://github.com/fmtlib/fmt/issues/4245,
https://github.com/fmtlib/fmt/pull/4246). Thanks @jsirpoma.
- Added support for UTF-32 code units greater than `0xFFFF` in fill
(https://github.com/fmtlib/fmt/issues/4201).
- Fixed handling of legacy encodings on Windows with GCC
(https://github.com/fmtlib/fmt/issues/4162).
- Made `fmt::to_string` take `fmt::basic_memory_buffer` by const reference
(https://github.com/fmtlib/fmt/issues/4261,
https://github.com/fmtlib/fmt/pull/4262). Thanks @sascha-devel.
- Added `fmt::dynamic_format_arg_store::size`
(https://github.com/fmtlib/fmt/pull/4270). Thanks @hannes-harnisch.
- Removed the ability to control locale usage via an undocumented
`FMT_STATIC_THOUSANDS_SEPARATOR` in favor of `FMT_USE_LOCALE`.
- Renamed `FMT_EXCEPTIONS` to `FMT_USE_EXCEPTIONS` for consistency with other
similar macros.
- Improved include directory ordering to reduce the chance of including
incorrect headers when using multiple versions of {fmt}
(https://github.com/fmtlib/fmt/pull/4116). Thanks @cdzhan.
- Made it possible to compile a subset of {fmt} without the C++ runtime.
- Improved documentation and README
(https://github.com/fmtlib/fmt/pull/4066,
https://github.com/fmtlib/fmt/issues/4117,
https://github.com/fmtlib/fmt/issues/4203,
https://github.com/fmtlib/fmt/pull/4235). Thanks @zyctree and @nikola-sh.
- Improved the documentation generator (https://github.com/fmtlib/fmt/pull/4110,
https://github.com/fmtlib/fmt/pull/4115). Thanks @rturrado.
- Improved CI (https://github.com/fmtlib/fmt/pull/4155,
https://github.com/fmtlib/fmt/pull/4151). Thanks @phprus.
- Fixed various warnings and compilation issues
(https://github.com/fmtlib/fmt/issues/2708,
https://github.com/fmtlib/fmt/issues/4091,
https://github.com/fmtlib/fmt/issues/4109,
https://github.com/fmtlib/fmt/issues/4113,
https://github.com/fmtlib/fmt/issues/4125,
https://github.com/fmtlib/fmt/issues/4129,
https://github.com/fmtlib/fmt/pull/4130,
https://github.com/fmtlib/fmt/pull/4131,
https://github.com/fmtlib/fmt/pull/4132,
https://github.com/fmtlib/fmt/issues/4133,
https://github.com/fmtlib/fmt/issues/4144,
https://github.com/fmtlib/fmt/issues/4150,
https://github.com/fmtlib/fmt/issues/4158,
https://github.com/fmtlib/fmt/pull/4159,
https://github.com/fmtlib/fmt/issues/4160,
https://github.com/fmtlib/fmt/pull/4170,
https://github.com/fmtlib/fmt/issues/4177,
https://github.com/fmtlib/fmt/pull/4187,
https://github.com/fmtlib/fmt/pull/4188,
https://github.com/fmtlib/fmt/pull/4194,
https://github.com/fmtlib/fmt/pull/4200,
https://github.com/fmtlib/fmt/issues/4205,
https://github.com/fmtlib/fmt/issues/4207,
https://github.com/fmtlib/fmt/pull/4208,
https://github.com/fmtlib/fmt/pull/4210,
https://github.com/fmtlib/fmt/issues/4220,
https://github.com/fmtlib/fmt/issues/4231,
https://github.com/fmtlib/fmt/issues/4232,
https://github.com/fmtlib/fmt/pull/4233,
https://github.com/fmtlib/fmt/pull/4236,
https://github.com/fmtlib/fmt/pull/4267,
https://github.com/fmtlib/fmt/pull/4271).
Thanks @torsten48, @Arghnews, @tinfoilboy, @aminya, @Ottani, @zeroomega,
@c4v4, @kongy, @vinayyadav3016, @sergio-nsk, @phprus and @YexuanXiao.
Signed-off-by: Adolf Belka <adolf.belka@ipfire.org> Signed-off-by: Michael Tremer <michael.tremer@ipfire.org>
Adolf Belka [Fri, 21 Feb 2025 12:21:26 +0000 (13:21 +0100)]
mpd: Update to version 0.23.17
- Update from version 0.23.15 to 0.23.17
- Update of rootfile not required
- Patch no longer needed as the fixes to work with fmt-11.0.x have been included in the
source tarball.
- This version includes the fix to work with fmt-11.1.x
- Changelog
0.23.17
* protocol
- "albumart" tries to send larger chunks if available
- explicitly disallow "idle" and "noidle" in command lists
* storage
- nfs: require libnfs 4.0 or later
* database
- inotify: trigger update after symlink was created
* decoder
- ffmpeg: prefer over sndfile and audiofile for its DTS-WAV support
* support libfmt 11.1
0.23.16
* database
- fix integer overflows with 64-bit inode numbers
* filter
- ffmpeg: fix for filters producing no output
* support libfmt 11
* support ICU 76
Signed-off-by: Adolf Belka <adolf.belka@ipfire.org> Signed-off-by: Michael Tremer <michael.tremer@ipfire.org>
Adolf Belka [Thu, 20 Feb 2025 21:13:25 +0000 (22:13 +0100)]
update.sh: Remove ABUSECH_BOTNETC2 lists from users systems during update.
- This removes ABUSECH_BOTNETC2 from users system during the update in the same way as
done previously with ALIENVAULT and SPAMHAUS_EDROP.
- As next is still in CU192 I could not add these lines into the CU193 update.sh so I have
added it to the CU192 update.sh
- If not appropriate then let me know and when the CU193 is created in next I will redo
the patch and re-submit it.
Signed-off-by: Adolf Belka <adolf.belka@ipfire.org> Signed-off-by: Michael Tremer <michael.tremer@ipfire.org>
Adolf Belka [Thu, 20 Feb 2025 21:13:23 +0000 (22:13 +0100)]
sources: Remove ABUSECH_BOTNETC2 from ipblocklist sources
- Abuse.ch deprecated the ABUSECH_BOTNETC2 list on 3rd Jan 2025 without any warning or
notification except for the deprecation message in the block list.
- This patch removes that list from the ipblocklist sources.
- This is part of a patch set that also removes this list from the files in users
systems and from any restore from an earlier backup when the updates sources list is
issued.
Signed-off-by: Adolf Belka <adolf.belka@ipfire.org> Signed-off-by: Michael Tremer <michael.tremer@ipfire.org>
Matthias Fischer [Thu, 20 Feb 2025 23:37:04 +0000 (00:37 +0100)]
bind: Update to 9.20.6
For details see:
https://downloads.isc.org/isc/bind9/9.20.5/doc/arm/html/notes.html#notes-for-bind-9-20-6
"Notes for BIND 9.20.6
New Features
Adds support for EDE code 1 and 2.
Support was added for EDE codes 1 and 2, which might occur during
DNSSEC validation in the case of an unsupported RRSIG algorithm or
DNSKEY digest. [GL #2715]
Add an rndc command to toggle jemalloc profiling.
The new command is rndc memprof; the memory profiling status is also
reported inside rndc status. The status shows whether named can toggle
memory profiling, and whether the server is built with jemalloc. [GL
#4759]
Add support for multiple extended DNS errors.
The Extended DNS Error (EDE) mechanism may raise errors during a DNS
resolution. named is now able to add up to three EDE codes in a DNS
response. If there are duplicate error codes, only the first one is
part of the DNS response. [GL #5085]
Print the expiration time of stale records.
BIND now prints the expiration time of any stale RRsets in the cache
dump.
Bug Fixes
Recently expired records could be returned with a timestamp in future.
Under rare circumstances, an RRSet that expired at the time of the
query could be returned with a TTL in the future. This has been fixed.
As a side effect, the expiration time of expired RRSets is no longer
returned in a cache dump. [GL #5094]
YAML string not terminated in negative response in delv.
[GL #5098]
Fix a bug in dnssec-signzone related to keys being offline.
When dnssec-signzone was called on an already-signed zone and the
private key file was unavailable, a signature that needed to be
refreshed was dropped without being able to generate a replacement.
This has been fixed. [GL #5126]
Apply the memory limit only to ADB database items.
Under heavy load, a resolver could exhaust the memory available for
storing the information in the Address Database (ADB), effectively
discarding previously stored information in the ADB. The memory used to
retrieve and provide information from the ADB is no longer subject to
the same memory limits that are applied to the Address Database. [GL
#5127]
Avoid unnecessary locking in the zone/cache database.
Lock contention among many worker threads referring to the same
database node at the same time is now prevented. This improves zone and
cache database performance for any heavily contended database nodes.
[GL #5130]
Fix reporting of Extended DNS Error 22 (No Reachable Authority).
This error code was previously not reported in some applicable
situations. This has been fixed. [GL #5137]"
Signed-off-by: Matthias Fischer <matthias.fischer@ipfire.org> Signed-off-by: Michael Tremer <michael.tremer@ipfire.org>
Adolf Belka [Thu, 20 Feb 2025 20:57:44 +0000 (21:57 +0100)]
tshark: Update to version 4.4.4
- Update from version 4.4.3 to 4.4.4
- Update of rootfile
- Changelog
4.4.4
The following vulnerabilities have been fixed:
wnpa-sec-2025-01 Bundle Protocol and CBOR dissector {crash,infinite loop,
memory leak}. Issue 20373.
The following bugs have been fixed:
Crash when sorting columns during capture with display filter active. Issue
20263.
OSS-Fuzz 384757274: Invalid-bool-value in dissect_tcp. Issue 20300.
Test failure in 4.4.2/4.4.3: test_sharkd_req_follow_http2. Issue 20330.
Regression in extcap interface toolbar. Issue 20354.
Clicking outside columns in TCP tab of Statistics → Conversations window
causes crash. Issue 20357.
FTBFS with Ubuntu development (25.04) release. Issue 20359.
DNS enable_qname_stats crash Wireshark when QDCOUNT == 0. Issue 20367.
Windows: Android extcap plugin fails with "Broken socket connection" if
there are no new packets for 2sec. Issue 20386.
TECMP: Calculation of lifecycle start in Status message is wrong. Issue 20387.
MQTT v5.0 properties total length presentation is incorrect. Issue 20389.
TShark doesn’t resolve addresses in custom "hosts" files. Issue 20391.
Incorrect JA4 fingerprint with empty ciphers. Issue 20394.
New and Updated Features
Updated Protocol Support
CESoETH, DNS, IEEE 1609.2, ISOBUS, ITS, MPLS, MQTT, PDU
Transport, RTP, TCP, TECMP, WebSocket, and WSMP
New and Updated Capture File Support
CLLog, EMS, and ERF
Signed-off-by: Adolf Belka <adolf.belka@ipfire.org> Signed-off-by: Michael Tremer <michael.tremer@ipfire.org>
Adolf Belka [Thu, 20 Feb 2025 11:16:31 +0000 (12:16 +0100)]
frr: Ship frr to use new libyang version
- PAK_VER incremented to provide build with new libyang version.
- Update of rootfile not required.
- Tested out on vm in combination with the new libyang version. frr daemons were all able
to successfully start. As I have never used frr, I can not test anything further.
Tested-by: Adolf Belka <adolf.belka@ipfire.org> Signed-off-by: Adolf Belka <adolf.belka@ipfire.org> Signed-off-by: Michael Tremer <michael.tremer@ipfire.org>
Adolf Belka [Thu, 20 Feb 2025 11:16:30 +0000 (12:16 +0100)]
libyang: Update to version 3.7.8
- Update from version 2.1.148 to 3.7.8
- Update of rootfile
- Submited as a set with a PAK_VER update of frr as frr needs to be shipped to use this
new version.
- In the changelog for moving the library from 2.x to 3.0 it mentions that there are
some breaking changes but then says they are minor. The library versions are not
alligned with the package version numbers.
Following is what is said:-
* Non-backwards-compatible changes between libyang version 2 and 3 are rather
minor and can be summarized as providing
* structured error information (instead of a single message), unifying
**lyd_new_*()** function options, and some
* minor changes such as removing deprecated functions or making a few functions
inlined. However, there is another
* large change that has not affected the API, specifically configuration
system-ordered lists and leaf-lists are now
* ordered based on their keys/values, respectively. Except for moderately
slower performance and negligible increased
* memory requirements, it should not affect existing applications (assuming
they do not rely on the previous order of
* these instances).
- I tested this updated version of libyang with frr. frr built without any problems. It
just has the requirement that libyang >= 2.1.128, so no restriction that it must not
be version 3. I then installed the IPFire built with the updated libyang and installed
the frr that was built with it. I was able to start frr successfully, so all the
specified frr daemons successfully started.
- I could only test that frr successfully had all the daemons start but could not test
out actual functioning of frr as this is something I have never used. I would expect
that if all the daemons start successfully then frr should be happy working with
libyang-3.7.8
- Changelog
3.7.8
yanglint UTF8 support
validation optimizations
lots of bugfixes
3.4.2
data handling optimizations
32b build fixes
various bugfixes
3.1.0
lots of improvements and bugfixes in various parts of the library
2.2.8
new SO version 3
with some non-backwards compatible changes
transition manual from version 2 in docs
(leaf-)list instance semantic ordering
sorts instances based on their values or their key values
minor performance cost
logging API improved
new parsing flag LYD_PARSE_STORE_ONLY
avoids value validation
run-time plugin support
build improvements
lots of other bugfixes and optimizations
Tested-by: Adolf Belka <adolf.belka@ipfire.org> Signed-off-by: Adolf Belka <adolf.belka@ipfire.org> Signed-off-by: Michael Tremer <michael.tremer@ipfire.org>
- Update from version 3470200 to 3490100
- Update of rootfile
- Changelog 3490100
Improve portability of makefiles and configure scripts.
Fix a bug in the concat_ws() function, introduced in version 3.44.0, that could
lead to a memory error if the separator string is very large (hundreds of
megabytes).
Enhanced the SQLITE_DBCONFIG_LOOKASIDE interface to make it more robust against
misuse. 3490000
Enhancements to the query planner:
Improve the query-time index optimization so that it works on WITHOUT ROWID
tables.
Better query plans for large star-query joins. This fixes three different
performance regressions that were reported on the SQLite Forum.
When two or more queries have the same estimated cost, use the one with the
fewer bytes per row.
Enhance the iif() SQL function so that it can accept any number of arguments
greater than or equal to two.
Enhance the session extension so that it works on databases that make use of
generated columns.
Omit the SQLITE_USE_STDIO_FOR_CONSOLE compile-time option which was not
implemented correctly and never worked right. In its place add the
SQLITE_USE_W32_FOR_CONSOLE_IO compile-time option. This option applies to
command-line tools like the CLI only, not to the SQLite core. It causes Win32
APIs to be used for console I/O instead of stdio. This option affects Windows
builds only.
Three new options to sqlite3_db_config(). All default to "on".
SQLITE_DBCONFIG_ENABLE_ATTACH_CREATE
SQLITE_DBCONFIG_ENABLE_ATTACH_WRITE
SQLITE_DBCONFIG_ENABLE_COMMENTS
Replace Autotools with Autosetup for the configure script used in the
precompiled amalgamation tarball. The configure script for the canonical
source code was changed to Autosetup in the previous (3.48.0) release. Only
the main SQLite configure script in the amalgamation tarball is changed. The
(deprecated) configuration script use by TEA subdirectory of the amalgamation
tarball still relies on Autotools.
Various minor patches and fixes for problems seen in the 3.48.0 release. 3480000
Refactor the "configure" script used to help build SQLite from canonical
sources, to fix bugs, improve performance, and make the code more maintainable.
This does not affect the "configure" script in the
sqlite3-autoconf-NNNNNNN.tar.gz "amalgamation tarball", only the
canonical sources. The build system for the amalgamation tarball is
unchanged. If you are using the amalgamation tarball, nothing about
this change log entry applies to you.
The key innovation here is that Autosetup is now used instead of GNU
Autoconf. That seems like a big change, but it is really just an
implementation detail. The ./configure script is coded very
differently, but should work the same as before.
One advantage of the new configure is that you no longer need to install
TCL in order to build most SQLite targets. TCL is still required to
run tests or to build accessory programs (like sqlite3_analyzer) that
use TCL, but it is not required for most common targets. Hence, as of
this release, the only build dependencies are a C compiler and "make"
or "nmake".
Improved EXPLAIN QUERY PLAN output for covering indexes.
Allow a two-argument version of the iif() SQL function. Also allow if() as an
alternative spelling for iif().
Add the ".dbtotxt" command to the CLI.
Add the SQLITE_IOCAP_SUBPAGE_READ property to the xDeviceCharacteristics
method of the sqlite3_io_methods object.
Add the SQLITE_PREPARE_DONT_LOG option to sqlite3_prepare_v3() that prevents
warning messages being sent to the error log if the SQL is ill-formed. This
allows sqlite3_prepare_v3() to be used to do test compiles of SQL to check
for validity without polluting the error log with false messages.
Increase the minimum allowed value of SQLITE_LIMIT_LENGTH from 1 to 30.
Added the SQLITE_FCNTL_NULL_IO file control.
Extend the FTS5 auxiliary API xInstToken() to work with prefix queries via the
insttoken configuration option and the fts5_insttoken() SQL function.
Increase the maximum number of arguments to an SQL function from 127 to 1000.
Remove vestigial traces of SQLITE_USER_AUTHENTICATION.
Various obscure bug fixes.
Signed-off-by: Adolf Belka <adolf.belka@ipfire.org> Signed-off-by: Michael Tremer <michael.tremer@ipfire.org>
- Update from version 20241112 to 20250211
- Update of rootfile
- Changelog 20250211
Security updates for INTEL-SA-01166
Security updates for INTEL-SA-01213
Security updates for INTEL-SA-01139
Security updates for INTEL-SA-01228
Security updates for INTEL-SA-01194
Update for functional issues. Refer to Intel® Core™ Ultra Processor for
details.
Update for functional issues. Refer to 13th/14th Generation Intel® Core™
Processor Specification Update for details.
Update for functional issues. Refer to 12th Generation Intel® Core™
Processor Family for details.
Update for functional issues. Refer to 11th Gen Intel® Core™ Processor
Specification Update for details.
Update for functional issues. Refer to 8th and 9th Generation Intel® Core™
Processor Family Spec Update for details.
Update for functional issues. Refer to 5th Gen Intel® Xeon® Scalable
Processors Specification Update for details.
Update for functional issues. Refer to 4th Gen Intel® Xeon® Scalable
Processors Specification Update for details.
Update for functional issues. Refer to 3rd Generation Intel® Xeon®
Processor Scalable Family Specification Update for details.
Update for functional issues. Refer to Intel® Xeon® D-2700 Processor
Specification Update for details.
Update for functional issues. Refer to Intel® Xeon® E-2300 Processor
Specification Update for details.
Update for functional issues. Refer to Intel® Xeon® 6700-Series Processor
Specification Update for details.
Update for functional issues. Refer to Intel® Processors and Intel® Core™
i3 N-Series for details
New Platforms
Processor Stepping F-M-S/PI Old Ver New Ver Products
SRF-SP C0 06-af-03/01 03000330 Xeon 6700-Series Processors with E-Cores
Updated Platforms
Processor Stepping F-M-S/PI Old Ver New Ver Products
ADL C0 06-97-02/07 0000003700000038 Core Gen12
ADL H0 06-97-05/07 0000003700000038 Core Gen12
ADL L0 06-9a-03/80 0000043500000436 Core Gen12
ADL R0 06-9a-04/80 0000043500000436 Core Gen12
ADL-N N0 06-be-00/19 0000001a0000001c Core i3-N305/N300, N50/N97/N100/N200, Atom x7211E/x7213E/x7425E
AZB A0/R0 06-9a-04/40 0000000700000009 Intel(R) Atom(R) C1100
CFL-H R0 06-9e-0d/22 0000010000000102 Core Gen9 Mobile
CFL-H/S/E3 U0 06-9e-0a/22 000000f8000000fa Core Gen8 Desktop, Mobile, Xeon E
EMR-SP A0 06-cf-01/87 2100028321000291 Xeon Scalable Gen5
EMR-SP A1 06-cf-02/87 2100028321000291 Xeon Scalable Gen5
ICL-D B0 06-6c-01/10 010002b0010002c0 Xeon D-17xx, D-27xx
ICX-SP Dx/M1 06-6a-06/87 0d0003e70d0003f5 Xeon Scalable Gen3
RPL-E/HX/S B0 06-b7-01/32 0000012b0000012c Core Gen13/Gen14
RPL-H/P/PX 6+8 J0 06-ba-02/e0 0000412300004124 Core Gen13
RPL-HX/S C0 06-bf-02/07 0000003700000038 Core Gen13/Gen14
RPL-U 2+8 Q0 06-ba-03/e0 0000412300004124 Core Gen13
RPL-S H0 06-bf-05/07 0000003700000038 Core Gen13/Gen14
RKL-S B0 06-a7-01/02 0000006200000063 Core Gen11
SPR-HBM Bx 06-8f-08/10 2c0003902c0003e0 Xeon Max
SPR-SP E4/S2 06-8f-07/87 2b0006032b000620 Xeon Scalable Gen4
SPR-SP E5/S3 06-8f-08/87 2b0006032b000620 Xeon Scalable Gen4
TWL N0 06-be-00/19 0000001a0000001c Core i3-N305/N300, N50/N97/N100/N200, Atom x7211E/x7213E/x7425E
New Disclosures Updated in Prior Releases
Processor Stepping F-M-S/PI Old Ver New Ver Products
CFL-H/S P0 06-9e-0c/22 000000f6000000f8 Core Gen9
Signed-off-by: Adolf Belka <adolf.belka@ipfire.org> Reviewed-by: Michael Tremer <michael.tremer@ipfire.org> Signed-off-by: Michael Tremer <michael.tremer@ipfire.org>
Matthias Fischer [Mon, 10 Feb 2025 14:40:17 +0000 (15:40 +0100)]
apache: Update to 2.4.63
For details see:
https://dlcdn.apache.org/httpd/CHANGES_2.4.63
"Changes with Apache 2.4.63
*) mod_dav: Update redirect-carefully example BrowserMatch config
to match more recent client versions. PR 66148, 67039.
[Michal Maloszewski <michal.maloszewski canonical.com>,
Romain Tartière <romain blogreen.org>]
*) mod_cache_socache: Fix possible crash on error path. PR 69358.
[Ruediger Pluem]
*) mod_ssl: Fail cleanly at startup if OpenSSL initialization fails.
[StephenWall]
*) mod_md: update to version 2.4.31
- Improved error reporting when waiting for ACME server to verify domains
or finalizing the order fails, e.g. times out.
- Increasing the timeouts to wait for ACME server to verify domain names
and issue the certificate from 30 seconds to 5 minutes.
- Change a log level from error to debug when Stapling is enabled but a
certificate carries no OCSP responder URL.
*) mod_proxy_balancer: Fix the handling of the stickysession configuration
parameter by the balancer manager. PR 69510
[Yutaka Tokunou <tokunou.yutaka@fujitsu.com>]
*) Add the ldap-search option to mod_authnz_ldap, allowing authorization
to be based on arbitrary expressions that do not include the username.
Make sure that when ldap searches are too long, we explicitly log the
error. [Graham Leggett]
*) mod_proxy: Honor parameters of ProxyPassMatch workers with substitution
in the host name or port. PR 69233. [Yann Ylavic]
*) mod_log_config: Fix merging for the "LogFormat" directive.
PR 65222. [Michael Kaufmann <mail michael-kaufmann.ch>]
*) mod_md: update to version 2.4.29
- Fixed HTTP-01 challenges to not carry a final newline, as some ACME
server fail to ignore it. [Michael Kaufmann (@mkauf)]
- Fixed missing label+newline in server-status plain text output when
MDStapling is enabled.
*) mod_ssl: Restore support for loading PKCS#11 keys via ENGINE
without "SSLCryptoDevice" configured. [Joe Orton]
*) mod_authnz_ldap: Fix possible memory corruption if the
AuthLDAPSubGroupAttribute directive is configured. [Joe Orton]
*) mod_proxy_fcgi: Don't re-encode SCRIPT_FILENAME when set via SetHandler.
PR 69203. [Yann Ylavic]
*) mod_rewrite, mod_proxy: mod_proxy to canonicalize rewritten [P] URLs,
including "unix:" ones. PR 69235, PR 69260. [Yann Ylavic, Ruediger Pluem]
*) mod_rewrite: Error out in case a RewriteRule in directory context uses the
proxy, but mod_proxy is not loaded. PR 56264.
[Christophe Jaillet, Michael Streeter <mstreeter1@gmail.com>]
*) http: Remove support for Request-Range header sent by Navigator 2-3 and
MSIE 3. [Stefan Fritsch]
*) mod_rewrite: Don't require [UNC] flag to preserve a leading //
added by applying the perdir prefix to the substitution.
[Ruediger Pluem, Eric Covener]
*) Windows: Restore the ability to "Include" configuration files on UNC
paths. PR 69313 [Eric Covener]
*) mod_proxy: Avoid AH01059 parsing error for SetHandler "unix:" URLs
in <Location> (incomplete fix in 2.4.62). PR 69160. [Yann Ylavic]
*) mod_md: update to version 2.4.28
- When the server starts, it looks for new, staged certificates to
activate. If the staged set of files in 'md/staging/<domain>' is messed
up, this could prevent further renewals to happen. Now, when the staging
set is present, but could not be activated due to an error, purge the
whole directory. [icing]
- Fix certificate retrieval on ACME renewal to not require a 'Location:'
header returned by the ACME CA. This was the way it was done in ACME
before it became an IETF standard. Let's Encrypt still supports this,
but other CAs do not. [icing]
- Restore compatibility with OpenSSL < 1.1. [ylavic]
*) mod_tls: removed the experimental module. It now is availble standalone
from https://github.com/icing/mod_tls. The rustls provided API is not
stable and does not align with the httpd release cycle.
[Stefan Eissing]
*) mod_rewrite: Better question mark tracking to avoid UnsafeAllow3F.
PR 69197. [Yann Ylavic, Eric Covener]
*) mod_http2: Return connection monitoring to the event MPM when blocking
on client updates. [Stefan Eissing, Yann Ylavic]"
Signed-off-by: Matthias Fischer <matthias.fischer@ipfire.org> Signed-off-by: Michael Tremer <michael.tremer@ipfire.org>
Matthias Fischer [Mon, 10 Feb 2025 09:03:59 +0000 (10:03 +0100)]
vnstat: Update to 2.13
For details see:
https://humdi.net/vnstat/CHANGES
"- Fixed
- Opening of body html tag was missing on some pages in image output
example cgi (examples/vnstat.cgi)
- New
- Add database data merge support as --merge
- Add --db for specifying database file for queries (vnstat and vnstati)
- Add exit status 2 options to --alert for making it possible to
differentiate alerts from errors (exit status 1)
- Add --dbiflist also to vnstati command
- Image output example cgi (examples/vnstat.cgi) improvements
- Remove dependency to vnstat command
- Add option for selecting how many images are shown per row on the index
page when the database has more than one interface
- Add option for selecting which image output is used on the index page
when the database has more than one interface
- Add options for selecting which interfaces are shown or hidden from the
index page without disabling access to all interface specific page when
the database has more than one interface
- Harmonize layout style between pages"
Signed-off-by: Matthias Fischer <matthias.fischer@ipfire.org> Signed-off-by: Michael Tremer <michael.tremer@ipfire.org>
Michael Tremer [Mon, 3 Feb 2025 20:50:12 +0000 (20:50 +0000)]
vpnmain.cgi: Reduce the number of offered ciphers
For new connections, we will now configure fewer ciphers by default. I
currently do not see any reason why we should support so many different
versions of AES-GCM and AES-128 by default.
The defaults should provide high security as well as decent
compatibility to solutions from other vendors.
I am currently not sure whether ChaCha20-Poly1305 should remain as
default as AES should usually outperform it by far. We can assume that
most hardware has support for AES-NI.
Signed-off-by: Michael Tremer <michael.tremer@ipfire.org>
projects / ipfire-2.x.git / log
