From: Karl Amrhein (ksa@SLAC.Stanford.EDU)
Date: Mon Sep 23 2002 - 18:38:47 EDT
No answers from the list, but more research gave me the
information I needed.
1. I misinterpreted the advisory -- it sounded like there was a way to
pick the port or range of ports on which rpc.ttdbserverd would listen
(possibily with a command line option, or config file). At least with
Solaris this does not seem possible.
2. Further investigations indicated that when rpc.ttdbserverd is started
as a daemon from a shell, as opposed to starting from inetd, it
listens on a privileged ephemeral port < 1024. In contrast, when
started from inetd, it grabs a port in the usual Solaris ephemeral
range above 32767.
Learning number 2 above solved my issue. I would have rather learned
this directly from Sun rather than by trial and error.
On Wed, Aug 14, 2002 at 12:11:41PM -0700, Karl Amrhein wrote:
> The recent CERT Advisory for rpc.ttdbserverd
> (http://www.cert.org/advisories/CA-2002-26.html) says:
>
> The ToolTalk RPC database server may be configured to use port 692/
> tcp or another port as indicated in output from the rpcinfo(1M)
> command.
>
> Does anyone actually know how to do this (change the port number used by
> rpc.ttdbserverd)?
-- Karl Amrhein, <ksa@slac.stanford.edu> | www.slac.stanford.edu/~ksa SLAC Computing Services, Systems Group | 650.926.5083 Bldg 50, 364 _______________________________________________ sunmanagers mailing list sunmanagers@sunmanagers.org http://www.sunmanagers.org/mailman/listinfo/sunmanagers
This archive was generated by hypermail 2.1.7 : Wed Apr 09 2008 - 23:24:58 EDT