src/usr.sbin/rpcbind, branch releng/10.3

Fix a regression with SA-15:24 patch that prevented NIS from

2015-10-02T16:36:16+00:00

working.

The Sun RPC framework uses a netbuf structure to represent the

2015-09-29T18:06:27+00:00

transport specific form of a universal transport address.  The
structure is expected to be opaque to consumers.  In the current
implementation, the structure contains a pointer to a buffer
that holds the actual address.

In rpcbind(8), netbuf structures are copied directly, which would
result in two netbuf structures that reference to one shared
address buffer.  When one of the two netbuf structures is freed,
access to the other netbuf structure would result in an undefined
result that may crash the rpcbind(8) daemon.

Fix this by making a copy of the buffer that is going to be freed
instead of doing a shallow copy.

Security:	FreeBSD-SA-15:24.rpcbind
Security:	CVE-2015-7236

Fix socket calls on error post-r243965.

2012-12-21T15:54:13+00:00

Submitted by:	Garrett Cooper

Fill sin6_scope_id in sockaddr_in6 before passing it from the kernel to

2012-11-17T20:19:00+00:00

userland via routing socket or sysctl.  This eliminates the following
KAME-specific sin6_scope_id handling routine from each userland utility:

 sin6.sin6_scope_id = ntohs(*(u_int16_t *)&sin6.sin6_addr.s6_addr[2]);

This behavior can be controlled by net.inet6.ip6.deembed_scopeid.  This is
set to 1 by default (sin6_scope_id will be filled in the kernel).

Reviewed by:	bz

Spelling fixes for usr.sbin/

2011-12-30T10:58:14+00:00

Use prototype. While I'm there, add a pair of parenthesis to mark an if

2011-07-14T07:28:49+00:00

statment's border.

MFC after:	1 month

Fix typos - remove duplicate "the".

2011-02-21T09:01:34+00:00

PR:	bin/154928
Submitted by:	Eitan Adler 
MFC after: 	3 days

Revert bogus change that snuck into r203972.

2010-02-17T06:11:05+00:00

The NetBSD Foundation has given permission to remove clause 3 and 4

2010-02-16T21:47:05+00:00

from their liceense.

Obtained from:	NetBSD

When you have multiple addresses on the same network on different

2010-02-09T18:10:56+00:00

interfaces (such as when you are part of a carp pool), and you run
rpcbind -h to restrict which interfaces have rpc services, rpcbind can
none-the-less return addresses that aren't in the -h list.  This patch
enforces the rule that when you specify -h on the command line, then
services returned from rpcbind must be to one of the addresses listed
in -h, or be a loopback address (since localhost is implicit when
running -h).

The root cause of this is the assumption in addrmerge that there can
be only one interface that matches a given network IP address.  This
turns out not to be the case.  To retain historical behavior, I didn't
try to fix the routine to prefer the address that the request came
into, since I didn't know the side effects that might cause in the
normal case.  My quick analysis suggests that it wouldn't be a
problem, but since this code is tricky I opted for the more
conservative patch of only restricting the reply when -h is in effect.

Hence, this change will have no effect when you are running rpcbind
without -h.

Reviewed by:	alfred@
Sponsored by:	iX Systems
MFC after:	2 weeks