Question: /usr/tcb/bin/edauth

From: Steve Copeland <steverc_at_enerco.co.nz>
Date: Tue, 18 Aug 1998 14:00:42 +1200

I have 200+ Users on a Trucluster pair of V4.0b 4100s most which neglect
to change their passwords within the preset expiry period and are
consequently locked out. There also seem to be many other reasons why a
user may be locked out of an enhanced security 4.0b system. Although
some configurations are intuitive, most are not and I therefore need to
determine the /usr/tcb/bin/edauth -g output configurations' translation
into meaningful descriptions.
A (sorted and unique) list of those configurations current in the
/usr/tcb/bin/edauth -g output of all my users follows, but is probably
not a complete list:
chkent
u_audcntl
u_basepriv
u_exp
u_expdate
u_genchars_at_
u_genletters_at_
u_genpwd_at_
u_life
u_lock_at_
u_max_login_intvl
u_maxlen
u_numunsuclog
u_oldcrypt
u_pickpw
u_psw_change_reqd
u_pwchanger
u_pwdepth
u_pwdict
u_restrict_at_
u_succhg
u_suclog
u_suctty
u_syspriv
u_unsucchg
u_unsuclog
u_unsuctty

Cheers.

Steve Copeland
Computer Systems Engineer

------------------------------------------------------------------------
----------------------------
Enersis Limited - (Northern) DDI : 09 359 6225
PO Box 4302 Pager : 026 250 9231
20 Beaumont Street Fax : 09 359 6320
Freemans Bay, Auckland E-Mail : copelands_at_enersis.co.nz
------------------------------------------------------------------------
----------------------------

Received on Tue Aug 18 1998 - 02:04:42 NZST

This archive was generated by hypermail 2.4.0 : Wed Nov 08 2023 - 11:53:38 NZDT