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
2001-03-19 12:50:13 +00:00
|
|
|
.\" @(#)rpc_xdr.3n 1.24 93/08/31 SMI; from SVr4
|
|
|
|
|
.\" Copyright 1989 AT&T
|
|
|
|
|
.\" @(#)rpc_xdr.new 1.1 89/04/06 SMI;
|
|
|
|
|
.\" Copyright (c) 1988 Sun Microsystems, Inc. - All Rights Reserved.
|
|
|
|
|
.\" $FreeBSD$
|
|
|
|
|
.Dd May 3, 1993
|
|
|
|
|
.Dt RPC_XDR 3
|
|
|
|
|
.Os
|
|
|
|
|
.Sh NAME
|
|
|
|
|
.Nm xdr_accepted_reply ,
|
|
|
|
|
.Nm xdr_authsys_parms ,
|
|
|
|
|
.Nm xdr_callhdr ,
|
|
|
|
|
.Nm xdr_callmsg ,
|
|
|
|
|
.Nm xdr_opaque_auth ,
|
|
|
|
|
.Nm xdr_rejected_reply ,
|
|
|
|
|
.Nm xdr_replymsg
|
|
|
|
|
.Nd XDR library routines for remote procedure calls
|
|
|
|
|
.Sh LIBRARY
|
|
|
|
|
.Lb libc
|
|
|
|
|
.Sh SYNOPSIS
|
2001-10-01 16:09:29 +00:00
|
|
|
.In rpc/rpc.h
|
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
2001-03-19 12:50:13 +00:00
|
|
|
.Ft bool_t
|
2001-10-03 16:47:56 +00:00
|
|
|
.Fn xdr_accepted_reply "XDR *xdrs" "struct accepted_reply *ar"
|
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
2001-03-19 12:50:13 +00:00
|
|
|
.Ft bool_t
|
|
|
|
|
.Fn xdr_authsys_parms "XDR *xdrs" "struct authsys_parms *aupp"
|
2001-10-03 16:47:56 +00:00
|
|
|
.Ft bool_t
|
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
2001-03-19 12:50:13 +00:00
|
|
|
.Fn xdr_callhdr "XDR *xdrs" "struct rpc_msg *chdr"
|
|
|
|
|
.Ft bool_t
|
|
|
|
|
.Fn xdr_callmsg "XDR *xdrs" "struct rpc_msg *cmsg"
|
|
|
|
|
.Ft bool_t
|
|
|
|
|
.Fn xdr_opaque_auth "XDR *xdrs" "struct opaque_auth *ap"
|
|
|
|
|
.Ft bool_t
|
2001-10-03 16:47:56 +00:00
|
|
|
.Fn xdr_rejected_reply "XDR *xdrs" "struct rejected_reply *rr"
|
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
2001-03-19 12:50:13 +00:00
|
|
|
.Ft bool_t
|
2001-10-03 16:47:56 +00:00
|
|
|
.Fn xdr_replymsg "XDR *xdrs" "struct rpc_msg *rmsg"
|
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
2001-03-19 12:50:13 +00:00
|
|
|
.Sh DESCRIPTION
|
|
|
|
|
These routines are used for describing the
|
|
|
|
|
RPC messages in XDR language.
|
|
|
|
|
They should normally be used by those who do not
|
|
|
|
|
want to use the RPC
|
|
|
|
|
package directly.
|
|
|
|
|
These routines return
|
|
|
|
|
.Dv TRUE
|
|
|
|
|
if they succeed,
|
|
|
|
|
.Dv FALSE
|
|
|
|
|
otherwise.
|
|
|
|
|
.Sh Routines
|
|
|
|
|
See
|
|
|
|
|
.Xr rpc 3
|
|
|
|
|
for the definition of the
|
|
|
|
|
.Vt XDR
|
|
|
|
|
data structure.
|
|
|
|
|
.Bl -tag -width XXXXX
|
|
|
|
|
.It Fn xdr_accepted_reply
|
|
|
|
|
Used to translate between RPC
|
|
|
|
|
reply messages and their external representation.
|
|
|
|
|
It includes the status of the RPC
|
|
|
|
|
call in the XDR language format.
|
|
|
|
|
In the case of success, it also includes the call results.
|
|
|
|
|
.It Fn xdr_authsys_parms
|
|
|
|
|
Used for describing
|
|
|
|
|
.Ux
|
|
|
|
|
operating system credentials.
|
|
|
|
|
It includes machine-name, uid, gid list, etc.
|
|
|
|
|
.It Fn xdr_callhdr
|
|
|
|
|
Used for describing
|
|
|
|
|
RPC
|
|
|
|
|
call header messages.
|
|
|
|
|
It encodes the static part of the call message header in the
|
|
|
|
|
XDR language format.
|
|
|
|
|
It includes information such as transaction
|
|
|
|
|
ID, RPC version number, program and version number.
|
|
|
|
|
.It Fn xdr_callmsg
|
|
|
|
|
Used for describing
|
|
|
|
|
RPC call messages.
|
|
|
|
|
This includes all the RPC
|
|
|
|
|
call information such as transaction
|
|
|
|
|
ID, RPC version number, program number, version number,
|
|
|
|
|
authentication information, etc.
|
|
|
|
|
This is normally used by servers to determine information about the client
|
|
|
|
|
RPC call.
|
|
|
|
|
.It Fn xdr_opaque_auth
|
|
|
|
|
Used for describing RPC
|
|
|
|
|
opaque authentication information messages.
|
|
|
|
|
.It Fn xdr_rejected_reply
|
|
|
|
|
Used for describing RPC reply messages.
|
|
|
|
|
It encodes the rejected RPC message in the XDR language format.
|
|
|
|
|
The message could be rejected either because of version
|
|
|
|
|
number mis-match or because of authentication errors.
|
|
|
|
|
.It Fn xdr_replymsg
|
|
|
|
|
Used for describing RPC
|
|
|
|
|
reply messages.
|
|
|
|
|
It translates between the
|
|
|
|
|
RPC reply message and its external representation.
|
|
|
|
|
This reply could be either an acceptance,
|
|
|
|
|
rejection or
|
|
|
|
|
.Dv NULL .
|
|
|
|
|
.El
|
|
|
|
|
.Sh SEE ALSO
|
|
|
|
|
.Xr rpc 3 ,
|
|
|
|
|
.Xr xdr 3
|