From: Chuck Lever <chuck.lever@oracle.com>
To: linux-nfs@vger.kernel.org, libtirpc-devel@lists.sourceforge.net
Subject: [PATCH RFC 0/3] Avoid well-known port numbers
Date: Thu, 15 Feb 2018 15:21:59 -0500 [thread overview]
Message-ID: <20180215201832.16924.28659.stgit@klimt.1015granger.net> (raw)
Following up on https://bugzilla.linux-nfs.org/show_bug.cgi?id=320 .
Here's a possible way to get libtirpc to avoid well-known port
numbers when a caller requests a dynamically-assigned port. This
compiles without complaint, but I haven't tested it yet. I'm
interested in comments on the approach.
I understand that Fedora 28 is closing soon. It would be nice to
see a fix for this issue in libtirpc for that release.
---
Chuck Lever (3):
Add an internal helper for binding to a dynamically-assigned port
Avoid choosing reserved ports in svc_tli_create(3)
Avoid choosing reserved ports in clnt_tli_create(3)
src/Makefile.am | 5 +-
src/binddynport.c | 132 ++++++++++++++++++++++++++++++++++++++++++++++++++++
src/clnt_generic.c | 4 +-
src/rpc_soc.c | 7 ++-
src/svc_generic.c | 12 ++---
5 files changed, 147 insertions(+), 13 deletions(-)
create mode 100644 src/binddynport.c
--
Chuck Lever
next reply other threads:[~2018-02-15 20:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-15 20:21 Chuck Lever [this message]
2018-02-15 20:22 ` [PATCH RFC 1/3] Add an internal helper for binding to a dynamically-assigned port Chuck Lever
2018-02-15 20:22 ` [PATCH RFC 2/3] Avoid choosing reserved ports in svc_tli_create(3) Chuck Lever
2018-02-15 21:11 ` Chuck Lever
2018-02-15 20:22 ` [PATCH RFC 3/3] Avoid choosing reserved ports in clnt_tli_create(3) Chuck Lever
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=20180215201832.16924.28659.stgit@klimt.1015granger.net \
--to=chuck.lever@oracle.com \
--cc=libtirpc-devel@lists.sourceforge.net \
--cc=linux-nfs@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).