[4021] in Release_7.7_team
Further improvements to "access" documentation for the PWOG.
daemon@ATHENA.MIT.EDU (Bill Cattey)
Wed Sep 17 16:25:27 2003
From: Bill Cattey <wdc@MIT.EDU>
To: release-team@mit.edu
Content-Type: text/plain
Content-Transfer-Encoding: 7bit
Message-Id: <1063830324.19591.12.camel@tokata.mit.edu>
Mime-Version: 1.0
Date: Wed, 17 Sep 2003 16:25:24 -0400
I just helped someone take a newly private workstation
and restrict access so only they could log in.
(Their machine is still re-installing after a previous
attempt to follow the instructions in the PWOG failed for them,
so I don't really know if I was successful.)
I would like to propose the following changes to the PWOG:
1. Delete the "Background: A pre-8.2 summary" section.
We've been away from 8.2 long enough, I think.
2. Move the, now smaller, "User Authorization" subsection to be the
first subsection of the section "Giving Users Access to Your
Workstation".
3. Add some front matter to the "User Authorization" subsection to say,
"This is what you do if you want to set up your workstation so only you
can use it. This is also what you do to control who can access your
computer if you do mkserv remote"
The above changes help people understand that they don't have to turn
their systems into timesharing hosts if all they want to do is be the
sole authorized user.
4. QUESTION: Do we need to add prose about making sure one creates a
local password file and changes the root password if the owner wants to
restrict access even if mkserv remote is not used?
5. The mkserv remote should point the reader back at "User
Authorization" to finish the mkserv remote tasks.
Questions?
Comments?
Tropical fish?
-wdc
