Development December 2023

development@lists.ipfire.org

10 participants
34 discussions

[PATCH] netpbm: Update to version 10.73.43
by Adolf Belka 01 Dec '23

01 Dec '23

- IPFire-3.x - Update from version 10.73.42 to 10.73.43 - Changelog 10.73.43 jpegtopnm: Many fixes to -dumpexif. Always broken. (-dumpexif was new in Netpbm 9.18 (September 2001)) pamtopng: fix -chroma option: always rejected. Always broken. pamtopng was new in Netpbm 10.70 (June 2015). pnmtopng: fix -rgb option: always rejected. Always broken -rgb was new in Netpbm 10.30 (October 2005). Signed-off-by: Adolf Belka <adolf.belka(a)ipfire.org> --- netpbm/netpbm.nm | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/netpbm/netpbm.nm b/netpbm/netpbm.nm index bca23a696..ec2154450 100644 --- a/netpbm/netpbm.nm +++ b/netpbm/netpbm.nm @@ -4,8 +4,8 @@ ############################################################################### name = netpbm -version = 10.73.42 -release = 3 +version = 10.73.43 +release = 1 groups = System/Libraries url = https://netpbm.sourceforge.net/ -- 2.42.1

1 0

[PATCH] newt: Update to version 0.52.24
by Adolf Belka 01 Dec '23

01 Dec '23

- IPFire-3.x - Update from version 0.52.21 to 0.52.24 - Changelog 0.52.24 - add support for python3.13 - fix compiler warnings 0.52.23 - fix automatic height of menu/list in whiptail (broken in 0.52.22) - fix automatic width of whiptail --yesno box - fix automatic width in whiptail with unicode characters - fix automatic width with whiptail --noitem and --notags options - fix spacing with longer tags in whiptail - avoid overlapping backtitle in whiptail with automatic height 0.52.22 - fix crash in whiptail with new libpopt - switch from usleep to nanosleep (Rosen Penev) - fix libnewt.pc to enable static linking (Alexey Sheplyakov) - fix LDFLAGS order in snack linking (Sam James) - use CFLAGS when compiling snack - improve configure.ac (Thomas Kuehne) - install header and libnewt.pc with shared library (Michael Olbrich) Signed-off-by: Adolf Belka <adolf.belka(a)ipfire.org> --- newt/newt.nm | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/newt/newt.nm b/newt/newt.nm index 67612cb94..6c0d52cb0 100644 --- a/newt/newt.nm +++ b/newt/newt.nm @@ -4,8 +4,8 @@ ############################################################################### name = newt -version = 0.52.21 -release = 2 +version = 0.52.24 +release = 1 groups = System/Libraries url = https://fedorahosted.org/releases/n/e/newt/ -- 2.42.1

1 0

[PATCH] openssl: Update to version 3.1.4
by Adolf Belka 01 Dec '23

01 Dec '23

- IPFire-3.x - Update from version 3.1.2 to 3.1.4 - Changelog 3.1.4 * Fix incorrect key and IV resizing issues when calling EVP_EncryptInit_ex2(), EVP_DecryptInit_ex2() or EVP_CipherInit_ex2() with OSSL_PARAM parameters that alter the key or IV length ([CVE-2023-5363]). 3.1.3 * Fix POLY1305 MAC implementation corrupting XMM registers on Windows. The POLY1305 MAC (message authentication code) implementation in OpenSSL does not save the contents of non-volatile XMM registers on Windows 64 platform when calculating the MAC of data larger than 64 bytes. Before returning to the caller all the XMM registers are set to zero rather than restoring their previous content. The vulnerable code is used only on newer x86_64 processors supporting the AVX512-IFMA instructions. The consequences of this kind of internal application state corruption can be various - from no consequences, if the calling application does not depend on the contents of non-volatile XMM registers at all, to the worst consequences, where the attacker could get complete control of the application process. However given the contents of the registers are just zeroized so the attacker cannot put arbitrary values inside, the most likely consequence, if any, would be an incorrect result of some application dependent calculations or a crash leading to a denial of service. ([CVE-2023-4807]) Signed-off-by: Adolf Belka <adolf.belka(a)ipfire.org> --- openssl/openssl.nm | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/openssl/openssl.nm b/openssl/openssl.nm index 6d5d21863..19214a8e9 100644 --- a/openssl/openssl.nm +++ b/openssl/openssl.nm @@ -4,8 +4,8 @@ ############################################################################### name = openssl -version = 3.1.2 -release = 2 +version = 3.1.4 +release = 1 maintainer = Michael Tremer <michael.tremer(a)ipfire.org> groups = System/Libraries -- 2.42.1

1 0

[PATCH 1/2] tor.cgi: Fixes deprecated tor option 'ExitNode' to 'ExitNodes'
by Erik Kapfer 01 Dec '23

01 Dec '23

If fingerprints in the Exit Node section are in usage, tor.cgi prints the deprecated option 'ExitNode' into torrc which leads to the following warning "The abbreviation ‘ExitNode’ is deprecated. Please use ‘ExitNodes’ instead". Fix has been found and tested in the community for reference please see --> https://community.ipfire.org/t/the-abbreviation-exitnode-is-deprecated-plea… Signed-off-by: Erik Kapfer <erik.kapfer(a)ipfire.org> --- html/cgi-bin/tor.cgi | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/html/cgi-bin/tor.cgi b/html/cgi-bin/tor.cgi index 75fdf0d5d..9aa2bc95a 100644 --- a/html/cgi-bin/tor.cgi +++ b/html/cgi-bin/tor.cgi @@ -790,7 +790,7 @@ sub BuildConfiguration() { my @nodes = split(",", $settings{'TOR_USE_EXIT_NODES'}); foreach (@nodes) { - print FILE "ExitNode $_\n"; + print FILE "ExitNodes $_\n"; } } -- 2.42.0

3 4

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

Development December 2023