Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sdd.hp.com!spool.mu.edu!agate!dog.ee.lbl.gov!nosc!humu!pegasus!bohtsg!art
From: art@bohtsg.pegasus.com (Art Neilson)
Newsgroups: comp.sys.ncr
Subject: shadow passwd in Tower 500 OS 1.01.02
Message-ID: <1991Jun21.202108.18914@bohtsg.UUCP>
Date: 21 Jun 91 20:21:08 GMT
Sender: art@bohtsg.UUCP (Art Neilson)
Organization: Bank of Hawaii Tech Support
Lines: 19

I recently tried to implement shadow passwords in our Tower 500
OS 1.01.02.  Everything seems to work fine except for va.  /bin/login,
/bin/su and other system utilities behave correctly in the presence
of /etc/shadow.  /bin/passwd correctly updates /etc/shadow with new
passwords, and /bin/login looks up passwords in /etc/shadow instead of
/etc/passwd as does /bin/su.  Unfortunately /va/obj/va which is invoked
by /va/obj/vastart (va's login shell) detects the presence of /etc/shadow
and complains that you must remove the shadow password option before
va will work.  Why is va crippled in this regard ?  We are a Banking
Institution and would like to implement the shadow feature to enhance
security.  The old sa administration system was composed of shell scripts
so it is easy to modify, however the new va administration system is a
binary file and cannot be easily modified.  We really liked the old
menu system and the ease of adding our own custom Banking menus to the
standard sa menu system.  This is no longer the case, we haven't a clue
as to how one can hook into the va menu system.
-- 
Arthur W. Neilson III        | INET: art@pilikia.pegasus.com
Bank of Hawaii Tech Support  | UUCP: uunet!ucsd!nosc!pegasus!bohtsg!art