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
|
|
|
/* $NetBSD: rpc_msg.h,v 1.11 2000/06/02 22:57:56 fvdl Exp $ */
|
|
|
|
|
|
1994-08-04 20:39:34 +00:00
|
|
|
/*
|
|
|
|
|
* Sun RPC is a product of Sun Microsystems, Inc. and is provided for
|
|
|
|
|
* unrestricted use provided that this legend is included on all tape
|
|
|
|
|
* media and as a part of the software program in whole or part. Users
|
|
|
|
|
* may copy or modify Sun RPC without charge, but are not authorized
|
|
|
|
|
* to license or distribute it to anyone else except as part of a product or
|
|
|
|
|
* program developed by the user.
|
1995-05-30 05:05:38 +00:00
|
|
|
*
|
1994-08-04 20:39:34 +00:00
|
|
|
* SUN RPC IS PROVIDED AS IS WITH NO WARRANTIES OF ANY KIND INCLUDING THE
|
1996-01-30 23:33:04 +00:00
|
|
|
* WARRANTIES OF DESIGN, MERCHANTABILITY AND FITNESS FOR A PARTICULAR
|
1994-08-04 20:39:34 +00:00
|
|
|
* PURPOSE, OR ARISING FROM A COURSE OF DEALING, USAGE OR TRADE PRACTICE.
|
1995-05-30 05:05:38 +00:00
|
|
|
*
|
1994-08-04 20:39:34 +00:00
|
|
|
* Sun RPC is provided with no support and without any obligation on the
|
|
|
|
|
* part of Sun Microsystems, Inc. to assist in its use, correction,
|
|
|
|
|
* modification or enhancement.
|
1995-05-30 05:05:38 +00:00
|
|
|
*
|
1994-08-04 20:39:34 +00:00
|
|
|
* SUN MICROSYSTEMS, INC. SHALL HAVE NO LIABILITY WITH RESPECT TO THE
|
|
|
|
|
* INFRINGEMENT OF COPYRIGHTS, TRADE SECRETS OR ANY PATENTS BY SUN RPC
|
|
|
|
|
* OR ANY PART THEREOF.
|
1995-05-30 05:05:38 +00:00
|
|
|
*
|
1994-08-04 20:39:34 +00:00
|
|
|
* In no event will Sun Microsystems, Inc. be liable for any lost revenue
|
|
|
|
|
* or profits or other special, indirect and consequential damages, even if
|
|
|
|
|
* Sun has been advised of the possibility of such damages.
|
1995-05-30 05:05:38 +00:00
|
|
|
*
|
1994-08-04 20:39:34 +00:00
|
|
|
* Sun Microsystems, Inc.
|
|
|
|
|
* 2550 Garcia Avenue
|
|
|
|
|
* Mountain View, California 94043
|
1994-08-07 18:41:02 +00:00
|
|
|
*
|
|
|
|
|
* from: @(#)rpc_msg.h 1.7 86/07/16 SMI
|
|
|
|
|
* from: @(#)rpc_msg.h 2.1 88/07/29 4.0 RPCSRC
|
1999-08-27 23:45:13 +00:00
|
|
|
* $FreeBSD$
|
1994-08-04 20:39:34 +00:00
|
|
|
*/
|
|
|
|
|
|
|
|
|
|
/*
|
|
|
|
|
* rpc_msg.h
|
|
|
|
|
* rpc message definition
|
|
|
|
|
*
|
|
|
|
|
* Copyright (C) 1984, Sun Microsystems, Inc.
|
|
|
|
|
*/
|
|
|
|
|
|
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
|
|
|
#ifndef _RPC_RPC_MSG_H
|
|
|
|
|
#define _RPC_RPC_MSG_H
|
1994-08-07 18:41:02 +00:00
|
|
|
|
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
|
|
|
#define RPC_MSG_VERSION ((u_int32_t) 2)
|
1994-08-04 20:39:34 +00:00
|
|
|
#define RPC_SERVICE_PORT ((u_short) 2048)
|
|
|
|
|
|
|
|
|
|
/*
|
|
|
|
|
* Bottom up definition of an rpc message.
|
|
|
|
|
* NOTE: call and reply use the same overall stuct but
|
|
|
|
|
* different parts of unions within it.
|
|
|
|
|
*/
|
|
|
|
|
|
|
|
|
|
enum msg_type {
|
|
|
|
|
CALL=0,
|
|
|
|
|
REPLY=1
|
|
|
|
|
};
|
|
|
|
|
|
|
|
|
|
enum reply_stat {
|
|
|
|
|
MSG_ACCEPTED=0,
|
|
|
|
|
MSG_DENIED=1
|
|
|
|
|
};
|
|
|
|
|
|
|
|
|
|
enum accept_stat {
|
|
|
|
|
SUCCESS=0,
|
|
|
|
|
PROG_UNAVAIL=1,
|
|
|
|
|
PROG_MISMATCH=2,
|
|
|
|
|
PROC_UNAVAIL=3,
|
|
|
|
|
GARBAGE_ARGS=4,
|
|
|
|
|
SYSTEM_ERR=5
|
|
|
|
|
};
|
|
|
|
|
|
|
|
|
|
enum reject_stat {
|
|
|
|
|
RPC_MISMATCH=0,
|
|
|
|
|
AUTH_ERROR=1
|
|
|
|
|
};
|
|
|
|
|
|
|
|
|
|
/*
|
|
|
|
|
* Reply part of an rpc exchange
|
|
|
|
|
*/
|
|
|
|
|
|
|
|
|
|
/*
|
|
|
|
|
* Reply to an rpc request that was accepted by the server.
|
|
|
|
|
* Note: there could be an error even though the request was
|
|
|
|
|
* accepted.
|
|
|
|
|
*/
|
|
|
|
|
struct accepted_reply {
|
|
|
|
|
struct opaque_auth ar_verf;
|
|
|
|
|
enum accept_stat ar_stat;
|
|
|
|
|
union {
|
|
|
|
|
struct {
|
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
|
|
|
rpcvers_t low;
|
|
|
|
|
rpcvers_t high;
|
1994-08-04 20:39:34 +00:00
|
|
|
} AR_versions;
|
|
|
|
|
struct {
|
|
|
|
|
caddr_t where;
|
|
|
|
|
xdrproc_t proc;
|
|
|
|
|
} AR_results;
|
|
|
|
|
/* and many other null cases */
|
|
|
|
|
} ru;
|
|
|
|
|
#define ar_results ru.AR_results
|
|
|
|
|
#define ar_vers ru.AR_versions
|
|
|
|
|
};
|
|
|
|
|
|
|
|
|
|
/*
|
|
|
|
|
* Reply to an rpc request that was rejected by the server.
|
|
|
|
|
*/
|
|
|
|
|
struct rejected_reply {
|
|
|
|
|
enum reject_stat rj_stat;
|
|
|
|
|
union {
|
|
|
|
|
struct {
|
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
|
|
|
rpcvers_t low;
|
|
|
|
|
rpcvers_t high;
|
1994-08-04 20:39:34 +00:00
|
|
|
} RJ_versions;
|
|
|
|
|
enum auth_stat RJ_why; /* why authentication did not work */
|
|
|
|
|
} ru;
|
|
|
|
|
#define rj_vers ru.RJ_versions
|
|
|
|
|
#define rj_why ru.RJ_why
|
|
|
|
|
};
|
|
|
|
|
|
|
|
|
|
/*
|
|
|
|
|
* Body of a reply to an rpc request.
|
|
|
|
|
*/
|
|
|
|
|
struct reply_body {
|
|
|
|
|
enum reply_stat rp_stat;
|
|
|
|
|
union {
|
|
|
|
|
struct accepted_reply RP_ar;
|
|
|
|
|
struct rejected_reply RP_dr;
|
|
|
|
|
} ru;
|
|
|
|
|
#define rp_acpt ru.RP_ar
|
|
|
|
|
#define rp_rjct ru.RP_dr
|
|
|
|
|
};
|
|
|
|
|
|
|
|
|
|
/*
|
|
|
|
|
* Body of an rpc request call.
|
|
|
|
|
*/
|
|
|
|
|
struct call_body {
|
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
|
|
|
rpcvers_t cb_rpcvers; /* must be equal to two */
|
|
|
|
|
rpcprog_t cb_prog;
|
|
|
|
|
rpcvers_t cb_vers;
|
|
|
|
|
rpcproc_t cb_proc;
|
1994-08-04 20:39:34 +00:00
|
|
|
struct opaque_auth cb_cred;
|
|
|
|
|
struct opaque_auth cb_verf; /* protocol specific - provided by client */
|
|
|
|
|
};
|
|
|
|
|
|
|
|
|
|
/*
|
|
|
|
|
* The rpc message
|
|
|
|
|
*/
|
|
|
|
|
struct rpc_msg {
|
1996-12-30 13:59:41 +00:00
|
|
|
u_int32_t rm_xid;
|
1994-08-04 20:39:34 +00:00
|
|
|
enum msg_type rm_direction;
|
|
|
|
|
union {
|
|
|
|
|
struct call_body RM_cmb;
|
|
|
|
|
struct reply_body RM_rmb;
|
|
|
|
|
} ru;
|
|
|
|
|
#define rm_call ru.RM_cmb
|
|
|
|
|
#define rm_reply ru.RM_rmb
|
|
|
|
|
};
|
|
|
|
|
#define acpted_rply ru.RM_rmb.ru.RP_ar
|
|
|
|
|
#define rjcted_rply ru.RM_rmb.ru.RP_dr
|
|
|
|
|
|
1994-08-07 18:41:02 +00:00
|
|
|
__BEGIN_DECLS
|
1994-08-04 20:39:34 +00:00
|
|
|
/*
|
|
|
|
|
* XDR routine to handle a rpc message.
|
|
|
|
|
* xdr_callmsg(xdrs, cmsg)
|
|
|
|
|
* XDR *xdrs;
|
|
|
|
|
* struct rpc_msg *cmsg;
|
|
|
|
|
*/
|
2002-03-23 17:24:55 +00:00
|
|
|
extern bool_t xdr_callmsg(XDR *, struct rpc_msg *);
|
1994-08-04 20:39:34 +00:00
|
|
|
|
|
|
|
|
/*
|
|
|
|
|
* XDR routine to pre-serialize the static part of a rpc message.
|
|
|
|
|
* xdr_callhdr(xdrs, cmsg)
|
|
|
|
|
* XDR *xdrs;
|
|
|
|
|
* struct rpc_msg *cmsg;
|
|
|
|
|
*/
|
2002-03-23 17:24:55 +00:00
|
|
|
extern bool_t xdr_callhdr(XDR *, struct rpc_msg *);
|
1994-08-04 20:39:34 +00:00
|
|
|
|
|
|
|
|
/*
|
|
|
|
|
* XDR routine to handle a rpc reply.
|
|
|
|
|
* xdr_replymsg(xdrs, rmsg)
|
|
|
|
|
* XDR *xdrs;
|
|
|
|
|
* struct rpc_msg *rmsg;
|
|
|
|
|
*/
|
2002-03-23 17:24:55 +00:00
|
|
|
extern bool_t xdr_replymsg(XDR *, struct rpc_msg *);
|
1994-08-04 20:39:34 +00:00
|
|
|
|
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
|
|
|
|
|
|
|
|
/*
|
|
|
|
|
* XDR routine to handle a accepted rpc reply.
|
|
|
|
|
* xdr_accepted_reply(xdrs, rej)
|
|
|
|
|
* XDR *xdrs;
|
|
|
|
|
* struct accepted_reply *rej;
|
|
|
|
|
*/
|
2002-03-23 17:24:55 +00:00
|
|
|
extern bool_t xdr_accepted_reply(XDR *, struct accepted_reply *);
|
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
|
|
|
|
|
|
|
|
/*
|
|
|
|
|
* XDR routine to handle a rejected rpc reply.
|
|
|
|
|
* xdr_rejected_reply(xdrs, rej)
|
|
|
|
|
* XDR *xdrs;
|
|
|
|
|
* struct rejected_reply *rej;
|
|
|
|
|
*/
|
2002-03-23 17:24:55 +00:00
|
|
|
extern bool_t xdr_rejected_reply(XDR *, struct rejected_reply *);
|
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
|
|
|
|
1994-08-04 20:39:34 +00:00
|
|
|
/*
|
|
|
|
|
* Fills in the error part of a reply message.
|
|
|
|
|
* _seterr_reply(msg, error)
|
|
|
|
|
* struct rpc_msg *msg;
|
|
|
|
|
* struct rpc_err *error;
|
|
|
|
|
*/
|
2002-03-23 17:24:55 +00:00
|
|
|
extern void _seterr_reply(struct rpc_msg *, struct rpc_err *);
|
1994-08-07 18:41:02 +00:00
|
|
|
__END_DECLS
|
|
|
|
|
|
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
|
|
|
#endif /* !_RPC_RPC_MSG_H */
|
