lostecho/oldlinux-files
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

add directory docs

Browse Source
This commit is contained in:
gohigh
2024-02-19 00:23:35 -05:00
parent b50063d9b3
commit 9912ec445d
12689 changed files with 3135349 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

72
docs/Install-Guide/install-guide-2.2.2/node159.html Normal file
View File

@@ -0,0 +1,72 @@
<!DOCTYPE HTML PUBLIC "-//W3O//DTD W3 HTML 2.0//EN">
<!Converted with LaTeX2HTML 95.1 (Fri Jan 20 1995) by Nikos Drakos (nikos@cbl.leeds.ac.uk), CBLU, University of Leeds >
<HEAD>
<TITLE>4.1.3 Dealing with users</TITLE>
</HEAD>
<BODY>
<meta name="description" value="4.1.3 Dealing with users">
<meta name="keywords" value="gs">
<meta name="resource-type" value="document">
<meta name="distribution" value="global">
<P>
<BR> <HR><A NAME=tex2html3802 HREF="node160.html"><IMG ALIGN=BOTTOM ALT="next" SRC="next_motif.gif"></A> <A NAME=tex2html3800 HREF="node156.html"><IMG ALIGN=BOTTOM ALT="up" SRC="up_motif.gif"></A> <A NAME=tex2html3794 HREF="node158.html"><IMG ALIGN=BOTTOM ALT="previous" SRC="previous_motif.gif"></A> <A NAME=tex2html3804 HREF="node1.html"><IMG ALIGN=BOTTOM ALT="contents" SRC="contents_motif.gif"></A> <A NAME=tex2html3805 HREF="node250.html"><IMG ALIGN=BOTTOM ALT="index" SRC="index_motif.gif"></A> <BR>
<B> Next:</B> <A NAME=tex2html3803 HREF="node160.html">4.1.4 Setting the rules</A>
<B>Up:</B> <A NAME=tex2html3801 HREF="node156.html">4.1 About RootHats, </A>
<B> Previous:</B> <A NAME=tex2html3795 HREF="node158.html">4.1.2 Abusing the system</A>
<BR> <HR> <P>
<H2><A NAME=SECTION00613000000000000000>4.1.3 Dealing with users</A></H2>
<P>
<A NAME=4222>&#160;</A>
<A NAME=4223>&#160;</A>
<A NAME=4224>&#160;</A>
<A NAME=4225>&#160;</A>
UNIX security is rather lax by design. Security on the system was
an afterthought---the system was originally developed in an environment where
users intruding upon other users was simply unheard of. Because of this,
even with security measures, there is still the ability for normal users
to do harm.
<P>
System administrators can take two stances when dealing with abusive
users: they can be either paranoid or trusting. The paranoid system
administrator usually causes more harm than he or she prevents. One of
my favorite sayings is, ``Never attribute to malice anything which can
be attributed to stupidity.'' Put another way, most users
don't have the ability or knowledge to do real harm on the system.
90% of the time, when a user is causing trouble on the system (by,
for instance, filling up the user partition with large files, or
running multiple instances of a large program), the user is simply unaware
that what he or she is doing is a problem. I have come down on users who
were causing a great deal of trouble, but they were simply acting out
of ignorance---not malice.
<P>
When you deal with users who are causing potential trouble, don't be
accusative. The old rule of ``innocent until proven guilty'' still holds.
It is best to simply talk to the user, and question about the trouble,
instead of causing a confrontation. The last thing you want to do is
be on the user's bad side. This will raise a lot of suspicion about you---the
system administrator---running the system correctly. If a user believes
that you distrust or dislike them, they might accuse you of deleting files
or breaching privacy on the system. This is certainly not the kind of position
that you want to be in.
<P>
If you do find that a user has been attempting to ``crack'' the system,
or was intentionally doing harm to the system, don't return the malicious
behavior with malice of your own. Instead, simply provide a warning---but
be flexible. In many cases, you may catch a user ``in the act'' of
doing harm to the system---give them a warning. Tell them not to let it
happen again. However, if you <em>do</em> catch them causing harm again,
be absolutely sure that it is intentional. I can't even begin to describe
the number of cases where it appeared as though a user was causing trouble,
when in fact it was either an accident or a fault of my own.
<P>
<BR> <HR><A NAME=tex2html3802 HREF="node160.html"><IMG ALIGN=BOTTOM ALT="next" SRC="next_motif.gif"></A> <A NAME=tex2html3800 HREF="node156.html"><IMG ALIGN=BOTTOM ALT="up" SRC="up_motif.gif"></A> <A NAME=tex2html3794 HREF="node158.html"><IMG ALIGN=BOTTOM ALT="previous" SRC="previous_motif.gif"></A> <A NAME=tex2html3804 HREF="node1.html"><IMG ALIGN=BOTTOM ALT="contents" SRC="contents_motif.gif"></A> <A NAME=tex2html3805 HREF="node250.html"><IMG ALIGN=BOTTOM ALT="index" SRC="index_motif.gif"></A> <BR>
<B> Next:</B> <A NAME=tex2html3803 HREF="node160.html">4.1.4 Setting the rules</A>
<B>Up:</B> <A NAME=tex2html3801 HREF="node156.html">4.1 About RootHats, </A>
<B> Previous:</B> <A NAME=tex2html3795 HREF="node158.html">4.1.2 Abusing the system</A>
<BR> <HR> <P>
<BR> <HR>
<P><ADDRESS>
<I>Matt Welsh <BR>
mdw@sunsite.unc.edu</I>
</ADDRESS>
</BODY>