1 |
swift 05/08/04 08:05:21 |
2 |
|
3 |
Modified: xml/htdocs/doc/en sudo-guide.xml |
4 |
Log: |
5 |
Spelling mistakes, no content change. Fixed #101189 |
6 |
|
7 |
Revision Changes Path |
8 |
1.5 +8 -8 xml/htdocs/doc/en/sudo-guide.xml |
9 |
|
10 |
file : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/sudo-guide.xml?rev=1.5&content-type=text/x-cvsweb-markup&cvsroot=gentoo |
11 |
plain: http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/sudo-guide.xml?rev=1.5&content-type=text/plain&cvsroot=gentoo |
12 |
diff : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/sudo-guide.xml.diff?r1=1.4&r2=1.5&cvsroot=gentoo |
13 |
|
14 |
Index: sudo-guide.xml |
15 |
=================================================================== |
16 |
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/sudo-guide.xml,v |
17 |
retrieving revision 1.4 |
18 |
retrieving revision 1.5 |
19 |
diff -u -r1.4 -r1.5 |
20 |
--- sudo-guide.xml 3 Aug 2005 08:13:40 -0000 1.4 |
21 |
+++ sudo-guide.xml 4 Aug 2005 08:05:21 -0000 1.5 |
22 |
@@ -1,6 +1,6 @@ |
23 |
<?xml version='1.0' encoding="UTF-8"?> |
24 |
|
25 |
-<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/sudo-guide.xml,v 1.4 2005/08/03 08:13:40 swift Exp $ --> |
26 |
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/sudo-guide.xml,v 1.5 2005/08/04 08:05:21 swift Exp $ --> |
27 |
|
28 |
<!DOCTYPE guide SYSTEM "/dtd/guide.dtd"> |
29 |
|
30 |
@@ -23,7 +23,7 @@ |
31 |
<license/> |
32 |
|
33 |
<version>1.2</version> |
34 |
-<date>2005-08-03</date> |
35 |
+<date>2005-08-04</date> |
36 |
|
37 |
<chapter> |
38 |
<title>About Sudo</title> |
39 |
@@ -45,8 +45,8 @@ |
40 |
application (or any user of a certain group, depending on the permissions used). |
41 |
You can (and probably even should) require the user to provide a password when |
42 |
he wants to execute the application and you can even fine-tune the permissions |
43 |
-based on the location where the user is at: if he is logged on from the system |
44 |
-itself or through SSH from a remote site. |
45 |
+based on the user's location: logged on from the system itself or through SSH |
46 |
+from a remote site. |
47 |
</p> |
48 |
|
49 |
</body> |
50 |
@@ -130,7 +130,7 @@ |
51 |
application that can allow people to elevate privileges. For instance, allowing |
52 |
users to execute <c>emerge</c> as root can indeed grant them full root access |
53 |
to the system because <c>emerge</c> can be manipulated to change the live file |
54 |
-system in the user his advantage. If you do not trust your <c>sudo</c> users, |
55 |
+system to the user's advantage. If you do not trust your <c>sudo</c> users, |
56 |
don't grant them any rights. |
57 |
</p> |
58 |
|
59 |
@@ -182,7 +182,7 @@ |
60 |
</pre> |
61 |
|
62 |
<p> |
63 |
-The password that <c>sudo</c> requires is the user his own password. This is to |
64 |
+The password that <c>sudo</c> requires is the user's own password. This is to |
65 |
make sure that no terminal that you accidentally left open to others is abused |
66 |
for malicious purposes. |
67 |
</p> |
68 |
@@ -245,7 +245,7 @@ |
69 |
<p> |
70 |
More interesting is to define a set of users who can run software administrative |
71 |
applications (such as <c>emerge</c> and <c>ebuild</c>) on the system and a group |
72 |
-of administrators who can change users their password - but not roots! |
73 |
+of administrators who can change the password of any user, except root! |
74 |
</p> |
75 |
|
76 |
<pre caption="Using aliases for users and commands"> |
77 |
@@ -346,7 +346,7 @@ |
78 |
before <c>sudo</c> fails) to <c>2</c> instead of the default 3: |
79 |
</p> |
80 |
|
81 |
-<pre caption="Requiring the root password instead of the user his password"> |
82 |
+<pre caption="Requiring the root password instead of the user's password"> |
83 |
Defaults:john runaspw, passwd_tries=2 |
84 |
</pre> |
85 |
|
86 |
|
87 |
|
88 |
|
89 |
-- |
90 |
gentoo-doc-cvs@g.o mailing list |