Development January 2024

development@lists.ipfire.org

12 participants
48 discussions

Test of mail list
by Adolf Belka 11 Jan '24

11 Jan '24

This is a test mail to see if individual named mails are delivered because my dev mailing list mails are not getting into the mail archive when I look online. Regards, Adolf. -- Sent from my laptop

2 4

Launching our new website
by Michael Tremer 10 Jan '24

10 Jan '24

Hello everyone, (yes, yes, I am still alive…) I would like to pre-announce our new website which Rico and I have been working on over the last couple of months, and collect some final feedback before we roll it out as soon as possible. So here is an outline of what has happened and what will happen next: * Rico has helped me to implement a fresh design for our website which has been drafted by another friend. The goals were to get rid of the sad and grey website, which is also *way* too simplistic, and create something that is nice looking, memorable, and brings people in. * During that journey, we have waved goodbye to Bootstrap which is hard to work with once you have discovered Bulma (https://bulma.io/), our new CSS framework of choice. We have also rewritten and refactored some parts of the backend code. There is now less Javascript and less CSS - and I am sure that we could actually still go and save a lot more. * One of the biggest rewrites is fireinfo, as with a growing number of profiles, our PostgreSQL database started to suffer. We haven’t tested this in full production, yet, but I am sure this will be a lot faster than the older version. This all only affects how we store the data and nothing changes for the clients or users. * We have upgraded the PostgreSQL driver from psycopg2 to psycopg3, and we use async programming a lot more where possible (these are all lessons learned from the build service). * We have replaced memcached with redis. Not because memcache didn’t do its job well, but rather because of the reason that we have both in our infrastructure and it is a little bit easier to just deploy one. * There is a new integration with Asterisk to see current calls - previously the phone stuff didn’t work at all any more since we replaced FreePBX with Asterisk. But that is enough about the technical stuff… Let’s talk about what has visually changed, and why: * First of all, we have brighter colours. Very bright! Because we are a fun project! The grey used to depress me slightly and if you ask a designer what would represent us as a community, you get this. I am a lot happier with that. * The tux is gone. This is kind of a bitter sweet moment, but the old IPFire “logo” is gone with this. I am sure it will be found here or there in a couple of places, but there is no way to make something ancient like this work with something modern-looking. I spent days together with professionals to draft a new logo, and we got nothing, well, apart from the simple things that is: IPFire_ * IPFire_ is not supposed to replace the word “IPFire” in texts, but I think it is a nice way to highlight the nerdiness/console people/Linux things without becoming complex to understand, or confusing to the corporate people… * On top of the front page, we finally have some mission statement: More Than A Firewall. We need to talk more about what we are and what we can do, and we need to explain (I don’t know why, but we do) to people what opportunities IPFire can open for them. This still needs a lot of work and I am happy to hear any ideas what is a nice way to communicate what IPFire is to new people using as few words as possible. * Then, there are a couple of new pages: One of the bigger ones is the About page that explains in more detail what IPFire does (which is why it feels hard to repeat the same on the front page) and it has a large list of (hopefully) all features that IPFire can do/supports/etc. This needs to be updated with every core update, so please let me know if there is something missing in the future as I will probably miss them. Additionally, we have a section with us, the team. Being a faceless project is not very good to attract more people joining our missing, and here is now the place where people will see us for the first time - the people who make IPFire happen. * The download page has mainly been made shorter and now includes the change log. Cloud providers have been added to an extra page. If you know of any cloud providers that support IPFire, please let me know. Torrent downloads are gone. * Help: The help page has always been a hard one for me. This time it contains a sentence or two that explains what all those things are good for :) Let’s see how that is going to work out… * This is a big one: We are getting rid of the thousand subdomains that we are having. There is no more wiki.ipfire.org <http://wiki.ipfire.org/>, blog.ipfire.org <http://blog.ipfire.org/>, people.ipfire.org <http://people.ipfire.org/>, location.ipfire.org <http://location.ipfire.org/>, and so on (exceptions do apply of course). Everything is now in one place: ipfire.org <http://ipfire.org/>. The blog is a subsection of the website, people register accounts on the main page, log in, the documentation has moved there as well. This should hopefully make everyone happy who for a long time wanted buttons to change from one thing to the next here. Here it finally is! * But there isn’t enough space for everything on the main navigation bar. So at the bottom of the page, there is an extra link called “Sitemap” with all the other things that didn’t get a large link. There is a lot of development stuff on there, too. * When logged in, the users area is a bit tidier and hopefully we are able to bring a couple more features to this in the future… * Since users might also be logged in on the main page/the blog/etc. we show “join us now” and “subscribe to our newsletter” only when people have not already done so, which makes it a lot more obvious what the next step of action for users is and a lot less confusing for the people who have already done so. * There has been a large list of bugs/feature requests submitted by a number of people who have been fixed in this. We might have introduced a couple of new ones, so please file a ticket in Bugzilla if something is broken and that needs fixing. All in all we hope that this is a big first step to make IPFire appear the modern distribution that it is, instead of having the dark image of some coders in their basements. To summarise this all in one email feels very short for all the labour that we have put into this over the years, but I suppose it is a good sign to have simplicity in the end. We would like to ask you now for your feedback on all of this. I know that many of you have seen this before, but please help us to double check, that a big launch does not become an embarrassment for some tiny reason :) We have taken some risky decisions and we are happy to see how they are turning out… The new website is currently running at https://www.michael.dev.ipfire.org/ to get to things like fireinfo, just change the subdomain like so https://fireinfo.michael.dev.ipfire.org/. A couple of things like editing your own profile won’t work because the development instance can’t write to our LDAP system, but apart from that, things should be running just fine. I am exciting to hear some feedback and hopefully we can build a small roadmap out of it for the future! Best, -Michael & Rico

4 16

[PATCH v2 1/4] optionsfw.cgi: Fix bug12981 - Add option to log or not log dropped hostile traffic
by Adolf Belka 10 Jan '24

10 Jan '24

- Added option with drop hostile section to decide if the dropped traffic should be logged or not. Fixes: bug12981 Tested-by: Adolf Belka <adolf.belka(a)ipfire.org> Signed-off-by: Adolf Belka <adolf.belka(a)ipfire.org> --- html/cgi-bin/optionsfw.cgi | 13 +++++++++++++ 1 file changed, 13 insertions(+) diff --git a/html/cgi-bin/optionsfw.cgi b/html/cgi-bin/optionsfw.cgi index fbff67b2f..a2a0058f7 100644 --- a/html/cgi-bin/optionsfw.cgi +++ b/html/cgi-bin/optionsfw.cgi @@ -94,6 +94,9 @@ if (!$settings{'DROPSPOOFEDMARTIAN'}) { if (!$settings{'DROPHOSTILE'}) { $settings{'DROPHOSTILE'} = 'off'; } +if (!$settings{'LOGDROPHOSTILE'}) { + $settings{'LOGDROPHOSTILE'} = 'on'; +} if (!$settings{'LOGDROPCTINVALID'}) { $settings{'LOGDROPCTINVALID'} = 'on'; } @@ -125,6 +128,9 @@ $checked{'DROPSPOOFEDMARTIAN'}{$settings{'DROPSPOOFEDMARTIAN'}} = "checked='chec $checked{'DROPHOSTILE'}{'off'} = ''; $checked{'DROPHOSTILE'}{'on'} = ''; $checked{'DROPHOSTILE'}{$settings{'DROPHOSTILE'}} = "checked='checked'"; +$checked{'LOGDROPHOSTILE'}{'off'} = ''; +$checked{'LOGDROPHOSTILE'}{'on'} = ''; +$checked{'LOGDROPHOSTILE'}{$settings{'LOGDROPHOSTILE'}} = "checked='checked'"; $checked{'LOGDROPCTINVALID'}{'off'} = ''; $checked{'LOGDROPCTINVALID'}{'on'} = ''; $checked{'LOGDROPCTINVALID'}{$settings{'LOGDROPCTINVALID'}} = "checked='checked'"; @@ -279,6 +285,13 @@ END <input type='radio' name='DROPSPOOFEDMARTIAN' value='off' $checked{'DROPSPOOFEDMARTIAN'}{'off'} /> $Lang::tr{'off'} </td> </tr> + <tr> + <td align='left' width='60%'>$Lang::tr{'log drop hostile'}</td> + <td align='left'> + $Lang::tr{'on'} <input type='radio' name='LOGDROPHOSTILE' value='on' $checked{'LOGDROPHOSTILE'}{'on'} />/ + <input type='radio' name='LOGDROPHOSTILE' value='off' $checked{'LOGDROPHOSTILE'}{'off'} /> $Lang::tr{'off'} + </td> + </tr> </table> <br/> -- 2.43.0

1 3

Re: Launching our new website
by Michael Tremer 09 Jan '24

09 Jan '24

Hello Tom, Thank you for your feedback! > On 4 Jan 2024, at 23:44, Tom Rymes <tom(a)rymes.net> wrote: > > I really like it at first glance, though the red used in the banner on this page (and I think it’s all over the place, I just didn’t confirm) is too close to magenta to my eyes. It’s bright, but more tropical flower than fire, IMHO (it clashes a bit with the fire video on the homepage). Is it a bad thing to be close to magenta? The colour is not meant to represent fire. It is just, that for a firewall, we are generally in the “red” section instead of blue or green. There are some companies that have tried it, and I don’t think it has worked well. Then, people have done the “blood red” approach, and to distinguish ourselves we used to have a darker (kind of maroon) red. And since I found that depressing, I thought that we could rather go lighter… and this is the result. The fire video didn’t come from the designer and he was slightly opposed to it :) The red should however never be right next to the video. > https://www.michael.dev.ipfire.org/downloads/ipfire-2.27-core182 What I did get as negative feedback before was that the red is quite bright (as in: burns your eyes). I use Apple devices which have generally good colour representation and this feedback came from people that didn’t have calibrated screens (brightness and contrast up all the way). -Michael > > Tom > >> On Jan 4, 2024, at 11:44 AM, Michael Tremer <michael.tremer(a)ipfire.org> wrote: >> >> Hello everyone, >> >> (yes, yes, I am still alive…) >> >> I would like to pre-announce our new website which Rico and I have been working on over the last couple of months, and collect some final feedback before we roll it out as soon as possible. >> >> So here is an outline of what has happened and what will happen next: >> >> * Rico has helped me to implement a fresh design for our website which has been drafted by another friend. The goals were to get rid of the sad and grey website, which is also *way* too simplistic, and create something that is nice looking, memorable, and brings people in. >> >> * During that journey, we have waved goodbye to Bootstrap which is hard to work with once you have discovered Bulma (https://bulma.io/), our new CSS framework of choice. We have also rewritten and refactored some parts of the backend code. There is now less Javascript and less CSS - and I am sure that we could actually still go and save a lot more. >> >> * One of the biggest rewrites is fireinfo, as with a growing number of profiles, our PostgreSQL database started to suffer. We haven’t tested this in full production, yet, but I am sure this will be a lot faster than the older version. This all only affects how we store the data and nothing changes for the clients or users. >> >> * We have upgraded the PostgreSQL driver from psycopg2 to psycopg3, and we use async programming a lot more where possible (these are all lessons learned from the build service). >> >> * We have replaced memcached with redis. Not because memcache didn’t do its job well, but rather because of the reason that we have both in our infrastructure and it is a little bit easier to just deploy one. >> >> * There is a new integration with Asterisk to see current calls - previously the phone stuff didn’t work at all any more since we replaced FreePBX with Asterisk. >> >> But that is enough about the technical stuff… Let’s talk about what has visually changed, and why: >> >> * First of all, we have brighter colours. Very bright! Because we are a fun project! The grey used to depress me slightly and if you ask a designer what would represent us as a community, you get this. I am a lot happier with that. >> >> * The tux is gone. This is kind of a bitter sweet moment, but the old IPFire “logo” is gone with this. I am sure it will be found here or there in a couple of places, but there is no way to make something ancient like this work with something modern-looking. I spent days together with professionals to draft a new logo, and we got nothing, well, apart from the simple things that is: IPFire_ >> >> * IPFire_ is not supposed to replace the word “IPFire” in texts, but I think it is a nice way to highlight the nerdiness/console people/Linux things without becoming complex to understand, or confusing to the corporate people… >> >> * On top of the front page, we finally have some mission statement: More Than A Firewall. We need to talk more about what we are and what we can do, and we need to explain (I don’t know why, but we do) to people what opportunities IPFire can open for them. This still needs a lot of work and I am happy to hear any ideas what is a nice way to communicate what IPFire is to new people using as few words as possible. >> >> * Then, there are a couple of new pages: One of the bigger ones is the About page that explains in more detail what IPFire does (which is why it feels hard to repeat the same on the front page) and it has a large list of (hopefully) all features that IPFire can do/supports/etc. This needs to be updated with every core update, so please let me know if there is something missing in the future as I will probably miss them. Additionally, we have a section with us, the team. Being a faceless project is not very good to attract more people joining our missing, and here is now the place where people will see us for the first time - the people who make IPFire happen. >> >> * The download page has mainly been made shorter and now includes the change log. Cloud providers have been added to an extra page. If you know of any cloud providers that support IPFire, please let me know. Torrent downloads are gone. >> >> * Help: The help page has always been a hard one for me. This time it contains a sentence or two that explains what all those things are good for :) Let’s see how that is going to work out… >> >> * This is a big one: We are getting rid of the thousand subdomains that we are having. There is no more wiki.ipfire.org <http://wiki.ipfire.org/>, blog.ipfire.org <http://blog.ipfire.org/>, people.ipfire.org <http://people.ipfire.org/>, location.ipfire.org <http://location.ipfire.org/>, and so on (exceptions do apply of course). Everything is now in one place: ipfire.org <http://ipfire.org/>. The blog is a subsection of the website, people register accounts on the main page, log in, the documentation has moved there as well. This should hopefully make everyone happy who for a long time wanted buttons to change from one thing to the next here. Here it finally is! >> >> * But there isn’t enough space for everything on the main navigation bar. So at the bottom of the page, there is an extra link called “Sitemap” with all the other things that didn’t get a large link. There is a lot of development stuff on there, too. >> >> * When logged in, the users area is a bit tidier and hopefully we are able to bring a couple more features to this in the future… >> >> * Since users might also be logged in on the main page/the blog/etc. we show “join us now” and “subscribe to our newsletter” only when people have not already done so, which makes it a lot more obvious what the next step of action for users is and a lot less confusing for the people who have already done so. >> >> * There has been a large list of bugs/feature requests submitted by a number of people who have been fixed in this. We might have introduced a couple of new ones, so please file a ticket in Bugzilla if something is broken and that needs fixing. >> >> All in all we hope that this is a big first step to make IPFire appear the modern distribution that it is, instead of having the dark image of some coders in their basements. To summarise this all in one email feels very short for all the labour that we have put into this over the years, but I suppose it is a good sign to have simplicity in the end. >> >> We would like to ask you now for your feedback on all of this. I know that many of you have seen this before, but please help us to double check, that a big launch does not become an embarrassment for some tiny reason :) We have taken some risky decisions and we are happy to see how they are turning out… >> >> The new website is currently running at https://www.michael.dev.ipfire.org/ to get to things like fireinfo, just change the subdomain like so https://fireinfo.michael.dev.ipfire.org/. A couple of things like editing your own profile won’t work because the development instance can’t write to our LDAP system, but apart from that, things should be running just fine. >> >> I am exciting to hear some feedback and hopefully we can build a small roadmap out of it for the future! >> >> Best, >> -Michael & Rico >

3 7

[PATCH] Revert "proxy.cgi: Fix for Bug #12826 'squid >=5 crashes on literal IPv6 addresses'"
by Michael Tremer 08 Jan '24

08 Jan '24

This reverts commit e0be9eab47d621545e5498c32c0fef39f7ef84a9. This change is now producing problems on IPv6-enabled systems as it will deny access to any website that is IPv6-enabled as well, even if the client connected using IPv4. I have tested if squid is now running on fine on systems where IPv6 is disabled and can confirm that its running just fine. Signed-off-by: Michael Tremer <michael.tremer(a)ipfire.org> --- html/cgi-bin/proxy.cgi | 12 +----------- 1 file changed, 1 insertion(+), 11 deletions(-) diff --git a/html/cgi-bin/proxy.cgi b/html/cgi-bin/proxy.cgi index 71be315f6..c8e3576df 100644 --- a/html/cgi-bin/proxy.cgi +++ b/html/cgi-bin/proxy.cgi @@ -3525,19 +3525,9 @@ END $_ =~ s/__PROXY_PORT__/$proxysettings{'PROXY_PORT'}/; print FILE $_; } - print FILE "\n#End of custom includes\n\n"; + print FILE "\n#End of custom includes\n"; close (ACL); } - - print FILE <<END -# Prevent ipv6 requests to avoid crash in squid > 5.x -acl to_ipv6 dst ipv6 -acl from_ipv6 src ipv6 -http_access deny to_ipv6 -http_access deny from_ipv6 -END - ; - if ((!-z $extgrp) && ($proxysettings{'AUTH_METHOD'} eq 'ncsa') && ($proxysettings{'NCSA_BYPASS_REDIR'} eq 'on')) { print FILE "\nredirector_access deny for_extended_users\n"; } # Check if squidclamav is enabled. -- 2.39.2

2 1

[PATCH] libssh: Update to 0.10.6
by Peter Müller 08 Jan '24

08 Jan '24

Please refer to https://www.libssh.org/2023/12/18/libssh-0-10-6-and-libssh-0-9-8-security-r… for this version's release announcement. Signed-off-by: Peter Müller <peter.mueller(a)ipfire.org> --- config/rootfiles/common/libssh | 2 +- lfs/libssh | 6 +++--- 2 files changed, 4 insertions(+), 4 deletions(-) diff --git a/config/rootfiles/common/libssh b/config/rootfiles/common/libssh index 464bf28c2..417a8be8d 100644 --- a/config/rootfiles/common/libssh +++ b/config/rootfiles/common/libssh @@ -13,5 +13,5 @@ #usr/lib/cmake/libssh/libssh-config.cmake #usr/lib/libssh.so usr/lib/libssh.so.4 -usr/lib/libssh.so.4.9.4 +usr/lib/libssh.so.4.9.6 #usr/lib/pkgconfig/libssh.pc diff --git a/lfs/libssh b/lfs/libssh index 36ff9f176..587a97921 100644 --- a/lfs/libssh +++ b/lfs/libssh @@ -1,7 +1,7 @@ ############################################################################### # # # IPFire.org - A linux based firewall # -# Copyright (C) 2007-2022 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 = 0.10.4 +VER = 0.10.6 THISAPP = libssh-$(VER) DL_FILE = $(THISAPP).tar.xz @@ -40,7 +40,7 @@ objects = $(DL_FILE) $(DL_FILE) = $(DL_FROM)/$(DL_FILE) -$(DL_FILE)_BLAKE2 = 9349a688bdbd7c0d3bc93d6d0d6d55122ae9f918b922baeae8a7c6d4ae3ec340e6607afdd8a47055176f31531aefa94b6cc2bda25d59625fe1a7f83823dd75f9 +$(DL_FILE)_BLAKE2 = 6ae1c611b685fa8ec5e5fb159f93493edf4d8ae8536300cd9a357daadc28ca2fbd8a64a22157744bc97e2e672b0b84b58e1167d7369fe88306b3581098af9f57 install : $(TARGET) -- 2.35.3

1 0

[PATCH] libgcrypt: Update to 1.10.3
by Peter Müller 08 Jan '24

08 Jan '24

Refer to https://dev.gnupg.org/T6817 for release information concerning this version. Signed-off-by: Peter Müller <peter.mueller(a)ipfire.org> --- config/rootfiles/common/libgcrypt | 2 +- lfs/libgcrypt | 6 +++--- 2 files changed, 4 insertions(+), 4 deletions(-) diff --git a/config/rootfiles/common/libgcrypt b/config/rootfiles/common/libgcrypt index fe687dab5..f08cf1db3 100644 --- a/config/rootfiles/common/libgcrypt +++ b/config/rootfiles/common/libgcrypt @@ -6,7 +6,7 @@ #usr/lib/libgcrypt.la #usr/lib/libgcrypt.so usr/lib/libgcrypt.so.20 -usr/lib/libgcrypt.so.20.4.2 +usr/lib/libgcrypt.so.20.4.3 #usr/lib/pkgconfig/libgcrypt.pc #usr/share/aclocal/libgcrypt.m4 #usr/share/info/gcrypt.info diff --git a/lfs/libgcrypt b/lfs/libgcrypt index a79f5bed2..dfd7a9a2f 100644 --- a/lfs/libgcrypt +++ b/lfs/libgcrypt @@ -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.10.2 +VER = 1.10.3 THISAPP = libgcrypt-$(VER) DL_FILE = $(THISAPP).tar.bz2 @@ -40,7 +40,7 @@ objects = $(DL_FILE) $(DL_FILE) = $(DL_FROM)/$(DL_FILE) -$(DL_FILE)_BLAKE2 = c86b29648664aae3fb694b20ad258828d2cecbb09db2b83df00fbdebd5d74228c92015c50f659c250cb0768ccaef7949294d9b7cdcd47e1387b7dce81d35da19 +$(DL_FILE)_BLAKE2 = 1a228e02820e886016eb55dee75936c4422a15fb4f95a2f9bcd1e4faac4015d4321c7c8d23f164eb08ece5d62935ab3b3d3104eabfdd22db997ab3e5689dfa6f install : $(TARGET) -- 2.35.3

1 0

[PATCH] kmod: Update to 31
by Peter Müller 08 Jan '24

08 Jan '24

According to the source tarball's NEWS file: - Improvements - Allow passing a path to modprobe so the module is loaded from anywhere from the filesystem, but still handling the module dependencies recorded in the indexes. This is mostly intended for kernel developers to speedup testing their kernel modules without having to load the dependencies manually or override the module in /usr/lib/modules/. Now it's possible to do: # modprobe ./drivers/gpu/drm/i915/i915.ko As long as the dependencies didn't change, this should do the right thing - Use in-kernel decompression if available. This will check the runtime support in the kernel for decompressing modules and use it through finit_module(). Previously kmod would fallback to the older init_module() when using compressed modules since there wasn't a way to instruct the kernel to uncompress it on load or check if the kernel supported it or not. This requires a recent kernel (>= 6.4) to have that support and in-kernel decompression properly working in the kernel. - Make modprobe fallback to syslog when stderr is not available, as was documented in the man page, but not implemented - Better explaing `modprobe -r` and how it differentiates from rmmod - depmod learned a `-o <dir>` option to allow using a separate output directory. With this, it's possible to split the output files from the ones used as input from the kernel build system - Add compat with glibc >= 2.32.9000 that dropped __xstat - Improve testsuite to stop skipping tests when sysconfdir is something other than /etc - Build system improvements and updates - Change a few return codes from -ENOENT to -ENODATA to avoid confusing output in depmod when the module itself lacks a particular ELF section due to e.g. CONFIG_MODVERSIONS=n in the kernel. - Bug Fixes - Fix testsuite using uninitialized memory when testing module removal with --wait - Fix testsuite not correctly overriding the stat syscall on 32-bit platforms. For most architectures this was harmless, but for MIPS it was causing some tests to fail. - Fix handling unknown signature algorithm - Fix linking with a static liblzma, libzstd or zlib - Fix memory leak when removing module holders - Fix out-of-bounds access when using very long paths as argument to rmmod - Fix warnings reported by UBSan Signed-off-by: Peter Müller <peter.mueller(a)ipfire.org> --- config/rootfiles/common/kmod | 2 +- lfs/kmod | 6 +++--- 2 files changed, 4 insertions(+), 4 deletions(-) diff --git a/config/rootfiles/common/kmod b/config/rootfiles/common/kmod index 78971ea22..1a0432169 100644 --- a/config/rootfiles/common/kmod +++ b/config/rootfiles/common/kmod @@ -9,6 +9,6 @@ sbin/rmmod #usr/lib/libkmod.la #usr/lib/libkmod.so usr/lib/libkmod.so.2 -usr/lib/libkmod.so.2.4.0 +usr/lib/libkmod.so.2.4.1 #usr/lib/pkgconfig/libkmod.pc #usr/share/bash-completion/completions/kmod diff --git a/lfs/kmod b/lfs/kmod index 89e196252..643573d33 100644 --- a/lfs/kmod +++ b/lfs/kmod @@ -1,7 +1,7 @@ ############################################################################### # # # IPFire.org - A linux based firewall # -# Copyright (C) 2007-2022 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 = 30 +VER = 31 THISAPP = kmod-$(VER) DL_FILE = $(THISAPP).tar.xz @@ -40,7 +40,7 @@ objects = $(DL_FILE) $(DL_FILE) = $(DL_FROM)/$(DL_FILE) -$(DL_FILE)_BLAKE2 = c5cb690dbb8fad66ac603648ff330794b417ff2fa2f8f61b6e9cb76dab93f984128b3d83a826203f39f3fb94f174f0db7395db6a47e52e8b7c561486f9d00778 +$(DL_FILE)_BLAKE2 = 0dc8572da570315cf0aadd87fa7e83d0f88dea91c8566749e6f3004f9a6df916dce337ca99ea5929d41f45b408c1e3effa50f9d24615d7fa28688150a5ce91cf install : $(TARGET) -- 2.35.3

1 0

[PATCH] cpio: Update to 2.14
by Peter Müller 08 Jan '24

08 Jan '24

Noteworthy changes in this release, according to https://lists.gnu.org/archive/html/info-gnu/2023-05/msg00001.html : * New option --ignore-dirnlink Valid in copy-out mode, it instructs cpio to ignore the actual number of links reported for each directory member and always store 2 instead. * Changes in --reproducible option The --reproducible option implies --ignore-dirlink. In other words, it is equivalent to --ignore-devno --ignore-dirnlink --renumber-inodes. * Use GNU ls algorithm for deciding timestamp format in -tv mode * Bugfixes ** Fix cpio header verification. ** Fix handling of device numbers on copy out. ** Fix calculation of CRC in copy-out mode. ** Rewrite the fix for CVE-2015-1197. ** Fix combination of --create --append --directory. ** Fix appending to archives bigger than 2G. Signed-off-by: Peter Müller <peter.mueller(a)ipfire.org> --- config/rootfiles/common/cpio | 1 + lfs/cpio | 6 +++--- 2 files changed, 4 insertions(+), 3 deletions(-) diff --git a/config/rootfiles/common/cpio b/config/rootfiles/common/cpio index 45bf9f79c..7b9bae045 100644 --- a/config/rootfiles/common/cpio +++ b/config/rootfiles/common/cpio @@ -12,6 +12,7 @@ bin/cpio #usr/share/locale/id/LC_MESSAGES/cpio.mo #usr/share/locale/it/LC_MESSAGES/cpio.mo #usr/share/locale/ja/LC_MESSAGES/cpio.mo +#usr/share/locale/ka/LC_MESSAGES/cpio.mo #usr/share/locale/ko/LC_MESSAGES/cpio.mo #usr/share/locale/nl/LC_MESSAGES/cpio.mo #usr/share/locale/pl/LC_MESSAGES/cpio.mo diff --git a/lfs/cpio b/lfs/cpio index 6c1e6faa5..f44fe1d2c 100644 --- a/lfs/cpio +++ b/lfs/cpio @@ -1,7 +1,7 @@ ############################################################################### # # # IPFire.org - A linux based firewall # -# Copyright (C) 2007-2019 IPFire Team <info(a)ipfire.org> # +# Copyright (C) 2007-2023 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.13 +VER = 2.14 THISAPP = cpio-$(VER) DL_FILE = $(THISAPP).tar.gz @@ -42,7 +42,7 @@ objects = $(DL_FILE) $(DL_FILE) = $(DL_FROM)/$(DL_FILE) -$(DL_FILE)_BLAKE2 = 225f88b7a3e916110671075249217e4811efe767d5c202b420565038a00c2df59159493ac1daefc3ce4349f34c560fcf90b26418f09f05adf7f3b79566ab74de +$(DL_FILE)_BLAKE2 = ddfecf7e3ff59cb15fa0856d374a8b1ff5aaf9143a940202c6c0eb84f0347b940a40e31258035e1d217fe210ef7ffdedb41e40f3a9d47ba51f44626378090f8a install : $(TARGET) -- 2.35.3

1 0

[PATCH] strongSwan: Update to 5.9.13
by Peter Müller 08 Jan '24

08 Jan '24

Please refer to https://github.com/strongswan/strongswan/releases/tag/5.9.13 for the changelog of this version. Signed-off-by: Peter Müller <peter.mueller(a)ipfire.org> --- lfs/strongswan | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/lfs/strongswan b/lfs/strongswan index 9496d05dd..d002290f7 100644 --- a/lfs/strongswan +++ b/lfs/strongswan @@ -24,7 +24,7 @@ include Config -VER = 5.9.12 +VER = 5.9.13 THISAPP = strongswan-$(VER) DL_FILE = $(THISAPP).tar.bz2 @@ -40,7 +40,7 @@ objects = $(DL_FILE) $(DL_FILE) = $(DL_FROM)/$(DL_FILE) -$(DL_FILE)_BLAKE2 = 40f80162970152bca028a9af6b37c4c6e2ef38e75f88b92bf03f18641dadacbc574441e74cd0c7abb49ce4c15d9b82301aa90cb07c4fd223bf83163ebfbc2381 +$(DL_FILE)_BLAKE2 = 1d60864a557cf14e84c62d4c04ae64eb24331e2576c157b276cf13691ac2a7f5d1b92925e4c3e6ab51dc1f6f64aeb7c60ffb16309673a9f78a73f652cb24da8c install : $(TARGET) -- 2.35.3

1 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

Development January 2024