Greetings, list
I've become used to manually entering new devices (e.g., foreign hosts
from which users connect) to be recognized under C2 security by our
various Tru64 alphas, in /etc/auth/system/devassign and ttys, then
rebuilding the databases with convauth -d v and -d t, resp. I've recently
attempted adding some remote hosts to a 5.1a machine, and while the
devassign.db build is fine, the ttys.db build *hangs*. It appears to
create a ttys.db when I ^C out of the hang, but the database doesn't work.
Copying .proto..ttys.db to provide a working ttys.db was required to at
least restore even access by root on the console (!).
I noticed that there is also no .proto..ttys (the asci file) in the
/etc/auth/system directories of each of the two 5.0a boxes we have. This
file exists on 4.0F DS10's we have. I've not had any trouble rebuilding
ttys.db and devassign.db on a small variety of alphas running 4.0B, D, and
F to date.
Any clues? Will summarize.
Chris
======================================================================
Christopher C Stevenson, C4063 office: (709) 737-2624
Dept. of Physics & Physical Oceanography fax: (709) 737-8739
Memorial University of Newfoundland
St. John's, Newfoundland, CANADA A1B 3X7
URL:
http://www.physics.mun.ca/~csteven
======================================================================
"We are all in the gutter, but some of us are looking at the stars."
-- Oscar Wilde
Received on Thu Sep 13 2001 - 17:16:59 NZST