#621712 Protocol selection for access to rpcbind is broken

Package:
libtirpc1
Source:
libtirpc
Submitter:
Ben Hutchings
Date:
2023-04-25 10:15:04 UTC
Severity:
normal
#621712#5
Date:
2011-04-08 03:51:22 UTC
From:
To:
Package: libtirpc1
Version: 0.2.1-1
X-Debbugs-Cc: 621471@bugs.debian.org

OK, it seems that the libtirpc caller has to do arrange to portmap by
calling svc_reg() and then svc_register().  (Or just give up on portmap
altogether.)

The connection fallback is definitely a bug in libtirpc and will affect
use of rpcbind if for some reason it is not accessible using all the
protocols listed in /etc/netconfig.

Ben.
#621712#10
Date:
2011-04-08 04:25:48 UTC
From:
To:
[...]

Unfortunately that's another trap.  svc_register() is backward-
compatible at the C API level but not the protocol level.  And it looks
like it would be a lot of work to add rpcbind/portmapper fallback
support in libtirpc itself.

Given that the portmapper protocol appears to have been deprecated in
favour of rpcbind in 1995 (RFC 1833), I'm happy to declare it obsolete.
I'm surprised that we've left it so long.

Ben.
#621712#15
Date:
2023-01-17 11:35:07 UTC
From:
To:
 Good Morning,
 Please scroll through the attachment to view your account statement and unpaid invoice #00198683 as of Jan 17th 2023.
 Please provide payment as soon as possible, if you have any question contact us.
 Thank you.


 Alex Stephanie Diane

Accounts Receivable Coordinator

a. 9675 NW 117th Ave, Suite 300, Miami, Florida 33178

o. (305) 421-9021|

f. (305) 887-1029

w. winpintl.com [1]