Article View: comp.sys.novell
Article #6121Re: Supervisor Lockout
From: Kevin Parris
Date: Wed, 17 May 1995 00:00
Date: Wed, 17 May 1995 00:00
29 lines
1692 bytes
1692 bytes
Also, I believe that "enable login" at the server console will unlock the Supervisor account. And I agree with you there should always be at least one super-equivalent account, or one other account that is MANAGER of Supervisor. Most of the "network manager is gone, we don't know the password" problems could be avoided with strategy like this. In article <3pcl2s$31o@mercury.kingston.ac.uk>, bs_s474@kingston.ac.uk says... > >Leslie Styles (lms@soton.ac.uk) wrote: >: Is there any way to remove Supervisor from the Intruder Detection Lockout >: scheme. Although we do want to use lockout for all our user accounts, we >: don't want people to be able to lock the Supervisor account by simply >: typing login supervisor and not giving a password three times. > >No. Give your supervisor a 'backdoor' account - use that account to unlock the >supervisor. > >Ted Slade >tedslade@kingston.ac.uk -- Kevin Parris kparris@sunbelt.net
Technical Details
Message-ID:
<3pd6vp$84m@ns.sunbelt.net>Path:
arc1-ca.pugleaf.net!unknown!not-for-mailReferences:
<3pcdvo$eul@wendy.ibmpcug.co.uk> <3pcl2s$31o@mercury.kingston.ac.uk>Show Full Headers
Complete Article Headers
X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: fe659,904914b3379d21bf X-Google-Attributes: gidfe659,public X-Google-Thread: 10f035,904914b3379d21bf X-Google-Attributes: gid10f035,public X-Google-Thread: 103bf6,904914b3379d21bf X-Google-Attributes: gid103bf6,public X-Google-Thread: f8bf7,904914b3379d21bf X-Google-Attributes: gidf8bf7,public From: kparris@sunbelt.net (Kevin Parris) Subject: Re: Supervisor Lockout Date: 1995/05/17 Message-ID: <3pd6vp$84m@ns.sunbelt.net> X-Deja-AN: 102834959 references: <3pcdvo$eul@wendy.ibmpcug.co.uk> <3pcl2s$31o@mercury.kingston.ac.uk> organization: My Own Self newsgroups: comp.sys.novell,bit.listserv.novell,comp.os.netware.security,comp.os.netware.misc