#
267654 |
|
19-Jun-2014 |
gjb |
Copy stable/9 to releng/9.3 as part of the 9.3-RELEASE cycle.
Approved by: re (implicit) Sponsored by: The FreeBSD Foundation |
#
241309 |
|
07-Oct-2012 |
pfg |
MFC r241141, r241165, r241165, r241181;
rpc: convert all uid and gid variables to u_int.
Follow a similar change in Solaris and linux where the uid and gid variables were made more similar to what the system expects. In our case we use u_int which is what XDR can manage,
Reviewed by: bde
|
#
241059 |
|
29-Sep-2012 |
pfg |
MFC r241007, r241008:
Complete revert of r239963 (from head).
The attempt to merge changes from the linux libtirpc caused rpc.lockd to exit after startup under unclear conditions.
Reported by: David Wolfskill
|
#
240799 |
|
22-Sep-2012 |
pfg |
MFC r239963:
Bring some changes from Bull's NFSv4 libtirpc implementation.
____
Fixed infinite loop in svc_run() ____
__rpc_taddr2uaddr_af() assumes the netbuf to always have a non-zero data. This is a bad assumption and can lead to a seg-fault. This patch adds a check for zero length and returns NULL when found. ____
Changed clnt_spcreateerror() to return clearer and more concise error messages. ____
Converted all uid and gid variables of the type uid_t and gid_t. ____
libtirpc: set r_netid and r_owner in __rpcb_findaddr_timed
These fields in the rpcbind GETADDR call are being passed uninitialized to CLNT_CALL. In the case of x86_64 at least, this usually leads to a segfault. On x86, it sometimes causes segfaults and other times causes garbage to be sent on the wire.
rpcbind generally ignores the r_owner field for calls that come in over the wire, so it really doesn't matter what we send in that slot. We just need to send something. The reference implementation from Sun seems to send a blank string. Have ours follow suit. ____
libtirpc: be sure to free cl_netid and cl_tp
When creating a client with clnt_tli_create, it uses strdup to copy strings for these fields if nconf is passed in. clnt_dg_destroy frees these strings already. Make sure clnt_vc_destroy frees them in the same way.
____
Obtained from: Bull GNU/Linux NFSv4 Project
|
#
225736 |
|
22-Sep-2011 |
kensmith |
Copy head to stable/9 as part of 9.0-RELEASE release cycle.
Approved by: re (implicit)
|
#
110440 |
|
06-Feb-2003 |
charnier |
The .Fn function
|
#
108087 |
|
19-Dec-2002 |
ru |
mdoc(7) police: "The .Fa argument.".
|
#
108037 |
|
18-Dec-2002 |
ru |
mdoc(7) police: "The .Fn function".
|
#
107788 |
|
12-Dec-2002 |
ru |
Uniformly refer to a file system as "file system".
Approved by: re
|
#
86656 |
|
20-Nov-2001 |
ru |
mdoc(7) police: consistently use the .Ux macro.
|
#
84487 |
|
04-Oct-2001 |
wpaul |
Add compatibility functions for the AF_LOCAL RPC transport stuff that used to live in RPC 4.0. This is needed for yppasswd and rpc.yppasswdd to work correctly. Patch supplied by Martin Blapp.
|
#
84425 |
|
03-Oct-2001 |
bde |
Fixed bitrot in synopsis. The TI-RPC changes gave mounds of it, mainly inconsistently weird const poisoning in the man pages relative to the headers.
|
#
84306 |
|
01-Oct-2001 |
ru |
mdoc(7) police: Use the new .In macro for #include statements.
|
#
77878 |
|
07-Jun-2001 |
sobomax |
Correct cross-reference: portmap.8 --> rpcbind.8
Submitted by: .Xr testing script
|
#
74695 |
|
23-Mar-2001 |
alfred |
change callrpc() from taking "char *" args, I'm quite sure they really meant to use "void *".
remove a duplicate prototype for callrpc() from libexec/ypxfr/ypxfr_extern.h
|
#
74517 |
|
20-Mar-2001 |
ru |
This manpage is heavily based on the old rpc.3 manpage, and should have been repo-copied from it in the first place.
Apply all of our fixes up to and including revision 1.14 to the original rpc.3 manpage, including conversion to mdoc(7).
|
#
74462 |
|
19-Mar-2001 |
alfred |
Bring in a hybrid of SunSoft's transport-independent RPC (TI-RPC) and associated changes that had to happen to make this possible as well as bugs fixed along the way.
Bring in required TLI library routines to support this.
Since we don't support TLI we've essentially copied what NetBSD has done, adding a thin layer to emulate direct the TLI calls into BSD socket calls.
This is mostly from Sun's tirpc release that was made in 1994, however some fixes were backported from the 1999 release (supposedly only made available after this porting effort was underway).
The submitter has agreed to continue on and bring us up to the 1999 release.
Several key features are introduced with this update: Client calls are thread safe. (1999 code has server side thread safe) Updated, a more modern interface.
Many userland updates were done to bring the code up to par with the recent RPC API.
There is an update to the pthreads library, a function pthread_main_np() was added to emulate a function of Sun's threads library.
While we're at it, bring in NetBSD's lockd, it's been far too long of a wait.
New rpcbind(8) replaces portmap(8) (supporting communication over an authenticated Unix-domain socket, and by default only allowing set and unset requests over that channel). It's much more secure than the old portmapper.
Umount(8), mountd(8), mount_nfs(8), nfsd(8) have also been upgraded to support TI-RPC and to support IPV6.
Umount(8) is also fixed to unmount pathnames longer than 80 chars, which are currently truncated by the Kernel statfs structure.
Submitted by: Martin Blapp <mb@imp.ch> Manpage review: ru Secure RPC implemented by: wpaul
|