From: Adolf Belka <adolf.belka@ipfire.org>
To: development@lists.ipfire.org
Subject: [PATCH] igmpproxy: Update to version 0.4
Date: Thu, 05 Jan 2023 19:21:09 +0100 [thread overview]
Message-ID: <20230105182110.3725538-5-adolf.belka@ipfire.org> (raw)
In-Reply-To: <20230105182110.3725538-1-adolf.belka@ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 2439 bytes --]
- Update from version 0.3 to 0.4
- Update of rootfile not required
- Changelog
* Release version 0.4
* Complement phyint whitelist with blacklist
Fixes: #54
Implement new phyint configuration option (blacklist), which enables
blocking of specific traffic.
* Chroot and drop privileges after startup
With this PR:
- The apparent root directory can be changed after startup, thus denying
igmpproxy access to files and commands outside that environmental
directory tree.
- igmpproxy can drop root privileges after startup by changing id to
another user.
* Add travis apt repositories for Ubuntu Precise
Signed-off-by: Adolf Belka <adolf.belka(a)ipfire.org>
---
lfs/igmpproxy | 8 ++++----
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/lfs/igmpproxy b/lfs/igmpproxy
index 1bf4246a8..99a9a6741 100644
--- a/lfs/igmpproxy
+++ b/lfs/igmpproxy
@@ -1,7 +1,7 @@
###############################################################################
# #
# IPFire.org - A linux based firewall #
-# Copyright (C) 2007-2018 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 #
@@ -26,7 +26,7 @@ include Config
SUMMARY = Multicast router utilizing IGMP forwarding
-VER = 0.3
+VER = 0.4
THISAPP = igmpproxy-$(VER)
DL_FILE = $(THISAPP).tar.gz
@@ -34,7 +34,7 @@ DL_FROM = $(URL_IPFIRE)
DIR_APP = $(DIR_SRC)/$(THISAPP)
TARGET = $(DIR_INFO)/$(THISAPP)
PROG = igmpproxy
-PAK_VER = 6
+PAK_VER = 7
DEPS =
@@ -48,7 +48,7 @@ objects = $(DL_FILE)
$(DL_FILE) = $(DL_FROM)/$(DL_FILE)
-$(DL_FILE)_BLAKE2 = 4dd07936074fbd9b3c869851f5b592f1eec33109be78ee5a05b3658c26afb67c30379f7cc66dfa20af276aae0a1c21dbf5c9fd337c853d623b08126324b06561
+$(DL_FILE)_BLAKE2 = 233af2fe35a0d661211d205fec89cce0a7dc91fe1530e940703e6d56eeb69f4490ca16d18787dbbaf7c0087dc2ebcb61d212778993af6fbb8acc7ba33429f7e0
install : $(TARGET)
--
2.39.0
next prev parent reply other threads:[~2023-01-05 18:21 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-05 18:21 [PATCH] grep: Update to version 3.8 Adolf Belka
2023-01-05 18:21 ` [PATCH] haproxy: Update to version 2.7.1 Adolf Belka
2023-01-05 18:21 ` [PATCH] hdparm: Update to version 9.65 Adolf Belka
2023-01-05 18:21 ` [PATCH] iana-etc: Update to version 20221226 Adolf Belka
2023-01-05 18:21 ` Adolf Belka [this message]
2023-01-05 18:45 ` [PATCH] igmpproxy: Update to version 0.4 Michael Tremer
2023-01-05 18:21 ` [PATCH] sdl2: Update to version 2.26.2 Adolf Belka
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20230105182110.3725538-5-adolf.belka@ipfire.org \
--to=adolf.belka@ipfire.org \
--cc=development@lists.ipfire.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox