linux-nfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
* [PATCH RFC 0/3] Avoid well-known port numbers
@ 2018-02-15 20:21 Chuck Lever
  2018-02-15 20:22 ` [PATCH RFC 1/3] Add an internal helper for binding to a dynamically-assigned port Chuck Lever
                   ` (2 more replies)
  0 siblings, 3 replies; 5+ messages in thread
From: Chuck Lever @ 2018-02-15 20:21 UTC (permalink / raw)
  To: linux-nfs, libtirpc-devel

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

^ permalink raw reply	[flat|nested] 5+ messages in thread

end of thread, other threads:[~2018-02-15 21:11 UTC | newest]

Thread overview: 5+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2018-02-15 20:21 [PATCH RFC 0/3] Avoid well-known port numbers Chuck Lever
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

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).