From: Adolf Belka <adolf.belka@ipfire.org>
To: development@lists.ipfire.org
Subject: [PATCH] rpcbind: Update to version 1.2.7
Date: Sun, 19 Jan 2025 23:08:42 +0100 [thread overview]
Message-ID: <20250119220844.3292084-3-adolf.belka@ipfire.org> (raw)
In-Reply-To: <20250119220844.3292084-1-adolf.belka@ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 3419 bytes --]
- Update from versio0n 1.2.6 to 1.2.7
- Update of rootfile
- Changelog
1.2.7
rpcinfo: try connecting using abstract address.
rpcinfo doesn't use library calls to set up the address for rpcbind. So
to get to it try the new abstract address, we need to explicitly
teach it how.
Listen on an AF_UNIX abstract address if supported.
As RPC is primarily a network service it is best, on Linux, to use
network namespaces to isolate it. However contacting rpcbind via an
AF_UNIX socket allows escape from the network namespace.
If clients could use an abstract address, that would ensure clients
contact an rpcbind in the same network namespace.
systemd can pass in a listening abstract socket by providing an '@'
prefix. However with libtirpc 1.3.3 or earlier attempting this will
fail as the library mistakenly determines that the socket is not bound.
This generates unsightly error messages.
So it is best not to request the abstract address when it is not likely
to work.
A patch to fix this also proposes adding a define for
_PATH_RPCBINDSOCK_ABSTRACT to the header files. We can check for this
and only include the new ListenStream when that define is present.
autotools/systemd: call rpcbind with -w only on enabled warm starts
If rpcbind is configured with --disable-warmstarts it responds on -w
with its usage string. This is not helpful in a systemd service, so pass
-w conditionally.
rpcbind: fix double free in init_transport
$ rpcbind -h 127.0.0.1
free(): double free detected in tcache 2
Aborted
Signed-off-by: Adolf Belka <adolf.belka(a)ipfire.org>
---
lfs/rpcbind | 8 ++++----
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/lfs/rpcbind b/lfs/rpcbind
index 31708192c..a707d9c05 100644
--- a/lfs/rpcbind
+++ b/lfs/rpcbind
@@ -1,7 +1,7 @@
###############################################################################
# #
# IPFire.org - A linux based firewall #
-# Copyright (C) 2007-2023 IPFire Team <info(a)ipfire.org> #
+# Copyright (C) 2007-2025 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 = Transport independent RPC portmapper
-VER = 1.2.6
+VER = 1.2.7
THISAPP = rpcbind-$(VER)
DL_FILE = $(THISAPP).tar.bz2
@@ -34,7 +34,7 @@ DL_FROM = $(URL_IPFIRE)
DIR_APP = $(DIR_SRC)/$(THISAPP)
TARGET = $(DIR_INFO)/$(THISAPP)
PROG = rpcbind
-PAK_VER = 7
+PAK_VER = 8
DEPS =
@@ -48,7 +48,7 @@ objects = $(DL_FILE)
$(DL_FILE) = $(DL_FROM)/$(DL_FILE)
-$(DL_FILE)_BLAKE2 = bb0e9f81e4747f8a732c9e25af561e79f2b6cd1c1955db586833871901b6da73f4b7ef32149a81b75daa81359b9c0554726670460b28857042dd66a2f861cac2
+$(DL_FILE)_BLAKE2 = f1e79b304ce5fe06c1c256d3512d999daffca782d956440f612b8a957ad7ddb35356b47aa4f4105d5b24d820daab32ec3a0f4a3b8ac76bb7adf5c3ed22d2ef01
install : $(TARGET)
--
2.48.1
next prev parent reply other threads:[~2025-01-19 22:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-19 22:08 [PATCH] flac: Update to version 1.4.3 Adolf Belka
2025-01-19 22:08 ` [PATCH] nfs: Update to version number 2.8.2 Adolf Belka
2025-01-19 22:08 ` Adolf Belka [this message]
2025-01-19 22:08 ` [PATCH] tcpdump: Update to version 4.99.5 Adolf Belka
2025-01-19 22:08 ` [PATCH] traceroute: Update to version 2.1.6 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=20250119220844.3292084-3-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