Development September 2024

development@lists.ipfire.org

7 participants
29 discussions

[PATCH] header.pl: only get memory consumption when service is running
by Robin Roevens 10 Sep '24

10 Sep '24

It probably doesn't matter much as the get_memory_consumption function just returns 0 when no pids are found. But it shouldn't even try as the mem var is never used when the service is not running. --- config/cfgroot/header.pl | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/config/cfgroot/header.pl b/config/cfgroot/header.pl index a90a6f481..3778c4e59 100644 --- a/config/cfgroot/header.pl +++ b/config/cfgroot/header.pl @@ -950,9 +950,6 @@ EOF @pids = &General::find_pids("${process}"); } - # Get memory consumption - my $mem = &General::get_memory_consumption(@pids); - print <<EOF; <tr> <th scope="row"> @@ -962,6 +959,9 @@ EOF # Running? if (scalar @pids) { + # Get memory consumption + my $mem = &General::get_memory_consumption(@pids); + # Format memory $mem = &General::formatBytes($mem); -- 2.46.0

1 0

[PATCH] zabbix_agentd: Add IPFire services.get item
by Robin Roevens 10 Sep '24

10 Sep '24

Hi all, This patch introduces again the ability for Zabbix to get information about the running IPFire services. This functionality was already submitted a long while ago but was rejected because the perl script behind it contained the same 'ugly code' as services.cgi contained back then. Meanwhile the code of services.cgi was updated by both me, adding more generic addon services discovery using new pakfire functions, and more recently by Michael with new general functions for finding pids and memory consumption of services. So I now refactored my services-discovery-perl-script, that will be used by the zabbix-agent if the Zabbix server requests services information, to use the same methods as currently used in services.cgi, using those new functions, hoping that this feature now can be accepted into IPFire. Note: I don't change the PAKVER in this patch, which should not be needed if this patch is applyed shortly after my previous patch updating zabbix_agentd to v6.0.33 Regards Robin

1 1

[PATCH] zabbix_agentd: Update to 6.0.33 (LTS)
by Robin Roevens 10 Sep '24

10 Sep '24

- Update from version 6.0.30 to 6.0.33 - Update of rootfile not required Bugs fixed: - ZBX-20766: Fixed confusing port binding error message - ZBX-24391: Fixed Zabbix agent to return net.tcp.socket.count result without error if IPv6 is disabled Full changelogs since 6.0.30: - https://www.zabbix.com/rn/rn6.0.31 - https://www.zabbix.com/rn/rn6.0.32 - https://www.zabbix.com/rn/rn6.0.33 --- lfs/zabbix_agentd | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/lfs/zabbix_agentd b/lfs/zabbix_agentd index 06956ad41..55abd609a 100644 --- a/lfs/zabbix_agentd +++ b/lfs/zabbix_agentd @@ -26,7 +26,7 @@ include Config SUMMARY = Zabbix Agent -VER = 6.0.30 +VER = 6.0.33 THISAPP = zabbix-$(VER) DL_FILE = $(THISAPP).tar.gz @@ -34,7 +34,7 @@ DL_FROM = $(URL_IPFIRE) DIR_APP = $(DIR_SRC)/$(THISAPP) TARGET = $(DIR_INFO)/$(THISAPP) PROG = zabbix_agentd -PAK_VER = 13 +PAK_VER = 14 DEPS = fping @@ -48,7 +48,7 @@ objects = $(DL_FILE) $(DL_FILE) = $(DL_FROM)/$(DL_FILE) -$(DL_FILE)_BLAKE2 = 5446a15c5fa3400d78eef47cced6cbd0bc884b6b1f14e267321f562b5891e21de41179bb615a733b49ee0ae334aadede32d931db400b9148ec9bc6636ac71e5a +$(DL_FILE)_BLAKE2 = 736c5b46193e7e7f93dfa00eb56c65fdf3fa6e36a647d0f910118923950114dbbbe9382563e96db4d8ee6199b4e0342037fb8ec6ec8d349884612f5ef18db966 install : $(TARGET) -- 2.46.0

1 0

Addressing #13764
by Michael Tremer 10 Sep '24

10 Sep '24

this a patchset that addresses a bug reported by Dan as #13764. Suricata and/or NFQUEUE end up in some undefined behaviour where packets will be accepted when Suricata goes away (in this case it is being killed by the OOM killer). This results in the firewall exposing all ports on all interfaces which is a serious problem. Although we actually configure the queue to simply bypass (as in no longer enqueue) packets when Suricata dies, the kernel always seems to end up in this scenario. We cannot prevent that Suricata might die, but we will have to make sure that the firewall does not change behaviour. This is now being done by moving the IPS to the mangle table. The behaviour will be the same, but an ACCEPT action on the mangle table will not accept the packet, it will just terminate processing traffic in that table. We further ensure that this is not going to be a problem by moving the NFQUEUE rule to the end. If it is being skipped, this is not a problem as we will only stop processing packets which won't be a problem as Suricata has gone away anyways. I believe that this is a better way to integrate Suricata, but it will change the behaviour of the firewall in that sense that the IPS is now the first thing that will see a packet. The location filter, IP blocklists and so on will all come after. I personally do not consider this a problem, but I wanted to make sure this is documented. We now make more use of marking packets which might need to be benchmarked in order to ensure that this is not introducing any performance penalty. Furthermore this patchset adds support for WireGuard and made some improvements on the web UI which used some broken tables and a lot of empty space on the screen. Please test this and give me feedback if these changes introduce any regressions. I believe we want to release this with c189. Best, -Michael

1 20

[PATCH] openvpn: Update to version 2.5.10
by Adolf Belka 07 Sep '24

07 Sep '24

- Update from version 2.5.9 to 2.5.10 - Update of rootfile not required - 3 CVE Fixes in this version but all are for Windows installations. - Changelog 2.5.10 Security fixes - CVE-2024-27459: Windows: fix a possible stack overflow in the interactive service component which might lead to a local privilege escalation. Reported-by: Vladimir Tokarev <vtokarev(a)microsoft.com> - CVE-2024-24974: Windows: disallow access to the interactive service pipe from remote computers. Reported-by: Vladimir Tokarev <vtokarev(a)microsoft.com> - CVE-2024-27903: Windows: disallow loading of plugins from untrusted installation paths, which could be used to attack openvpn.exe via a malicious plugin. Plugins can now only be loaded from the OpenVPN install directory, the Windows system directory, and possibly from a directory specified by HKLM\SOFTWARE\OpenVPN\plugin_dir. Reported-by: Vladimir Tokarev <vtokarev(a)microsoft.com> User visible changes - License amendment: all NEW commits fall under a modified license that explicitly permits linking with Apache2 libraries (mbedTLS, OpenSSL) - see COPYING for details. Existing code in the release/2.5 branch will not been relicensed (only in release/2.6 and later branches). Signed-off-by: Adolf Belka <adolf.belka(a)ipfire.org> --- lfs/openvpn | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/lfs/openvpn b/lfs/openvpn index b686cc930..807019f0a 100644 --- a/lfs/openvpn +++ b/lfs/openvpn @@ -1,7 +1,7 @@ ############################################################################### # # # IPFire.org - A linux based firewall # -# Copyright (C) 2007-2023 IPFire Team <info(a)ipfire.org> # +# Copyright (C) 2007-2024 IPFire Team <info(a)ipfire.org> # # # # This program is free software: you can redistribute it and/or modify # # it under the terms of the GNU General Public License as published by # @@ -24,7 +24,7 @@ include Config -VER = 2.5.9 +VER = 2.5.10 THISAPP = openvpn-$(VER) DL_FILE = $(THISAPP).tar.gz @@ -40,7 +40,7 @@ objects = $(DL_FILE) $(DL_FILE) = $(DL_FROM)/$(DL_FILE) -$(DL_FILE)_BLAKE2 = e5110ebb9149121c11de45f085f66d30a89fb674ad96c5792d83b16dc29c95215a91e682adb3c800b91ed4d88d6d24b5bcae0799cdb855a284832f0668ffcb82 +$(DL_FILE)_BLAKE2 = 7f4ae82162e2e48e66df2da8008f45a2db53a22483730808b873948f1dc13a2e5582c79e4469f9d794f8b0f87f08d627e8d1bd070b088ea33444af31779f5479 install : $(TARGET) -- 2.46.0

1 0

Feedback on WG
by Adolf Belka 07 Sep '24

07 Sep '24

Hi Michael, Sorry for the delay with feedback on the WG testing. I was a bit tied up with DIY stuff in the house. By manually importing the WG config file created I was able to successfully connect from my laptop to my IPFire vm system. The WUI showed connected. The config file had my allowed subnets set as 192.168.200.0/255.255.255.0 which is the green subnet on my vm system. However trying ping over the WG tunnel gave failures for the IP of the vm machine, green1, and also for the green interface of the vm IPFire. Trying to ping with the FQDN for the green1 system resulted in no resolving of green1's FQDN to a local IP but tried to send it to my main red interface with my ISP. So something appears to be missing or incorrect with the routing but not sure what. Minor points on the WUI. When disconnected the status section that is coloured red is huge and the space for the remark is very small but when connected then the status space is large enough to have the connected status word, giving much more room for the remark. When the WG config file is created and you have the page with the QR code, there is also a message about the WG config file only being shown this one time as it contains private key material. The message is fine but the heading for the message is "Oops, something went wrong...". It should really be something like "Information Note" or equivalent as it is not an actual error message. See the screenshots attached. Regards, Adolf.

2 16

Bug patch submissions waiting for review
by Adolf Belka 06 Sep '24

06 Sep '24

Hi Michael, Here are the bugs that I have supplied patch fixes for that require a review. https://bugzilla.ipfire.org/show_bug.cgi?id=13029 https://bugzilla.ipfire.org/show_bug.cgi?id=13074 https://bugzilla.ipfire.org/show_bug.cgi?id=13762 Regards, Adolf -- Sent from my laptop

1 0

[PATCH] sudo: Update to version 1.9.16
by Adolf Belka 05 Sep '24

05 Sep '24

- Update from version 1.9.15p5 to 1.9.16 - Update of rootfile - Changelog 1.9.16 * Added the "cmddenial_message" sudoers option to provide additional information to the user when a command is denied by the sudoers policy. The default message is still displayed. * The time stamp used for file-based logs is now more consistent with the time stamp produced by syslog. GitHub issues #327. * Sudo will now warn the user if it can detect the user's terminal but cannot determine the path to the terminal device. The sudoers time stamp file will now use the terminal device number directly. GitHub issue #329. * The embedded copy of zlib has been updated to version 1.3.1. * Improved error handling if generating the list of signals and signal names fails at build time. * Fixed a compilation issue on Linux systems without process_vm_readv(). * Fixed cross-compilation with WolfSSL. * Added a "json_compact" value for the sudoers "log_format" option which can be used when logging to a file. The existing "json" value has been aliased to "json_pretty". In a future release, "json" will be an alias for "json_compact". GitHub issue #357. * A new "pam_silent" sudoers option has been added which may be negated to avoid suppressing output from PAM authentication modules. GitHub issue #216. * Fixed several cvtsudoers JSON output problems. GitHub issues #369, #370, #371, #373, #381. * When sudo runs a command in a pseudo-terminal and the user's terminal is revoked, the pseudo-terminal's foreground process group will now receive SIGHUP before the terminal is revoked. This emulates the behavior of the session leader exiting and is consistent with what happens when, for example, an ssh session is closed. GitHub issue #367. * Fixed "make test" with Python 3.12. GitHub issue #374. * In schema.ActiveDirectory, fixed the quoting in the example command. GitHub issue #376. * Paths specified via a Chdir_Spec or Chroot_Spec in sudoers may now be double-quoted. * Sudo insults are now included by default, but disabled unless the --with-insults configure option is specified or the "insults" sudoers option is enabled. * The default sudoers file now enables the "secure_path" option by default and preserves the EDITOR, VISUAL, and SUDO_EDITOR environment variables when running visudo. The new --with-secure-path-value configure option can be used to set the value of "secure_path" in the default sudoers file. GitHub issue #387. * A sudoers schema for IBM Directory Server (aka IBM Tivoli Directory Server, IBM Security Directory Server, and IBM Security Verify Directory) is now included. * When cross-compiling sudo, the configure script now assumes that the snprintf() function is C99-compliant if the C compiler supports the C99 standard. Previously, configure would use sudo's own snprintf() when cross-compiling. GitHub issue #386. Signed-off-by: Adolf Belka <adolf.belka(a)ipfire.org> --- config/rootfiles/common/sudo | 1 + lfs/sudo | 6 +++--- 2 files changed, 4 insertions(+), 3 deletions(-) diff --git a/config/rootfiles/common/sudo b/config/rootfiles/common/sudo index a09f06b38..651a284e3 100644 --- a/config/rootfiles/common/sudo +++ b/config/rootfiles/common/sudo @@ -75,6 +75,7 @@ usr/sbin/visudo #usr/share/locale/hu/LC_MESSAGES/sudo.mo #usr/share/locale/hu/LC_MESSAGES/sudoers.mo #usr/share/locale/id/LC_MESSAGES/sudo.mo +#usr/share/locale/id/LC_MESSAGES/sudoers.mo #usr/share/locale/it/LC_MESSAGES/sudo.mo #usr/share/locale/it/LC_MESSAGES/sudoers.mo #usr/share/locale/ja/LC_MESSAGES/sudo.mo diff --git a/lfs/sudo b/lfs/sudo index 129e41e9f..cac540be0 100644 --- a/lfs/sudo +++ b/lfs/sudo @@ -1,7 +1,7 @@ ############################################################################### # # # IPFire.org - A linux based firewall # -# Copyright (C) 2007-2023 IPFire Team <info(a)ipfire.org> # +# Copyright (C) 2007-2024 IPFire Team <info(a)ipfire.org> # # # # This program is free software: you can redistribute it and/or modify # # it under the terms of the GNU General Public License as published by # @@ -24,7 +24,7 @@ include Config -VER = 1.9.15p5 +VER = 1.9.16 THISAPP = sudo-$(VER) DL_FILE = $(THISAPP).tar.gz @@ -40,7 +40,7 @@ objects = $(DL_FILE) $(DL_FILE) = $(DL_FROM)/$(DL_FILE) -$(DL_FILE)_BLAKE2 = 73ee598c2a2848d5be24f97492b13eba2f326c514799220e43a1aeafc6692224a7555fb7cc0a96a2720751d3e4d98e752804db589ac3c1476f24e71f5b9bc720 +$(DL_FILE)_BLAKE2 = 19daa789af3ca2c4832950f0dd6f26a97285fdc155f0d7c18ec1f1accafce9b86f2f5730d3bb0b8e7717c0c55f4079928e03acb3974cb2652c58d4bcb2f74a12 install : $(TARGET) -- 2.46.0

1 0

[PATCH] dhcpcd: Update to version 10.0.10
by Adolf Belka 05 Sep '24

05 Sep '24

- Update from version 10.0.8 to 10.0.10 - Update of rootfile not required - Patch for free selection of MTU has been removed as in version 10.0.9 the MTU code was changed to not apply limits to it. - Changelog 10.0.10 Reversion of commit "linux: make if_getnetworknamespace static" 10.0.9 Option 2: Fix stdin parsing by @holmanb in #289 IPv4LL: Restart ARP probling on address conflict by @LeoRuan in #340 DHCP: Handle option 108 correctly when receiving 0.0.0.0 OFFER by @taoyl-g in #342 DHCP: No longer set interface mtu by @rsmarples in #346 Update privsep-linux.c to allow statx by @Jabrwock in #349 Signed-off-by: Adolf Belka <adolf.belka(a)ipfire.org> --- lfs/dhcpcd | 5 +-- ...ow-free-selection-of-MTU-by-the-user.patch | 44 ------------------- 2 files changed, 2 insertions(+), 47 deletions(-) delete mode 100644 src/patches/dhcpcd-10.0.2-Allow-free-selection-of-MTU-by-the-user.patch diff --git a/lfs/dhcpcd b/lfs/dhcpcd index 3bac681d8..10b7b0212 100644 --- a/lfs/dhcpcd +++ b/lfs/dhcpcd @@ -24,7 +24,7 @@ include Config -VER = 10.0.8 +VER = 10.0.10 THISAPP = dhcpcd-$(VER) DL_FILE = $(THISAPP).tar.xz @@ -40,7 +40,7 @@ objects = $(DL_FILE) $(DL_FILE) = $(DL_FROM)/$(DL_FILE) -$(DL_FILE)_BLAKE2 = 1bf27387c13f192c6216e2f1ecad06bfa82267d5d6e08ddaa123789699fe9154222c33b1aa1f603e65ae8dce510cb24d48e72701494e0793c766e81f024f8bc5 +$(DL_FILE)_BLAKE2 = 2ecf52009f3fd4442863e1927a8d9e777ee6f34ff4d50a6f1e67821fb23fd12221df1e3a0a04ea0874df8feac15785772b4aa75af407f74448e442db36410e30 install : $(TARGET) @@ -70,7 +70,6 @@ $(subst %,%_BLAKE2,$(objects)) : $(TARGET) : $(patsubst %,$(DIR_DL)/%,$(objects)) @$(PREBUILD) @rm -rf $(DIR_APP) && cd $(DIR_SRC) && tar axf $(DIR_DL)/$(DL_FILE) - cd $(DIR_APP) && patch -Np1 < $(DIR_SRC)/src/patches/dhcpcd-10.0.2-Allow-free-selection-of-MTU-by-the-user.patch cd $(DIR_APP) && ./configure \ --prefix="" \ --sysconfdir=/var/ipfire/dhcpc \ diff --git a/src/patches/dhcpcd-10.0.2-Allow-free-selection-of-MTU-by-the-user.patch b/src/patches/dhcpcd-10.0.2-Allow-free-selection-of-MTU-by-the-user.patch deleted file mode 100644 index 69a35daf5..000000000 --- a/src/patches/dhcpcd-10.0.2-Allow-free-selection-of-MTU-by-the-user.patch +++ /dev/null @@ -1,44 +0,0 @@ -From 1acff721a3874a74efc9921a1e07bd48bd7efab0 Mon Sep 17 00:00:00 2001 -From: Michael Tremer <michael.tremer(a)ipfire.org> -Date: Tue, 22 Feb 2022 12:07:15 +0000 -Subject: [PATCH] Allow free selection of MTU by the user - -Various ISPs (or equipment?) seem to hand out an MTU of only 576 bytes. -Hwoever, this does not seem to be intentional which is why we would like -to manually overwrite this in the configuration. - -dhcpcd only allows setting a maximum MTU of 1472 bytes which does not -seem to have any rationale (any more). Although Ethernet might limit any -MTU to less, IPv6 and IPv4 support MTUs of up to 64KiB. - -This patch allows the user to configure the MTU freely with providing -some sanity check. - -Signed-off-by: Michael Tremer <michael.tremer(a)ipfire.org> ---- - src/dhcp-common.h | 9 +++++---- - 1 file changed, 5 insertions(+), 4 deletions(-) - -diff --git a/src/dhcp-common.h b/src/dhcp-common.h -index a82fcd4c..d6620822 100644 ---- a/src/dhcp-common.h -+++ b/src/dhcp-common.h -@@ -46,10 +46,11 @@ - #define NS_MAXLABEL MAXLABEL - #endif - --/* Max MTU - defines dhcp option length */ --#define IP_UDP_SIZE 28 --#define MTU_MAX 1500 - IP_UDP_SIZE --#define MTU_MIN 576 + IP_UDP_SIZE -+/* Max/Min MTU */ -+#define MTU_MAX 65536 -+#define MTU_MIN 576 -+ -+#define IP_UDP_SIZE 28 - - #define OT_REQUEST (1 << 0) - #define OT_UINT8 (1 << 1) --- -2.30.2 - -- 2.46.0

1 0

[PATCH] clamav: Update to version 1.3.2
by Adolf Belka 05 Sep '24

05 Sep '24

- Update from version 1.3.1 to 1.3.2 - Update of rootfile - 2 CVE Fixes - Changelog 1.3.2 - [CVE-2024-20506](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-205…: Changed the logging module to disable following symlinks on Linux and Unix systems so as to prevent an attacker with existing access to the 'clamd' or 'freshclam' services from using a symlink to corrupt system files. This issue affects all currently supported versions. It will be fixed in: - 1.4.1 - 1.3.2 - 1.0.7 - 0.103.12 Thank you to Detlef for identifying this issue. - [CVE-2024-20505](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-205…: Fixed a possible out-of-bounds read bug in the PDF file parser that could cause a denial-of-service (DoS) condition. This issue affects all currently supported versions. It will be fixed in: - 1.4.1 - 1.3.2 - 1.0.7 - 0.103.12 Thank you to OSS-Fuzz for identifying this issue. - Removed unused Python modules from freshclam tests including deprecated 'cgi' module that is expected to cause test failures in Python 3.13. - Fix unit test caused by expiring signing certificate. - Backport of [GitHub pull request](https://github.com/Cisco-Talos/clamav/pull/1305) - Fixed a build issue on Windows with newer versions of Rust. Also upgraded GitHub Actions imports to fix CI failures. Fixes courtesy of liushuyu. - Backport of [GitHub pull request](https://github.com/Cisco-Talos/clamav/pull/1307) - Fixed an unaligned pointer dereference issue on select architectures. Fix courtesy of Sebastian Andrzej Siewior. - Backport of [GitHub pull request](https://github.com/Cisco-Talos/clamav/pull/1293) - Fixes to Jenkins CI pipeline. For details, see [GitHub pull request](https://github.com/Cisco-Talos/clamav/pull/1330) Signed-off-by: Adolf Belka <adolf.belka(a)ipfire.org> --- config/rootfiles/packages/clamav | 4 ++-- lfs/clamav | 6 +++--- 2 files changed, 5 insertions(+), 5 deletions(-) diff --git a/config/rootfiles/packages/clamav b/config/rootfiles/packages/clamav index 2c7242d7e..f8deb9479 100644 --- a/config/rootfiles/packages/clamav +++ b/config/rootfiles/packages/clamav @@ -105,14 +105,13 @@ usr/sbin/clamd #usr/share/doc/ClamAV/html/images #usr/share/doc/ClamAV/html/images/change-fork-name.png #usr/share/doc/ClamAV/html/images/cisco.png +#usr/share/doc/ClamAV/html/images/clamav-git-workflow.png #usr/share/doc/ClamAV/html/images/clone-your-fork.png #usr/share/doc/ClamAV/html/images/create-a-fork.png #usr/share/doc/ClamAV/html/images/demon.png #usr/share/doc/ClamAV/html/images/flamegraph.svg #usr/share/doc/ClamAV/html/images/fork-is-behind.png #usr/share/doc/ClamAV/html/images/logo.png -#usr/share/doc/ClamAV/html/images/new-git-workflow.png -#usr/share/doc/ClamAV/html/images/old-git-workflow.png #usr/share/doc/ClamAV/html/index.html #usr/share/doc/ClamAV/html/manual #usr/share/doc/ClamAV/html/manual/Development @@ -163,6 +162,7 @@ usr/sbin/clamd #usr/share/doc/ClamAV/html/manual/Usage/Scanning.html #usr/share/doc/ClamAV/html/manual/Usage/Services.html #usr/share/doc/ClamAV/html/manual/Usage/SignatureManagement.html +#usr/share/doc/ClamAV/html/manual/cisco-talos.gpg #usr/share/doc/ClamAV/html/mark.min.js #usr/share/doc/ClamAV/html/mode-rust.js #usr/share/doc/ClamAV/html/print.html diff --git a/lfs/clamav b/lfs/clamav index 32b4aa4f9..f98d52532 100644 --- a/lfs/clamav +++ b/lfs/clamav @@ -26,7 +26,7 @@ include Config SUMMARY = Antivirus Toolkit -VER = 1.3.1 +VER = 1.3.2 THISAPP = clamav-$(VER) DL_FILE = $(THISAPP).tar.gz @@ -34,7 +34,7 @@ DL_FROM = $(URL_IPFIRE) DIR_APP = $(DIR_SRC)/$(THISAPP) TARGET = $(DIR_INFO)/$(THISAPP) PROG = clamav -PAK_VER = 72 +PAK_VER = 73 DEPS = @@ -50,7 +50,7 @@ objects = $(DL_FILE) $(DL_FILE) = $(DL_FROM)/$(DL_FILE) -$(DL_FILE)_BLAKE2 = 49fc5f2f9b4497c095c4d19f86ebcdbcd49cac0e1355c0dbaba8bd56cbbc5af94404b6e6b04fbfb5e3d4364b7ff110b8461f93ba485ddc3f6b56cd86dbe4b362 +$(DL_FILE)_BLAKE2 = 65f5e951a0c8b506e4975a7f5ffcf2c0402907ac528075362efd39fece1325ca05127b89a8ae7dcb638577b441af20aed7ab233e5b73d33f5daa0f793e6416e8 install : $(TARGET) -- 2.46.0

1 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

Development September 2024