sudo-tutorial/po sudo-tutorial.pot, 1.1, 1.2 de.po, 1.1, 1.2 pt.po, 1.6, 1.7
Paul W. Frields (pfrields)
fedora-docs-commits at redhat.com
Sat Aug 5 22:49:21 UTC 2006
Author: pfrields
Update of /cvs/docs/sudo-tutorial/po
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv9268/po
Modified Files:
sudo-tutorial.pot de.po pt.po
Log Message:
Move rpm-info and update POT and PO accordingly
Index: sudo-tutorial.pot
===================================================================
RCS file: /cvs/docs/sudo-tutorial/po/sudo-tutorial.pot,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- sudo-tutorial.pot 13 Feb 2006 16:08:38 -0000 1.1
+++ sudo-tutorial.pot 5 Aug 2006 22:49:18 -0000 1.2
@@ -1,7 +1,7 @@
msgid ""
msgstr ""
"Project-Id-Version: PACKAGE VERSION\n"
-"POT-Creation-Date: 2006-02-13 10:03-0600\n"
+"POT-Creation-Date: 2006-08-05 18:48-0400\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL at ADDRESS>\n"
"Language-Team: LANGUAGE <LL at li.org>\n"
@@ -9,400 +9,136 @@
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
-#: en/sudo-tutorial.xml:22(para)
-msgid "WHERE IS MY FDP-INFO, DUDE"
-msgstr ""
-
-#: en/sudo-tutorial.xml:26(title)
-msgid "Introduction"
-msgstr ""
-
-#: en/sudo-tutorial.xml:28(para)
-msgid "The security of a Linux system depends largely on the enforcement of <firstterm>file access permissions</firstterm>. Access to a file is granted or withheld by comparing the identity of the user making the request against permissions associated with the file itself. Most of the configuration files, and many system administration activities, must be accessed by the privileged system user, commonly known as the <firstterm>superuser</firstterm> or the <firstterm>root</firstterm> account, and are not available to ordinary users."
-msgstr ""
-
-#: en/sudo-tutorial.xml:34(para)
-msgid "In this tutorial, we examine a technique for safely granting trusted users access to these programs and files that would normally be denied. The system administrator can keep the root password concealed, yet still allow selected users to obtain privileged access. Everybody wins with this approach."
-msgstr ""
-
-#: en/sudo-tutorial.xml:42(para)
-msgid "When writing about programs or system configuration files, it is customary to indicate which section of the on-line manual pages contain its documentation. For example, section one (1) documents applications; section two (2) documents system calls, section three (3) a library function and so on. Sometimes the same name may be both a system call and a library function, knowing the manual page section is important. Compare the results of \"<userinput>man 2 exit</userinput>\" with \"<userinput>man 3 exit</userinput>\"."
-msgstr ""
-
-#: en/sudo-tutorial.xml:40(para)
-msgid "Although <application>sudo(8)</application><footnote><placeholder-1/></footnote> offers robust control for a networked environment, we shall consider only local use in this tutorial. For more information, consult <ulink url=\"http://www.sudo.ws/sudo\"><filename>http://www.sudo.ws/sudo</filename></ulink>, the official web site."
-msgstr ""
-
-#: en/sudo-tutorial.xml:55(title)
-msgid "How Linux Controls Access"
-msgstr ""
-
-#: en/sudo-tutorial.xml:56(para)
-msgid "To better understand the benefit that <application>sudo(8)</application> brings, let us review how Linux provides access security to the system resources. If you like, skip this section but come back if you need."
-msgstr ""
-
-#: en/sudo-tutorial.xml:60(para)
-msgid "Linux is a multiuser system. There is more to this than simply having a <application>login(1)</application> program: every time a system resource is accessed, care must be taken to ensure that the user attempting the access is permitted to do so."
-msgstr ""
-
-#: en/sudo-tutorial.xml:64(para)
-msgid "For this reason, Linux assigns each login user a set of <firstterm>credentials</firstterm>. Each user has a unique <firstterm>user-id</firstterm>, or <abbrev>UID</abbrev>, and also has a <firstterm>group-id</firstterm>, or <abbrev>GID</abbrev> which need not be unique. This <abbrev>uid</abbrev>:<abbrev>gid</abbrev> pair form an important component of that user's credentials."
-msgstr ""
-
-#: en/sudo-tutorial.xml:70(title)
-msgid "Who Are You?"
-msgstr ""
-
-#: en/sudo-tutorial.xml:71(para)
-msgid "Before you get access to a Linux system, you must prove your identity. While the system administrator decides the security policy for the machine, usually one or more password challenges must be answered. After all, if you really are user <userinput>joesixpack</userinput>, then you should know the answer to a question that only <userinput>joesixpack</userinput> would know: what is the password?"
-msgstr ""
-
-#: en/sudo-tutorial.xml:79(para)
-msgid "Actually, there is more to the authentication process than just a password challenge. The sysadmin can impose restrictions such as limiting the time of day when a given user may login, or requiring that a user make the login attempt from a specific location."
-msgstr ""
-
-#: en/sudo-tutorial.xml:76(para)
-msgid "This process of proving your identity to the system is known as <firstterm>authentication</firstterm>. Many schemes are available to the system administrator, but once the system authenticates your login request, the kernel has enough information to determine what programs you can run or what files you can access<footnote><placeholder-1/></footnote>."
-msgstr ""
-
-#: en/sudo-tutorial.xml:85(para)
-msgid "After a successfully authentication the system uses your uid and gid to control your access to system resources."
-msgstr ""
-
-#: en/sudo-tutorial.xml:90(title)
-msgid "File Access Permissions"
-msgstr ""
-
-#: en/sudo-tutorial.xml:91(para)
-msgid "Every system resource, whether an application program, directory, or file, has a unique name: its <firstterm>filename</firstterm>. You can think of a filename has a unique identifier for that system resource. The part of Linux that manages these named system resources is known as the <firstterm>file system</firstterm>."
-msgstr ""
-
-#: en/sudo-tutorial.xml:96(para)
-msgid "In addition to the file content itself, the file system keeps extra information about every file: its size; disk block locations; and modification and access timestamps. You can see most of this \"meta-data\" using the <application>ls(1)</application> program:"
-msgstr ""
-
-#: en/sudo-tutorial.xml:101(title)
-msgid "Using ls(1) to examine file permissions"
-msgstr ""
-
-#: en/sudo-tutorial.xml:102(screen)
-#, no-wrap
-msgid "$ ls -l /bin/mail\n-rwxr-xr-x 1 root mail 73588 Apr 4 07:03 /bin/mail"
-msgstr ""
-
-#: en/sudo-tutorial.xml:105(para)
-msgid "We are most interested in two groups of information about the file: its ownership and its access permissions."
-msgstr ""
-
-#: en/sudo-tutorial.xml:110(para)
-msgid "The <application>chown(1)</application> program allows the ownership credentials to be changed, but that is another HOWTO."
-msgstr ""
-
-#: en/sudo-tutorial.xml:108(para)
-msgid "When a user creates a file, the user credentials are attached to the file, giving that user <emphasis>ownership</emphasis> of that file<footnote><placeholder-1/></footnote>. In our example, <filename>/bin/mail</filename> is owned by user <userinput>root</userinput> and group <userinput>mail</userinput>."
-msgstr ""
-
-#: en/sudo-tutorial.xml:116(para)
-msgid "The created file also gets a set of file access permissions that describe who may access that file and what kind of access they can get. There are exactly three types of access: read, write, or execute usually abbreviated as <abbrev>rwx</abbrev>. Permissions for a file which could be read, but neither written nor executed, would be written as <abbrev>r--</abbrev>. Remember, the notation is positional and order matters."
-msgstr ""
-
-#: en/sudo-tutorial.xml:122(para)
-msgid "Files actually have three sets of permissions: one set for the file owner, one set for members of the owner's group; and one set for everyone else; again order matters, the owner permissions are first, followed by the group and then the world permissions. In the next section, we shall see how Linux puts all this together."
-msgstr ""
-
-#: en/sudo-tutorial.xml:128(title)
-msgid "May I Access This File, Please?"
-msgstr ""
-
-#: en/sudo-tutorial.xml:129(para)
-msgid "Before any file is accessed, and this includes running an application program, the file system must validate the attempt. There is a very simple, but very powerful, method used to determine whether access should be granted or denied. This algorithm is shown below:"
-msgstr ""
-
-#: en/sudo-tutorial.xml:135(title)
-msgid "Determining File Access"
-msgstr ""
-
-#: en/sudo-tutorial.xml:136(programlisting)
-#, no-wrap
-msgid "if( u.uid == f.uid ) {\n rwx = perms.owner;\n} else if( u.gid == f.gid ) {\n rwx = perms.group;\n} else {\n rwx = perms.world;\n}\nif( !accessok( access_wanted, rwx ) ) {\n errno = EPERM;\n return( -1 );\n}\ndo_access();"
-msgstr ""
-
-#: en/sudo-tutorial.xml:149(para)
-msgid "Assuming the following definitions:"
-msgstr ""
-
-#: en/sudo-tutorial.xml:154(glossterm)
-msgid "u"
-msgstr ""
-
-#: en/sudo-tutorial.xml:156(para)
-msgid "Represents the user credentials containing both the <abbrev>uid</abbrev> and <abbrev>gid</abbrev>."
-msgstr ""
-
-#: en/sudo-tutorial.xml:162(glossterm)
-msgid "f"
+#: en_US/doc-entities.xml:4(title)
+msgid "Local entities for Sudo Tutorial"
msgstr ""
-#: en/sudo-tutorial.xml:164(para)
-msgid "Represents the file ownership credentials, as shown by the <command>ls -l</command> command. Contains both the <abbrev>uid</abbrev> and <abbrev>gid</abbrev> values identifying the owner of the file."
+#: en_US/doc-entities.xml:7(comment)
+msgid "Document name"
msgstr ""
-#: en/sudo-tutorial.xml:171(glossterm)
-msgid "perms"
+#: en_US/doc-entities.xml:8(text)
+msgid "sudo-tutorial"
msgstr ""
-#: en/sudo-tutorial.xml:172(para)
-msgid "The file access permissions for the file, including all three sets of permissions: owner, group and world."
+#: en_US/doc-entities.xml:11(comment)
+msgid "Version number"
msgstr ""
-#: en/sudo-tutorial.xml:177(para)
-msgid "The key point here is that, although there are three sets of file access permissions associated with the file, exactly <emphasis>one</emphasis> set is used to arbitrate the file access. Emphatically, the sets are <emphasis>not</emphasis> tried in sequence until the access is granted or we run out of sets: you get one and only one try at accessing the file."
+#: en_US/doc-entities.xml:12(text)
+msgid "0.14.1"
msgstr ""
-#: en/sudo-tutorial.xml:181(para)
-msgid "If you are the owner of the file, the system uses the file owner permissions. If you are not the owner, but a member of the same group as the file, the system uses the group permissions. If you are neither of these, the system checks against the world permissions."
+#: en_US/doc-entities.xml:15(comment)
+msgid "Date of last revision"
msgstr ""
-#: en/sudo-tutorial.xml:190(title)
-msgid "What Not To Do"
+#: en_US/doc-entities.xml:16(text)
+msgid "2006-01-21"
msgstr ""
-#: en/sudo-tutorial.xml:192(para)
-msgid "As desirable as enforcing file access permissions are on a Linux system, there are valid reasons for needing to bypass the checking. Several users run the same program to generate project files that must be accessible to all; a printer queue is hung and the sysadmin has given a local user authority to restart the printer daemon; an ordinary user wants to mount an NFS hierarchy from a file server; a mail delivery program must be able to write into mail files writable only by the mail recipient; and finally, a local user is empowered to perform designated sysadmin functions but the real sysadmin does not want to grant blanket permission to alter everything on the system."
+#: en_US/doc-entities.xml:19(comment)
+msgid "Document ID"
msgstr ""
-#: en/sudo-tutorial.xml:201(para)
-msgid "Below we will look at common methods of working around the Linux file access permissions scheme and point out some short-comings of each technique. All these methods \"work\", in the sense that they function correctly but incur unnecessary security risks. In the next section, we show how <application>sudo(8)</application> controls most of these risks."
+#: en_US/doc-entities.xml:20(text)
+msgid "<use entity=\"DOCNAME\"/>-<use entity=\"DOCVERSION\"/> (<use entity=\"DOCDATE\"/>)"
msgstr ""
-#: en/sudo-tutorial.xml:208(title)
-msgid "Perhaps You Have Heard Of The su(1) Application?"
+#: en_US/doc-entities.xml:26(comment)
+msgid "Name of program"
msgstr ""
-#: en/sudo-tutorial.xml:209(para)
-msgid "One technique, used since <trademark>UNIX</trademark> systems began, is for the user to temporarily assume the privileges of the superuser account. The <application>su(1)</application> changes the identification for the current user by <emphasis>s</emphasis>ubstituting <emphasis>u</emphasis>ser credentials."
+#: en_US/doc-entities.xml:27(text)
+msgid "<command>sudo(8)</command>"
msgstr ""
-#: en/sudo-tutorial.xml:215(title)
-msgid "Traditional Approach Using su(1)"
+#: en_US/rpm-info.xml:9(rights)
+msgid "OPL"
msgstr ""
-#: en/sudo-tutorial.xml:216(screen)
-#, no-wrap
-msgid "$ id\nuid=500(reynolds) gid=500(reynolds) groups=500(reynolds)\n$ su -c id\nPassword:\nuid=0(root) gid=0(root) groups=0(root),1(bin)..."
+#: en_US/rpm-info.xml:10(version)
+msgid "1.0"
msgstr ""
-#: en/sudo-tutorial.xml:223(para)
-msgid "There are some problems with this approach:"
+#: en_US/rpm-info.xml:13(year)
+msgid "2005"
msgstr ""
-#: en/sudo-tutorial.xml:229(para)
-msgid "The superuser password is compromised."
+#: en_US/rpm-info.xml:14(year)
+msgid "2006"
msgstr ""
-#: en/sudo-tutorial.xml:232(para)
-msgid "Once anyone other than the system administrator knows the superuser password, everyone will know it. He that wishes to keep a secret must keep it a secret that he has a secret to keep. Promises not to tell are not sufficient security."
+#: en_US/rpm-info.xml:15(holder)
+msgid "Tommy Reynolds"
msgstr ""
-#: en/sudo-tutorial.xml:239(para)
-msgid "There is no audit trail."
+#: en_US/rpm-info.xml:17(title)
+msgid "Sudo Tutorial"
msgstr ""
-#: en/sudo-tutorial.xml:245(para)
-msgid "In security parlance, \"to trust\" is identical to \"be at risk from\"."
+#: en_US/rpm-info.xml:18(desc)
+msgid "Guide to using sudo to perform tasks as another user"
msgstr ""
-#: en/sudo-tutorial.xml:242(para)
-msgid "With a superuser shell, a user can do anything that the root account can do. We must trust<footnote><placeholder-1/></footnote>the user to access only the files and programs they claimed to need."
+#: en_US/rpm-info.xml:22(details)
+msgid "Dummy version"
msgstr ""
-#: en/sudo-tutorial.xml:255(title)
-msgid "Please, No Setuid Shell Scripts"
-msgstr ""
-
-#: en/sudo-tutorial.xml:256(para)
-msgid "Another technology, used by the <application>su(1)</application> program, takes advantage of a neat feature."
-msgstr ""
-
-#: en/sudo-tutorial.xml:259(para)
-msgid "Normally, the files accessible to an application or shell depend on who is executing that program. Recall those <emphasis>credentials</emphasis> mentioned earlier? An application executes using the credentials of the user who runs the program."
-msgstr ""
-
-#: en/sudo-tutorial.xml:264(para)
-msgid "Stop, wait, there's more!"
-msgstr ""
-
-#: en/sudo-tutorial.xml:267(para)
-msgid "Files have access permissions but since a program is stored in a file, the program has file access permissions, too."
-msgstr ""
-
-#: en/sudo-tutorial.xml:272(para)
-msgid "The commands:"
-msgstr ""
-
-#: en/sudo-tutorial.xml:277(para)
-msgid "would give whomever runs <filename>/bin/foo</filename> the same privileges that the superuser account would have while running the same application."
-msgstr ""
-
-#: en/sudo-tutorial.xml:270(para)
-msgid "By setting a special flag, called the <firstterm>set user id bit</firstterm> or <function>setuid(2)</function>, we can cause the system to check \"credentials\" made from the program file access permissions, instead of using the credentials for the user running the application<footnote><placeholder-1/><screen width=\"60\"># chown root:root /bin/foo\n# chmod 06555 /bin/foo</screen><placeholder-2/></footnote>."
-msgstr ""
-
-#: en/sudo-tutorial.xml:282(para)
-msgid "This ability to use the credentials of an application, instead of those of the user, can be a great boon to multiuser applications such as databases or email delivery agents. The feature has its proper use on a Linux system."
-msgstr ""
-
-#: en/sudo-tutorial.xml:286(para)
-msgid "As useful as it is, one must resist the temptation to make a shell program, such as <filename>/bin/bash</filename>, or a shell script, such as <filename>/usr/local/bin/run_as_root</filename>, be set user ID to root."
-msgstr ""
-
-#: en/sudo-tutorial.xml:289(para)
-msgid "If this were to be done, then <emphasis>any</emphasis> user running that script or application would be able to access any file that the root account could access."
-msgstr ""
-
-#: en/sudo-tutorial.xml:292(para)
-msgid "Again, the objections to this method a similar to those we mentioned for the <application>su(1)</application> program: no control, and no traceability."
-msgstr ""
-
-#: en/sudo-tutorial.xml:300(title)
-msgid "A Safer Alternative: sudo(8)"
-msgstr ""
-
-#: en/sudo-tutorial.xml:301(para)
-msgid "The <application>sudo(8)</application> program solves the dilemma of how to allow ordinary users access to certain privileged system resources yet still keep the superuser password secret."
-msgstr ""
-
-#: en/sudo-tutorial.xml:304(para)
-msgid "Before granting privileges to a user, the <application>sudo(8)</application> program checks the configuration file <filename>/etc/sudoers</filename> and:"
-msgstr ""
-
-#: en/sudo-tutorial.xml:309(para)
-msgid "Grants privileges to the user without requiring any password at all."
-msgstr ""
-
-#: en/sudo-tutorial.xml:314(para)
-msgid "Grants privileges to the user if, and only if, the user supplies the correct password to prove their identity. Note that this is the password for the user account, <emphasis>not</emphasis> the superuser password."
-msgstr ""
-
-#: en/sudo-tutorial.xml:320(para)
-msgid "Deny the access and notify the system administrator of the failed attempt via an email sent to the root account."
-msgstr ""
-
-#: en/sudo-tutorial.xml:324(para)
-msgid "Log the command, its arguments, and timestamp into the <filename>/var/log/secure</filename> file."
-msgstr ""
-
-#: en/sudo-tutorial.xml:328(para)
-msgid "<application>Sudo(8)</application> keeps a log of all activity in the <filename>/var/log/secure</filename> file. Thus, there is an audit trail recording everything done in the name of the system administrator."
-msgstr ""
-
-#: en/sudo-tutorial.xml:334(title)
-msgid "Controlling Access To sudo(8)"
-msgstr ""
-
-#: en/sudo-tutorial.xml:335(para)
-msgid "The <filename>/etc/sudoers</filename> file configures the programs that users can access using <application>sudo(8)</application>, along with whether or not a password will be needed."
-msgstr ""
-
-#: en/sudo-tutorial.xml:338(para)
-msgid "The system administrator adds users to this file using the <filename>/usr/sbin/visudo</filename> command. Each non-comment line in the file has two parts:"
-msgstr ""
-
-#: en/sudo-tutorial.xml:344(para)
-msgid "A username (\"reynolds\"), or a group name (\"%wheel\")."
-msgstr ""
-
-#: en/sudo-tutorial.xml:347(para)
-msgid "A list of machine names where a program may be run, or the keyword <literal>ALL</literal>. Following an equal sign (<literal>=</literal>), a list of user identities the command may be run as, enclosed in round brackets (parenthesis); the wildcard <literal>ALL</literal> may also appear. Finally, a list of applications which may be run as the named users; the keyword <literal>ALL</literal> is a wildcard."
-msgstr ""
-
-#: en/sudo-tutorial.xml:354(para)
-msgid "The following examples should help make this clear:"
-msgstr ""
-
-#: en/sudo-tutorial.xml:359(title)
-msgid "/etc/sudoers Examples"
-msgstr ""
-
-#: en/sudo-tutorial.xml:363(computeroutput)
-#, no-wrap
-msgid "reynolds ALL=(ALL) ALL"
-msgstr ""
-
-#: en/sudo-tutorial.xml:366(para)
-msgid "User reynolds can execute any command as any user, but must know the password to the reynolds account."
-msgstr ""
-
-#: en/sudo-tutorial.xml:373(computeroutput)
-#, no-wrap
-msgid "reynolds ALL=(root) shutdown"
-msgstr ""
-
-#: en/sudo-tutorial.xml:376(para)
-msgid "User reynolds can execute only command <application>shutdown</application>, but must know the password to the reynolds account."
-msgstr ""
-
-#: en/sudo-tutorial.xml:383(computeroutput)
-#, no-wrap
-msgid "reynolds ALL=(root) NOPASSWD: /usr/bin/id"
-msgstr ""
-
-#: en/sudo-tutorial.xml:386(para)
-msgid "User reynolds can execute only the application <filename>/usr/bin/id</filename>; no password will be needed."
+#: en_US/sudo-tutorial.xml:18(para)
+msgid "WHERE IS MY FDP-INFO, DUDE"
msgstr ""
-#: en/sudo-tutorial.xml:397(title)
-msgid "Using sudo(8)"
+#: en_US/sudo-tutorial.xml:22(title)
+msgid "Introduction"
msgstr ""
-#: en/sudo-tutorial.xml:398(para)
-msgid "Once the system administrator has entered the necessary setup into the <filename>/etc/sudoers</filename> file, users can safely access privileged system resources and activities like this:"
+#: en_US/sudo-tutorial.xml:24(para)
+msgid "The security of a Linux system depends largely on the enforcement of <firstterm>file access permissions</firstterm>. Access to a file is granted or withheld by comparing the identity of the user making the request against permissions associated with the file itself. Most system configuration files and administration activities are accessible only to the privileged system user. That user is commonly known as the <firstterm>superuser</firstterm> or the <firstterm><systemitem class=\"username\">root</systemitem></firstterm> account, and are not available to ordinary users."
msgstr ""
-#: en/sudo-tutorial.xml:401(screen)
-#, no-wrap
-msgid "$ sudo reboot\nPassword:"
+#: en_US/sudo-tutorial.xml:36(para)
+msgid "This tutorial presents a technique for safely granting trusted users access to these programs and files where it would normally be denied. The system administrator can keep the root password concealed, yet still allow selected users to obtain privileged access."
msgstr ""
-#: en/sudo-tutorial.xml:403(para)
-msgid "No awkward quoting on the command line, just prefix the command you want with the word <userinput>sudo</userinput>. If you want to run the command as a user other than <userinput>root</userinput>, just add the <option>-u </option><replaceable>username</replaceable> switch:"
+#: en_US/sudo-tutorial.xml:45(para)
+msgid "When writing about programs or system configuration files, it is customary to indicate which section of the on-line manual pages contain its documentation. For example, section one (1) documents applications, section two (2) documents system calls, and so on. Because sometimes the same name may be both a system call and a library function, knowing the manual page section is important. Compare the results of the following commands:"
msgstr ""
-#: en/sudo-tutorial.xml:407(screen)
-#, no-wrap
-msgid "$ sudo -u reynolds id"
+#: en_US/sudo-tutorial.xml:43(para)
+msgid "Although &PROGRAM;<footnote><placeholder-1/><screen>\n<command>man 2 exit</command> <command>man 3 exit</command>\n</screen></footnote> offers robust control for a networked environment, this tutorial covers only local use. For more information, refer to <ulink url=\"http://www.sudo.ws/sudo\"><filename>http://www.sudo.ws/sudo</filename></ulink>, the official web site."
msgstr ""
-#: en/sudo-tutorial.xml:408(para)
-msgid "There will be a log entry written to the <filename>/var/log/secure</filename> file to show who did the deed."
+#: en_US/sudo-tutorial.xml:67(title)
+msgid "How Linux Controls Access"
msgstr ""
-#: en/sudo-tutorial.xml:411(para)
-msgid "Of course, the sysadmin may have configured <application>sudo(8)</application> not to request a password. In this case, the command is immediately executed although the audit trail entry will still be written."
+#: en_US/sudo-tutorial.xml:68(para)
+msgid "To better understand the benefits of &PROGRAM;, consider how Linux provides access security to the system resources. Linux is a multiuser system, which involves more than simply having a <command>login(1)</command> program. Every time a user attempts to access system resources, the system must ensure that the user is permitted to do so."
msgstr ""
-#: en/sudo-tutorial.xml:419(title)
-msgid "And, In Conclusion"
+#: en_US/sudo-tutorial.xml:76(para)
+msgid "For this reason, Linux assigns each login user a set of <firstterm>credentials</firstterm>. Each user has a unique <firstterm>user-id</firstterm>, or <abbrev>UID</abbrev>, and also has a <firstterm>group-id</firstterm>, or <abbrev>GID</abbrev> which need not be unique. This <abbrev>UID</abbrev>:<abbrev>GID</abbrev> pair form an important component of that user's credentials."
msgstr ""
-#: en/sudo-tutorial.xml:420(para)
-msgid "The <application>sudo(8)</application> program provides a safe, controlled facility that allows a user to run a defined set of programs using the credentials of a defined set of users. The superuser password need never be publicised or compromised, since <application>sudo(8)</application> is controlled from a configuration file crafted by the system administrator."
+#: en_US/sudo-tutorial.xml:85(title)
+msgid "Who Are You?"
msgstr ""
-#: en/sudo-tutorial.xml:424(para)
-msgid "All commands run by <application>sudo(8)</application> are logged to the <filename>/var/log/secure</filename> file, while access violations are reported via email. Traceability results."
+#: en_US/sudo-tutorial.xml:86(para)
+msgid "To gain access to a Linux system, you must prove your identity. While the system administrator decides the security policy for the machine, usually one or more password challenges must be answered. A credentialed user should know the answer to a question that only that user would know: What is the password?"
msgstr ""
-#: en/sudo-tutorial.xml:428(para)
-msgid "From a user perspective, <application>sudo(8)</application> is easy to use: simply prefix the desired command line with the word <wordasword>sudo</wordasword>, press return, and possibly enter a password (but <emphasis>not</emphasis> the superuser password)."
+#: en_US/sudo-tutorial.xml:100(para)
+msgid "Actually, there is more to the authentication process than just a password challenge. The sysadmin can impose additional restrictions such as limiting the time of day when a given user may login, or limiting logins to specific locations."
msgstr ""
-#: en/sudo-tutorial.xml:431(para)
-msgid "End Of Document"
+#: en_US/sudo-tutorial.xml:93(para)
+msgid "This process of proving your identity to the system is known as <firstterm>authentication</firstterm>. Many schemes are available to the system administrator for performing authentication. Once the system authenticates your login request, the kernel has enough information to determine what programs you can run and what files you can access.<footnote><placeholder-1/> sudo-tutorial.xml After a successfully authentication the system uses your UID and GID to control your access to system resources. ======= . After a successful authentication the system uses your uid and gid to control your access to system resources. >>>>>>> 1.3 File Access Permissions Every system resource, whether an application program, directory, or file, has a unique filename. A filename (including the directory path) is a unique identifier for that system resource. The part of Linux that manages these named system resources is known as the file system. In addition to the file c!
ontent itself, the file system keeps extra information about every file. This metadata includes the file's size, disk block locations, and modification and access timestamps. You can see most of this metadata using the ls(1) program: Using ls(1) to examine file permissions $ ls -l /bin/mail -rwxr-xr-x 1 root mail 73588 Apr 4 07:03 /bin/mail Consider two pieces of metadata for a file, its ownership and its access permissions. When a user creates a file, the user credentials are attached to the file, giving that user ownership of that file The chown(1) program allows the ownership credentials to be changed. . In our example, /bin/mail is owned by user root and group mail. The created file also gets a set of file access permissions that describe who may access that file and what kind of access they can get. There are exactly three types of access: read, write, or execute. These are usually abbreviated as rwx. Permissions for a file which could be read, but neither written nor !
executed, would be written as r--. Remember, the notation is p!
ositio
and order matters. Files actually have three sets of permissions. One set is for the file owner, one set is for members of the owner's group, and one set is for everyone else, in that order. May I Access This File, Please? Before a user accesses any file, including running an application program, the kernel must validate the attempt against the file system. It uses a simple but very powerful method to determine whether access should be granted or denied. This algorithm is shown below: Determining File Access if( u.uid == f.uid ) { rwx = perms.owner; } else if( u.gid == f.gid ) { rwx = perms.group; } else { rwx = perms.world; } if( !accessok( access_wanted, rwx ) ) { errno = EPERM; return( -1 ); } do_access(); Assuming the following definitions: u Represents the user credentials containing both the uid and gid. f Represents the file ownership credentials, as shown by the ls -l command. Contains both the uid and gid values identifying the owner of the file. perms The file acc!
ess permissions for the file, including all three sets of permissions: owner, group and world. The key point here is that, although there are three sets of file access permissions associated with the file, exactly one set is used to arbitrate the file access. Emphatically, the sets are not tried in sequence until the access is granted or we run out of sets: you get one and only one try at accessing the file. If you are the owner of the file, the system uses the file owner permissions. If you are not the owner, but a member of the same group as the file, the system uses the group permissions. If you are neither of these, the system checks against the world permissions. </footnote>"
msgstr ""
#. Put one translator per line, in the form of NAME <EMAIL>, YEAR1, YEAR2.
-#: en/sudo-tutorial.xml:0(None)
+#: en_US/sudo-tutorial.xml:0(None)
msgid "translator-credits"
msgstr ""
Index: de.po
===================================================================
RCS file: /cvs/docs/sudo-tutorial/po/de.po,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- de.po 13 Feb 2006 16:08:38 -0000 1.1
+++ de.po 5 Aug 2006 22:49:18 -0000 1.2
@@ -1,7 +1,7 @@
msgid ""
msgstr ""
"Project-Id-Version: PACKAGE VERSION\n"
-"POT-Creation-Date: 2006-02-13 10:03-0600\n"
+"POT-Creation-Date: 2006-08-05 18:48-0400\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL at ADDRESS>\n"
"Language-Team: LANGUAGE <LL at li.org>\n"
@@ -9,400 +9,232 @@
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
-#: en/sudo-tutorial.xml:22(para)
-msgid "WHERE IS MY FDP-INFO, DUDE"
-msgstr ""
-
-#: en/sudo-tutorial.xml:26(title)
-msgid "Introduction"
-msgstr ""
-
-#: en/sudo-tutorial.xml:28(para)
-msgid "The security of a Linux system depends largely on the enforcement of <firstterm>file access permissions</firstterm>. Access to a file is granted or withheld by comparing the identity of the user making the request against permissions associated with the file itself. Most of the configuration files, and many system administration activities, must be accessed by the privileged system user, commonly known as the <firstterm>superuser</firstterm> or the <firstterm>root</firstterm> account, and are not available to ordinary users."
-msgstr ""
-
-#: en/sudo-tutorial.xml:34(para)
-msgid "In this tutorial, we examine a technique for safely granting trusted users access to these programs and files that would normally be denied. The system administrator can keep the root password concealed, yet still allow selected users to obtain privileged access. Everybody wins with this approach."
-msgstr ""
-
-#: en/sudo-tutorial.xml:42(para)
-msgid "When writing about programs or system configuration files, it is customary to indicate which section of the on-line manual pages contain its documentation. For example, section one (1) documents applications; section two (2) documents system calls, section three (3) a library function and so on. Sometimes the same name may be both a system call and a library function, knowing the manual page section is important. Compare the results of \"<userinput>man 2 exit</userinput>\" with \"<userinput>man 3 exit</userinput>\"."
-msgstr ""
-
-#: en/sudo-tutorial.xml:40(para)
-msgid "Although <application>sudo(8)</application><footnote><placeholder-1/></footnote> offers robust control for a networked environment, we shall consider only local use in this tutorial. For more information, consult <ulink url=\"http://www.sudo.ws/sudo\"><filename>http://www.sudo.ws/sudo</filename></ulink>, the official web site."
-msgstr ""
-
-#: en/sudo-tutorial.xml:55(title)
-msgid "How Linux Controls Access"
-msgstr ""
-
-#: en/sudo-tutorial.xml:56(para)
-msgid "To better understand the benefit that <application>sudo(8)</application> brings, let us review how Linux provides access security to the system resources. If you like, skip this section but come back if you need."
-msgstr ""
-
-#: en/sudo-tutorial.xml:60(para)
-msgid "Linux is a multiuser system. There is more to this than simply having a <application>login(1)</application> program: every time a system resource is accessed, care must be taken to ensure that the user attempting the access is permitted to do so."
-msgstr ""
-
-#: en/sudo-tutorial.xml:64(para)
-msgid "For this reason, Linux assigns each login user a set of <firstterm>credentials</firstterm>. Each user has a unique <firstterm>user-id</firstterm>, or <abbrev>UID</abbrev>, and also has a <firstterm>group-id</firstterm>, or <abbrev>GID</abbrev> which need not be unique. This <abbrev>uid</abbrev>:<abbrev>gid</abbrev> pair form an important component of that user's credentials."
-msgstr ""
-
-#: en/sudo-tutorial.xml:70(title)
-msgid "Who Are You?"
-msgstr ""
-
-#: en/sudo-tutorial.xml:71(para)
-msgid "Before you get access to a Linux system, you must prove your identity. While the system administrator decides the security policy for the machine, usually one or more password challenges must be answered. After all, if you really are user <userinput>joesixpack</userinput>, then you should know the answer to a question that only <userinput>joesixpack</userinput> would know: what is the password?"
-msgstr ""
-
-#: en/sudo-tutorial.xml:79(para)
-msgid "Actually, there is more to the authentication process than just a password challenge. The sysadmin can impose restrictions such as limiting the time of day when a given user may login, or requiring that a user make the login attempt from a specific location."
-msgstr ""
-
-#: en/sudo-tutorial.xml:76(para)
-msgid "This process of proving your identity to the system is known as <firstterm>authentication</firstterm>. Many schemes are available to the system administrator, but once the system authenticates your login request, the kernel has enough information to determine what programs you can run or what files you can access<footnote><placeholder-1/></footnote>."
-msgstr ""
-
-#: en/sudo-tutorial.xml:85(para)
-msgid "After a successfully authentication the system uses your uid and gid to control your access to system resources."
-msgstr ""
-
-#: en/sudo-tutorial.xml:90(title)
-msgid "File Access Permissions"
-msgstr ""
-
-#: en/sudo-tutorial.xml:91(para)
-msgid "Every system resource, whether an application program, directory, or file, has a unique name: its <firstterm>filename</firstterm>. You can think of a filename has a unique identifier for that system resource. The part of Linux that manages these named system resources is known as the <firstterm>file system</firstterm>."
-msgstr ""
-
-#: en/sudo-tutorial.xml:96(para)
-msgid "In addition to the file content itself, the file system keeps extra information about every file: its size; disk block locations; and modification and access timestamps. You can see most of this \"meta-data\" using the <application>ls(1)</application> program:"
+#: en_US/doc-entities.xml:4(title)
+msgid "Local entities for Sudo Tutorial"
msgstr ""
-#: en/sudo-tutorial.xml:101(title)
-msgid "Using ls(1) to examine file permissions"
+#: en_US/doc-entities.xml:7(comment)
+msgid "Document name"
msgstr ""
-#: en/sudo-tutorial.xml:102(screen)
-#, no-wrap
-msgid "$ ls -l /bin/mail\n-rwxr-xr-x 1 root mail 73588 Apr 4 07:03 /bin/mail"
+#: en_US/doc-entities.xml:8(text)
+msgid "sudo-tutorial"
msgstr ""
-#: en/sudo-tutorial.xml:105(para)
-msgid "We are most interested in two groups of information about the file: its ownership and its access permissions."
+#: en_US/doc-entities.xml:11(comment)
+msgid "Version number"
msgstr ""
-#: en/sudo-tutorial.xml:110(para)
-msgid "The <application>chown(1)</application> program allows the ownership credentials to be changed, but that is another HOWTO."
+#: en_US/doc-entities.xml:12(text)
+msgid "0.14.1"
msgstr ""
-#: en/sudo-tutorial.xml:108(para)
-msgid "When a user creates a file, the user credentials are attached to the file, giving that user <emphasis>ownership</emphasis> of that file<footnote><placeholder-1/></footnote>. In our example, <filename>/bin/mail</filename> is owned by user <userinput>root</userinput> and group <userinput>mail</userinput>."
+#: en_US/doc-entities.xml:15(comment)
+msgid "Date of last revision"
msgstr ""
-#: en/sudo-tutorial.xml:116(para)
-msgid "The created file also gets a set of file access permissions that describe who may access that file and what kind of access they can get. There are exactly three types of access: read, write, or execute usually abbreviated as <abbrev>rwx</abbrev>. Permissions for a file which could be read, but neither written nor executed, would be written as <abbrev>r--</abbrev>. Remember, the notation is positional and order matters."
+#: en_US/doc-entities.xml:16(text)
+msgid "2006-01-21"
msgstr ""
-#: en/sudo-tutorial.xml:122(para)
-msgid "Files actually have three sets of permissions: one set for the file owner, one set for members of the owner's group; and one set for everyone else; again order matters, the owner permissions are first, followed by the group and then the world permissions. In the next section, we shall see how Linux puts all this together."
+#: en_US/doc-entities.xml:19(comment)
+msgid "Document ID"
msgstr ""
-#: en/sudo-tutorial.xml:128(title)
-msgid "May I Access This File, Please?"
+#: en_US/doc-entities.xml:20(text)
+msgid ""
+"<use entity=\"DOCNAME\"/>-<use entity=\"DOCVERSION\"/> (<use entity=\"DOCDATE"
+"\"/>)"
msgstr ""
-#: en/sudo-tutorial.xml:129(para)
-msgid "Before any file is accessed, and this includes running an application program, the file system must validate the attempt. There is a very simple, but very powerful, method used to determine whether access should be granted or denied. This algorithm is shown below:"
+#: en_US/doc-entities.xml:26(comment)
+msgid "Name of program"
msgstr ""
-#: en/sudo-tutorial.xml:135(title)
-msgid "Determining File Access"
+#: en_US/doc-entities.xml:27(text)
+msgid "<command>sudo(8)</command>"
msgstr ""
-#: en/sudo-tutorial.xml:136(programlisting)
-#, no-wrap
-msgid "if( u.uid == f.uid ) {\n rwx = perms.owner;\n} else if( u.gid == f.gid ) {\n rwx = perms.group;\n} else {\n rwx = perms.world;\n}\nif( !accessok( access_wanted, rwx ) ) {\n errno = EPERM;\n return( -1 );\n}\ndo_access();"
+#: en_US/rpm-info.xml:9(rights)
+msgid "OPL"
msgstr ""
-#: en/sudo-tutorial.xml:149(para)
-msgid "Assuming the following definitions:"
+#: en_US/rpm-info.xml:10(version)
+msgid "1.0"
msgstr ""
-#: en/sudo-tutorial.xml:154(glossterm)
-msgid "u"
+#: en_US/rpm-info.xml:13(year)
+msgid "2005"
msgstr ""
-#: en/sudo-tutorial.xml:156(para)
-msgid "Represents the user credentials containing both the <abbrev>uid</abbrev> and <abbrev>gid</abbrev>."
+#: en_US/rpm-info.xml:14(year)
+msgid "2006"
msgstr ""
-#: en/sudo-tutorial.xml:162(glossterm)
-msgid "f"
+#: en_US/rpm-info.xml:15(holder)
+msgid "Tommy Reynolds"
msgstr ""
-#: en/sudo-tutorial.xml:164(para)
-msgid "Represents the file ownership credentials, as shown by the <command>ls -l</command> command. Contains both the <abbrev>uid</abbrev> and <abbrev>gid</abbrev> values identifying the owner of the file."
+#: en_US/rpm-info.xml:17(title)
+msgid "Sudo Tutorial"
msgstr ""
-#: en/sudo-tutorial.xml:171(glossterm)
-msgid "perms"
+#: en_US/rpm-info.xml:18(desc)
+msgid "Guide to using sudo to perform tasks as another user"
msgstr ""
-#: en/sudo-tutorial.xml:172(para)
-msgid "The file access permissions for the file, including all three sets of permissions: owner, group and world."
+#: en_US/rpm-info.xml:22(details)
+msgid "Dummy version"
msgstr ""
-#: en/sudo-tutorial.xml:177(para)
-msgid "The key point here is that, although there are three sets of file access permissions associated with the file, exactly <emphasis>one</emphasis> set is used to arbitrate the file access. Emphatically, the sets are <emphasis>not</emphasis> tried in sequence until the access is granted or we run out of sets: you get one and only one try at accessing the file."
-msgstr ""
-
-#: en/sudo-tutorial.xml:181(para)
-msgid "If you are the owner of the file, the system uses the file owner permissions. If you are not the owner, but a member of the same group as the file, the system uses the group permissions. If you are neither of these, the system checks against the world permissions."
-msgstr ""
-
-#: en/sudo-tutorial.xml:190(title)
-msgid "What Not To Do"
-msgstr ""
-
-#: en/sudo-tutorial.xml:192(para)
-msgid "As desirable as enforcing file access permissions are on a Linux system, there are valid reasons for needing to bypass the checking. Several users run the same program to generate project files that must be accessible to all; a printer queue is hung and the sysadmin has given a local user authority to restart the printer daemon; an ordinary user wants to mount an NFS hierarchy from a file server; a mail delivery program must be able to write into mail files writable only by the mail recipient; and finally, a local user is empowered to perform designated sysadmin functions but the real sysadmin does not want to grant blanket permission to alter everything on the system."
-msgstr ""
-
-#: en/sudo-tutorial.xml:201(para)
-msgid "Below we will look at common methods of working around the Linux file access permissions scheme and point out some short-comings of each technique. All these methods \"work\", in the sense that they function correctly but incur unnecessary security risks. In the next section, we show how <application>sudo(8)</application> controls most of these risks."
-msgstr ""
-
-#: en/sudo-tutorial.xml:208(title)
-msgid "Perhaps You Have Heard Of The su(1) Application?"
-msgstr ""
-
-#: en/sudo-tutorial.xml:209(para)
-msgid "One technique, used since <trademark>UNIX</trademark> systems began, is for the user to temporarily assume the privileges of the superuser account. The <application>su(1)</application> changes the identification for the current user by <emphasis>s</emphasis>ubstituting <emphasis>u</emphasis>ser credentials."
-msgstr ""
-
-#: en/sudo-tutorial.xml:215(title)
-msgid "Traditional Approach Using su(1)"
-msgstr ""
-
-#: en/sudo-tutorial.xml:216(screen)
-#, no-wrap
-msgid "$ id\nuid=500(reynolds) gid=500(reynolds) groups=500(reynolds)\n$ su -c id\nPassword:\nuid=0(root) gid=0(root) groups=0(root),1(bin)..."
-msgstr ""
-
-#: en/sudo-tutorial.xml:223(para)
-msgid "There are some problems with this approach:"
-msgstr ""
-
-#: en/sudo-tutorial.xml:229(para)
-msgid "The superuser password is compromised."
-msgstr ""
-
-#: en/sudo-tutorial.xml:232(para)
-msgid "Once anyone other than the system administrator knows the superuser password, everyone will know it. He that wishes to keep a secret must keep it a secret that he has a secret to keep. Promises not to tell are not sufficient security."
-msgstr ""
-
-#: en/sudo-tutorial.xml:239(para)
-msgid "There is no audit trail."
-msgstr ""
-
-#: en/sudo-tutorial.xml:245(para)
-msgid "In security parlance, \"to trust\" is identical to \"be at risk from\"."
-msgstr ""
-
-#: en/sudo-tutorial.xml:242(para)
-msgid "With a superuser shell, a user can do anything that the root account can do. We must trust<footnote><placeholder-1/></footnote>the user to access only the files and programs they claimed to need."
-msgstr ""
-
-#: en/sudo-tutorial.xml:255(title)
-msgid "Please, No Setuid Shell Scripts"
-msgstr ""
-
-#: en/sudo-tutorial.xml:256(para)
-msgid "Another technology, used by the <application>su(1)</application> program, takes advantage of a neat feature."
-msgstr ""
-
-#: en/sudo-tutorial.xml:259(para)
-msgid "Normally, the files accessible to an application or shell depend on who is executing that program. Recall those <emphasis>credentials</emphasis> mentioned earlier? An application executes using the credentials of the user who runs the program."
-msgstr ""
-
-#: en/sudo-tutorial.xml:264(para)
-msgid "Stop, wait, there's more!"
-msgstr ""
-
-#: en/sudo-tutorial.xml:267(para)
-msgid "Files have access permissions but since a program is stored in a file, the program has file access permissions, too."
-msgstr ""
-
-#: en/sudo-tutorial.xml:272(para)
-msgid "The commands:"
-msgstr ""
-
-#: en/sudo-tutorial.xml:277(para)
-msgid "would give whomever runs <filename>/bin/foo</filename> the same privileges that the superuser account would have while running the same application."
-msgstr ""
-
-#: en/sudo-tutorial.xml:270(para)
-msgid "By setting a special flag, called the <firstterm>set user id bit</firstterm> or <function>setuid(2)</function>, we can cause the system to check \"credentials\" made from the program file access permissions, instead of using the credentials for the user running the application<footnote><placeholder-1/><screen width=\"60\"># chown root:root /bin/foo\n# chmod 06555 /bin/foo</screen><placeholder-2/></footnote>."
-msgstr ""
-
-#: en/sudo-tutorial.xml:282(para)
-msgid "This ability to use the credentials of an application, instead of those of the user, can be a great boon to multiuser applications such as databases or email delivery agents. The feature has its proper use on a Linux system."
-msgstr ""
-
-#: en/sudo-tutorial.xml:286(para)
-msgid "As useful as it is, one must resist the temptation to make a shell program, such as <filename>/bin/bash</filename>, or a shell script, such as <filename>/usr/local/bin/run_as_root</filename>, be set user ID to root."
-msgstr ""
-
-#: en/sudo-tutorial.xml:289(para)
-msgid "If this were to be done, then <emphasis>any</emphasis> user running that script or application would be able to access any file that the root account could access."
-msgstr ""
-
-#: en/sudo-tutorial.xml:292(para)
-msgid "Again, the objections to this method a similar to those we mentioned for the <application>su(1)</application> program: no control, and no traceability."
-msgstr ""
-
-#: en/sudo-tutorial.xml:300(title)
-msgid "A Safer Alternative: sudo(8)"
-msgstr ""
-
-#: en/sudo-tutorial.xml:301(para)
-msgid "The <application>sudo(8)</application> program solves the dilemma of how to allow ordinary users access to certain privileged system resources yet still keep the superuser password secret."
-msgstr ""
-
-#: en/sudo-tutorial.xml:304(para)
-msgid "Before granting privileges to a user, the <application>sudo(8)</application> program checks the configuration file <filename>/etc/sudoers</filename> and:"
-msgstr ""
-
-#: en/sudo-tutorial.xml:309(para)
-msgid "Grants privileges to the user without requiring any password at all."
-msgstr ""
-
-#: en/sudo-tutorial.xml:314(para)
-msgid "Grants privileges to the user if, and only if, the user supplies the correct password to prove their identity. Note that this is the password for the user account, <emphasis>not</emphasis> the superuser password."
-msgstr ""
-
-#: en/sudo-tutorial.xml:320(para)
-msgid "Deny the access and notify the system administrator of the failed attempt via an email sent to the root account."
-msgstr ""
-
-#: en/sudo-tutorial.xml:324(para)
-msgid "Log the command, its arguments, and timestamp into the <filename>/var/log/secure</filename> file."
-msgstr ""
-
-#: en/sudo-tutorial.xml:328(para)
-msgid "<application>Sudo(8)</application> keeps a log of all activity in the <filename>/var/log/secure</filename> file. Thus, there is an audit trail recording everything done in the name of the system administrator."
-msgstr ""
-
-#: en/sudo-tutorial.xml:334(title)
-msgid "Controlling Access To sudo(8)"
-msgstr ""
-
-#: en/sudo-tutorial.xml:335(para)
-msgid "The <filename>/etc/sudoers</filename> file configures the programs that users can access using <application>sudo(8)</application>, along with whether or not a password will be needed."
-msgstr ""
-
-#: en/sudo-tutorial.xml:338(para)
-msgid "The system administrator adds users to this file using the <filename>/usr/sbin/visudo</filename> command. Each non-comment line in the file has two parts:"
-msgstr ""
-
-#: en/sudo-tutorial.xml:344(para)
-msgid "A username (\"reynolds\"), or a group name (\"%wheel\")."
-msgstr ""
-
-#: en/sudo-tutorial.xml:347(para)
-msgid "A list of machine names where a program may be run, or the keyword <literal>ALL</literal>. Following an equal sign (<literal>=</literal>), a list of user identities the command may be run as, enclosed in round brackets (parenthesis); the wildcard <literal>ALL</literal> may also appear. Finally, a list of applications which may be run as the named users; the keyword <literal>ALL</literal> is a wildcard."
-msgstr ""
-
-#: en/sudo-tutorial.xml:354(para)
-msgid "The following examples should help make this clear:"
-msgstr ""
-
-#: en/sudo-tutorial.xml:359(title)
-msgid "/etc/sudoers Examples"
-msgstr ""
-
-#: en/sudo-tutorial.xml:363(computeroutput)
-#, no-wrap
-msgid "reynolds ALL=(ALL) ALL"
-msgstr ""
-
-#: en/sudo-tutorial.xml:366(para)
-msgid "User reynolds can execute any command as any user, but must know the password to the reynolds account."
-msgstr ""
-
-#: en/sudo-tutorial.xml:373(computeroutput)
-#, no-wrap
-msgid "reynolds ALL=(root) shutdown"
-msgstr ""
-
-#: en/sudo-tutorial.xml:376(para)
-msgid "User reynolds can execute only command <application>shutdown</application>, but must know the password to the reynolds account."
-msgstr ""
-
-#: en/sudo-tutorial.xml:383(computeroutput)
-#, no-wrap
-msgid "reynolds ALL=(root) NOPASSWD: /usr/bin/id"
-msgstr ""
-
-#: en/sudo-tutorial.xml:386(para)
-msgid "User reynolds can execute only the application <filename>/usr/bin/id</filename>; no password will be needed."
-msgstr ""
-
-#: en/sudo-tutorial.xml:397(title)
-msgid "Using sudo(8)"
-msgstr ""
-
-#: en/sudo-tutorial.xml:398(para)
-msgid "Once the system administrator has entered the necessary setup into the <filename>/etc/sudoers</filename> file, users can safely access privileged system resources and activities like this:"
-msgstr ""
-
-#: en/sudo-tutorial.xml:401(screen)
-#, no-wrap
-msgid "$ sudo reboot\nPassword:"
-msgstr ""
-
-#: en/sudo-tutorial.xml:403(para)
-msgid "No awkward quoting on the command line, just prefix the command you want with the word <userinput>sudo</userinput>. If you want to run the command as a user other than <userinput>root</userinput>, just add the <option>-u </option><replaceable>username</replaceable> switch:"
-msgstr ""
-
-#: en/sudo-tutorial.xml:407(screen)
-#, no-wrap
-msgid "$ sudo -u reynolds id"
-msgstr ""
-
-#: en/sudo-tutorial.xml:408(para)
-msgid "There will be a log entry written to the <filename>/var/log/secure</filename> file to show who did the deed."
+#: en_US/sudo-tutorial.xml:18(para)
+msgid "WHERE IS MY FDP-INFO, DUDE"
msgstr ""
-#: en/sudo-tutorial.xml:411(para)
-msgid "Of course, the sysadmin may have configured <application>sudo(8)</application> not to request a password. In this case, the command is immediately executed although the audit trail entry will still be written."
+#: en_US/sudo-tutorial.xml:22(title)
+msgid "Introduction"
msgstr ""
-#: en/sudo-tutorial.xml:419(title)
-msgid "And, In Conclusion"
+#: en_US/sudo-tutorial.xml:24(para)
+msgid ""
+"The security of a Linux system depends largely on the enforcement of "
+"<firstterm>file access permissions</firstterm>. Access to a file is granted "
+"or withheld by comparing the identity of the user making the request against "
+"permissions associated with the file itself. Most system configuration files "
+"and administration activities are accessible only to the privileged system "
+"user. That user is commonly known as the <firstterm>superuser</firstterm> or "
+"the <firstterm><systemitem class=\"username\">root</systemitem></firstterm> "
+"account, and are not available to ordinary users."
+msgstr ""
+
+#: en_US/sudo-tutorial.xml:36(para)
+msgid ""
+"This tutorial presents a technique for safely granting trusted users access "
+"to these programs and files where it would normally be denied. The system "
+"administrator can keep the root password concealed, yet still allow selected "
+"users to obtain privileged access."
+msgstr ""
+
+#: en_US/sudo-tutorial.xml:45(para)
+msgid ""
+"When writing about programs or system configuration files, it is customary "
+"to indicate which section of the on-line manual pages contain its "
+"documentation. For example, section one (1) documents applications, section "
+"two (2) documents system calls, and so on. Because sometimes the same name "
+"may be both a system call and a library function, knowing the manual page "
+"section is important. Compare the results of the following commands:"
+msgstr ""
+
+#: en_US/sudo-tutorial.xml:43(para)
+msgid ""
+"Although &PROGRAM;<footnote><placeholder-1/><screen>\n"
+"<command>man 2 exit</command> <command>man 3 exit</command>\n"
+"</screen></footnote> offers robust control for a networked environment, this "
+"tutorial covers only local use. For more information, refer to <ulink url="
+"\"http://www.sudo.ws/sudo\"><filename>http://www.sudo.ws/sudo</filename></"
+"ulink>, the official web site."
msgstr ""
-#: en/sudo-tutorial.xml:420(para)
-msgid "The <application>sudo(8)</application> program provides a safe, controlled facility that allows a user to run a defined set of programs using the credentials of a defined set of users. The superuser password need never be publicised or compromised, since <application>sudo(8)</application> is controlled from a configuration file crafted by the system administrator."
+#: en_US/sudo-tutorial.xml:67(title)
+msgid "How Linux Controls Access"
msgstr ""
-#: en/sudo-tutorial.xml:424(para)
-msgid "All commands run by <application>sudo(8)</application> are logged to the <filename>/var/log/secure</filename> file, while access violations are reported via email. Traceability results."
+#: en_US/sudo-tutorial.xml:68(para)
+msgid ""
+"To better understand the benefits of &PROGRAM;, consider how Linux provides "
+"access security to the system resources. Linux is a multiuser system, which "
+"involves more than simply having a <command>login(1)</command> program. "
+"Every time a user attempts to access system resources, the system must "
+"ensure that the user is permitted to do so."
+msgstr ""
+
+#: en_US/sudo-tutorial.xml:76(para)
+msgid ""
+"For this reason, Linux assigns each login user a set of "
+"<firstterm>credentials</firstterm>. Each user has a unique <firstterm>user-"
+"id</firstterm>, or <abbrev>UID</abbrev>, and also has a <firstterm>group-id</"
+"firstterm>, or <abbrev>GID</abbrev> which need not be unique. This "
+"<abbrev>UID</abbrev>:<abbrev>GID</abbrev> pair form an important component "
+"of that user's credentials."
msgstr ""
-#: en/sudo-tutorial.xml:428(para)
-msgid "From a user perspective, <application>sudo(8)</application> is easy to use: simply prefix the desired command line with the word <wordasword>sudo</wordasword>, press return, and possibly enter a password (but <emphasis>not</emphasis> the superuser password)."
+#: en_US/sudo-tutorial.xml:85(title)
+msgid "Who Are You?"
msgstr ""
-#: en/sudo-tutorial.xml:431(para)
-msgid "End Of Document"
+#: en_US/sudo-tutorial.xml:86(para)
+msgid ""
+"To gain access to a Linux system, you must prove your identity. While the "
+"system administrator decides the security policy for the machine, usually "
+"one or more password challenges must be answered. A credentialed user should "
+"know the answer to a question that only that user would know: What is the "
+"password?"
+msgstr ""
+
+#: en_US/sudo-tutorial.xml:100(para)
+msgid ""
+"Actually, there is more to the authentication process than just a password "
+"challenge. The sysadmin can impose additional restrictions such as limiting "
+"the time of day when a given user may login, or limiting logins to specific "
+"locations."
+msgstr ""
+
+#: en_US/sudo-tutorial.xml:93(para)
+msgid ""
+"This process of proving your identity to the system is known as "
+"<firstterm>authentication</firstterm>. Many schemes are available to the "
+"system administrator for performing authentication. Once the system "
+"authenticates your login request, the kernel has enough information to "
+"determine what programs you can run and what files you can access."
+"<footnote><placeholder-1/> sudo-tutorial.xml After a successfully "
+"authentication the system uses your UID and GID to control your access to "
+"system resources. ======= . After a successful authentication the system "
+"uses your uid and gid to control your access to system resources. >>"
+">>>>> 1.3 File Access Permissions Every system resource, "
+"whether an application program, directory, or file, has a unique filename. A "
+"filename (including the directory path) is a unique identifier for that "
+"system resource. The part of Linux that manages these named system resources "
+"is known as the file system. In addition to the file content itself, the "
+"file system keeps extra information about every file. This metadata includes "
+"the file's size, disk block locations, and modification and access "
+"timestamps. You can see most of this metadata using the ls(1) program: Using "
+"ls(1) to examine file permissions $ ls -l /bin/mail -rwxr-xr-x 1 root mail "
+"73588 Apr 4 07:03 /bin/mail Consider two pieces of metadata for a file, its "
+"ownership and its access permissions. When a user creates a file, the user "
+"credentials are attached to the file, giving that user ownership of that "
+"file The chown(1) program allows the ownership credentials to be changed. . "
+"In our example, /bin/mail is owned by user root and group mail. The created "
+"file also gets a set of file access permissions that describe who may access "
+"that file and what kind of access they can get. There are exactly three "
+"types of access: read, write, or execute. These are usually abbreviated as "
+"rwx. Permissions for a file which could be read, but neither written nor "
+"executed, would be written as r--. Remember, the notation is positional and "
+"order matters. Files actually have three sets of permissions. One set is for "
+"the file owner, one set is for members of the owner's group, and one set is "
+"for everyone else, in that order. May I Access This File, Please? Before a "
+"user accesses any file, including running an application program, the kernel "
+"must validate the attempt against the file system. It uses a simple but very "
+"powerful method to determine whether access should be granted or denied. "
+"This algorithm is shown below: Determining File Access if( u.uid == f.uid ) "
+"{ rwx = perms.owner; } else if( u.gid == f.gid ) { rwx = perms.group; } else "
+"{ rwx = perms.world; } if( !accessok( access_wanted, rwx ) ) { errno = "
+"EPERM; return( -1 ); } do_access(); Assuming the following definitions: u "
+"Represents the user credentials containing both the uid and gid. f "
+"Represents the file ownership credentials, as shown by the ls -l command. "
+"Contains both the uid and gid values identifying the owner of the file. "
+"perms The file access permissions for the file, including all three sets of "
+"permissions: owner, group and world. The key point here is that, although "
+"there are three sets of file access permissions associated with the file, "
+"exactly one set is used to arbitrate the file access. Emphatically, the sets "
+"are not tried in sequence until the access is granted or we run out of sets: "
+"you get one and only one try at accessing the file. If you are the owner of "
+"the file, the system uses the file owner permissions. If you are not the "
+"owner, but a member of the same group as the file, the system uses the group "
+"permissions. If you are neither of these, the system checks against the "
+"world permissions. </footnote>"
msgstr ""
#. Put one translator per line, in the form of NAME <EMAIL>, YEAR1, YEAR2.
-#: en/sudo-tutorial.xml:0(None)
+#: en_US/sudo-tutorial.xml:0(None)
msgid "translator-credits"
msgstr ""
-
Index: pt.po
===================================================================
RCS file: /cvs/docs/sudo-tutorial/po/pt.po,v
retrieving revision 1.6
retrieving revision 1.7
diff -u -r1.6 -r1.7
--- pt.po 5 Jul 2006 09:57:33 -0000 1.6
+++ pt.po 5 Aug 2006 22:49:18 -0000 1.7
@@ -2,7 +2,7 @@
msgstr ""
"Project-Id-Version: sudo-tutorial\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
-"POT-Creation-Date: 2006-07-05 02:22+0100\n"
+"POT-Creation-Date: 2006-08-05 18:48-0400\n"
"PO-Revision-Date: 2006-07-05 10:53+0100\n"
"Last-Translator: José Nuno Coelho Pires <jncp at netcabo.pt>\n"
"Language-Team: pt <kde-i18n-pt at kde.org>\n"
@@ -18,6 +18,86 @@
"X-POFile-SpellExtra: chown log tilizador sabê login Abr fazeracesso Sudo\n"
"X-POFile-SpellExtra: Tommy\n"
+#: en_US/doc-entities.xml:4(title)
+msgid "Local entities for Sudo Tutorial"
+msgstr ""
+
+#: en_US/doc-entities.xml:7(comment)
+msgid "Document name"
+msgstr ""
+
+#: en_US/doc-entities.xml:8(text)
+#, fuzzy
+msgid "sudo-tutorial"
+msgstr "Tutorial do Sudo"
+
+#: en_US/doc-entities.xml:11(comment)
+msgid "Version number"
+msgstr ""
+
+#: en_US/doc-entities.xml:12(text)
+msgid "0.14.1"
+msgstr ""
+
+#: en_US/doc-entities.xml:15(comment)
+msgid "Date of last revision"
+msgstr ""
+
+#: en_US/doc-entities.xml:16(text)
+msgid "2006-01-21"
+msgstr ""
+
+#: en_US/doc-entities.xml:19(comment)
+#, fuzzy
+msgid "Document ID"
+msgstr "Fim do Documento"
+
+#: en_US/doc-entities.xml:20(text)
+msgid ""
+"<use entity=\"DOCNAME\"/>-<use entity=\"DOCVERSION\"/> (<use entity=\"DOCDATE"
+"\"/>)"
+msgstr ""
+
+#: en_US/doc-entities.xml:26(comment)
+msgid "Name of program"
+msgstr ""
+
+#: en_US/doc-entities.xml:27(text)
+msgid "<command>sudo(8)</command>"
+msgstr ""
+
+#: en_US/rpm-info.xml:9(rights)
+msgid "OPL"
+msgstr ""
+
+#: en_US/rpm-info.xml:10(version)
+msgid "1.0"
+msgstr ""
+
+#: en_US/rpm-info.xml:13(year)
+msgid "2005"
+msgstr ""
+
+#: en_US/rpm-info.xml:14(year)
+msgid "2006"
+msgstr ""
+
+#: en_US/rpm-info.xml:15(holder)
+msgid "Tommy Reynolds"
+msgstr "Tommy Reynolds"
+
+#: en_US/rpm-info.xml:17(title)
+msgid "Sudo Tutorial"
+msgstr "Tutorial do Sudo"
+
+#: en_US/rpm-info.xml:18(desc)
+msgid "Guide to using sudo to perform tasks as another user"
+msgstr ""
+
+#: en_US/rpm-info.xml:22(details)
+msgid "Dummy version"
+msgstr ""
+
#: en_US/sudo-tutorial.xml:18(para)
msgid "WHERE IS MY FDP-INFO, DUDE"
msgstr "ONDE ESTà A MINHA INFORMAÇÃO DO FDP, PÃ"
@@ -27,15 +107,16 @@
msgstr "Introdução"
#: en_US/sudo-tutorial.xml:24(para)
+#, fuzzy
msgid ""
"The security of a Linux system depends largely on the enforcement of "
"<firstterm>file access permissions</firstterm>. Access to a file is granted "
"or withheld by comparing the identity of the user making the request against "
-"permissions associated with the file itself. Most of the configuration "
-"files, and many system administration activities, must be accessed by the "
-"privileged system user, commonly known as the <firstterm>superuser</"
-"firstterm> or the <firstterm>root</firstterm> account, and are not available "
-"to ordinary users."
+"permissions associated with the file itself. Most system configuration files "
+"and administration activities are accessible only to the privileged system "
+"user. That user is commonly known as the <firstterm>superuser</firstterm> or "
+"the <firstterm><systemitem class=\"username\">root</systemitem></firstterm> "
+"account, and are not available to ordinary users."
msgstr ""
"A segurança de um sistema Linux depende em grande medida da aplicação de "
"<firstterm>permissões de acesso aos ficheiros</firstterm>. O acesso a um "
@@ -47,12 +128,13 @@
"firstterm> ou a conta do <firstterm>root</firstterm> e não estão disponÃveis "
"aos utilizadores normais."
-#: en_US/sudo-tutorial.xml:30(para)
+#: en_US/sudo-tutorial.xml:36(para)
+#, fuzzy
msgid ""
-"In this tutorial, we examine a technique for safely granting trusted users "
-"access to these programs and files that would normally be denied. The system "
+"This tutorial presents a technique for safely granting trusted users access "
+"to these programs and files where it would normally be denied. The system "
"administrator can keep the root password concealed, yet still allow selected "
-"users to obtain privileged access. Everybody wins with this approach."
+"users to obtain privileged access."
msgstr ""
"Neste tutorial, será examinada uma técnica para ceder em segurança aos "
"utilizadores de confiança o acesso a estes programas e ficheiros que seriam, "
@@ -60,61 +142,63 @@
"'root' escondida, permitindo à mesma o acesso privilegiado a utilizadores "
"seleccionados. Todos ficam a ganhar com esta aproximação."
-#: en_US/sudo-tutorial.xml:38(para)
+#: en_US/sudo-tutorial.xml:45(para)
+#, fuzzy
msgid ""
"When writing about programs or system configuration files, it is customary "
"to indicate which section of the on-line manual pages contain its "
-"documentation. For example, section one (1) documents applications; section "
-"two (2) documents system calls, section three (3) a library function and so "
-"on. Sometimes the same name may be both a system call and a library "
-"function, knowing the manual page section is important. Compare the results "
-"of \"<userinput>man 2 exit</userinput>\" with \"<userinput>man 3 exit</"
+"documentation. For example, section one (1) documents applications, section "
+"two (2) documents system calls, and so on. Because sometimes the same name "
+"may be both a system call and a library function, knowing the manual page "
+"section is important. Compare the results of the following commands:"
+msgstr ""
+"Ao escrever sobre os programas ou ficheiros de configuração do sistema, é "
+"normal indicar a secção das páginas de manual que contêm a sua documentação. "
+"Por exemplo, a secção um (1) documenta as aplicações; a secção dois (2) "
+"documenta as chamadas de sistema; a secção três (3) as funções de "
+"bibliotecas, e assim por diante. Em alguns casos, o mesmo nome poderá ser "
+"tanto uma chamada de sistema como uma função da biblioteca, pelo que "
+"conhecer a secção da página de manual é importante. Compare os resultados do "
+"\"<userinput>man 2 exit</userinput>\" com os do \"<userinput>man 3 exit</"
"userinput>\"."
-msgstr "Ao escrever sobre os programas ou ficheiros de configuração do sistema, é normal indicar a secção das páginas de manual que contêm a sua documentação. Por exemplo, a secção um (1) documenta as aplicações; a secção dois (2) documenta as chamadas de sistema; a secção três (3) as funções de bibliotecas, e assim por diante. Em alguns casos, o mesmo nome poderá ser tanto uma chamada de sistema como uma função da biblioteca, pelo que conhecer a secção da página de manual é importante. Compare os resultados do \"<userinput>man 2 exit</userinput>\" com os do \"<userinput>man 3 exit</userinput>\"."
-#: en_US/sudo-tutorial.xml:36(para)
+#: en_US/sudo-tutorial.xml:43(para)
+#, fuzzy
msgid ""
-"Although <application>sudo(8)</application><footnote><placeholder-1/></"
-"footnote> offers robust control for a networked environment, we shall "
-"consider only local use in this tutorial. For more information, consult "
-"<ulink url=\"http://www.sudo.ws/sudo\"><filename>http://www.sudo.ws/sudo</"
-"filename></ulink>, the official web site."
-msgstr "Ainda que o <application>sudo(8)</application><footnote><placeholder-1/></footnote> ofereça um controlo robusto para um ambiente em rede, dever-se-á considerar apenas o uso local neste tutorial. Para mais informações, consulte o <ulink url=\"http://www.sudo.ws/sudo\"><filename>http://www.sudo.ws/sudo</filename></ulink>, a página Web oficial."
+"Although &PROGRAM;<footnote><placeholder-1/><screen>\n"
+"<command>man 2 exit</command> <command>man 3 exit</command>\n"
+"</screen></footnote> offers robust control for a networked environment, this "
+"tutorial covers only local use. For more information, refer to <ulink url="
+"\"http://www.sudo.ws/sudo\"><filename>http://www.sudo.ws/sudo</filename></"
+"ulink>, the official web site."
+msgstr ""
+"Ainda que o <application>sudo(8)</application><footnote><placeholder-1/></"
+"footnote> ofereça um controlo robusto para um ambiente em rede, dever-se-á "
+"considerar apenas o uso local neste tutorial. Para mais informações, "
+"consulte o <ulink url=\"http://www.sudo.ws/sudo\"><filename>http://www.sudo."
+"ws/sudo</filename></ulink>, a página Web oficial."
-#: en_US/sudo-tutorial.xml:51(title)
+#: en_US/sudo-tutorial.xml:67(title)
msgid "How Linux Controls Access"
msgstr "Como o Linux Controla o Acesso"
-#: en_US/sudo-tutorial.xml:52(para)
+#: en_US/sudo-tutorial.xml:68(para)
msgid ""
-"To better understand the benefit that <application>sudo(8)</application> "
-"brings, let us review how Linux provides access security to the system "
-"resources. If you like, skip this section but come back if you need."
-msgstr ""
-"Para compreender melhor o benefÃcio que o <application>sudo(8)</application> "
-"traz, façamos uma revisão da forma como o Linux oferece a segurança de "
-"acesso aos recursos do sistema. Se preferir, salte esta secção, mas volte se "
-"necessitar."
-
-#: en_US/sudo-tutorial.xml:56(para)
-msgid ""
-"Linux is a multiuser system. There is more to this than simply having a "
-"<application>login(1)</application> program: every time a system resource is "
-"accessed, care must be taken to ensure that the user attempting the access "
-"is permitted to do so."
-msgstr ""
-"O Linux é um sistema multi-utilizador. Isto é muito mais do que ter "
-"simplesmente um programa <application>login(1)</application>: de cada vez "
-"que acede a um recurso do sistema, deverá ter cuidado para garantir que o "
-"utilizador que tenta o acesso tem permissões para tal."
+"To better understand the benefits of &PROGRAM;, consider how Linux provides "
+"access security to the system resources. Linux is a multiuser system, which "
+"involves more than simply having a <command>login(1)</command> program. "
+"Every time a user attempts to access system resources, the system must "
+"ensure that the user is permitted to do so."
+msgstr ""
-#: en_US/sudo-tutorial.xml:60(para)
+#: en_US/sudo-tutorial.xml:76(para)
+#, fuzzy
msgid ""
"For this reason, Linux assigns each login user a set of "
"<firstterm>credentials</firstterm>. Each user has a unique <firstterm>user-"
"id</firstterm>, or <abbrev>UID</abbrev>, and also has a <firstterm>group-id</"
"firstterm>, or <abbrev>GID</abbrev> which need not be unique. This "
-"<abbrev>uid</abbrev>:<abbrev>gid</abbrev> pair form an important component "
+"<abbrev>UID</abbrev>:<abbrev>GID</abbrev> pair form an important component "
"of that user's credentials."
msgstr ""
"Por essa razão, o Linux atribui a cada utilizador autenticado um conjunto de "
@@ -124,18 +208,18 @@
"ser único. Este par <abbrev>UID</abbrev>:<abbrev>GID</abbrev> forma um "
"componente importante nas credenciais desse utilizador."
-#: en_US/sudo-tutorial.xml:66(title)
+#: en_US/sudo-tutorial.xml:85(title)
msgid "Who Are You?"
msgstr "Quem é Você?"
-#: en_US/sudo-tutorial.xml:67(para)
+#: en_US/sudo-tutorial.xml:86(para)
+#, fuzzy
msgid ""
-"Before you get access to a Linux system, you must prove your identity. While "
-"the system administrator decides the security policy for the machine, "
-"usually one or more password challenges must be answered. After all, if you "
-"really are user <userinput>joesixpack</userinput>, then you should know the "
-"answer to a question that only <userinput>joesixpack</userinput> would know: "
-"what is the password?"
+"To gain access to a Linux system, you must prove your identity. While the "
+"system administrator decides the security policy for the machine, usually "
+"one or more password challenges must be answered. A credentialed user should "
+"know the answer to a question that only that user would know: What is the "
+"password?"
msgstr ""
"Antes de ter acesso a um sistema Linux, tem de provar a sua identidade. "
"Embora o administrador de sistema decida a polÃtica de segurança da máquina, "
@@ -144,730 +228,763 @@
"deverá saber a resposta a uma pergunta que só o <userinput>zepovinho</"
"userinput> deveria saber: qual é a senha?"
-#: en_US/sudo-tutorial.xml:75(para)
+#: en_US/sudo-tutorial.xml:100(para)
+#, fuzzy
msgid ""
"Actually, there is more to the authentication process than just a password "
-"challenge. The sysadmin can impose restrictions such as limiting the time of "
-"day when a given user may login, or requiring that a user make the login "
-"attempt from a specific location."
-msgstr "De facto, existe mais no processo de autenticação que apenas um desafio de senhas. O administrador de sistemas poderá impor restrições, como a limitação da hora do dia em que um dado utilizador se poderá autenticar ou obrigar um utilizador a fazer a tentativa de autenticação a partir de um local especÃfico."
+"challenge. The sysadmin can impose additional restrictions such as limiting "
+"the time of day when a given user may login, or limiting logins to specific "
+"locations."
+msgstr ""
+"De facto, existe mais no processo de autenticação que apenas um desafio de "
+"senhas. O administrador de sistemas poderá impor restrições, como a "
+"limitação da hora do dia em que um dado utilizador se poderá autenticar ou "
+"obrigar um utilizador a fazer a tentativa de autenticação a partir de um "
+"local especÃfico."
-#: en_US/sudo-tutorial.xml:72(para)
+#: en_US/sudo-tutorial.xml:93(para)
msgid ""
"This process of proving your identity to the system is known as "
"<firstterm>authentication</firstterm>. Many schemes are available to the "
-"system administrator, but once the system authenticates your login request, "
-"the kernel has enough information to determine what programs you can run or "
-"what files you can access<footnote><placeholder-1/></footnote>."
-msgstr "Este processo de prova da sua identidade no sistema é conhecido por <firstterm>autenticação</firstterm>. Estão disponÃveis muitos esquemas para o administrador do sistema, mas uma vez que o sistema autentique o seu pedido de autenticação, o 'kernel' fica com informações suficientes para determinar os programas que poderá executar ou os ficheiros a que poderá aceder <footnote><placeholder-1/></footnote>."
-
-#: en_US/sudo-tutorial.xml:81(para)
-msgid ""
-"After a successful authentication the system uses your uid and gid to "
-"control your access to system resources."
+"system administrator for performing authentication. Once the system "
+"authenticates your login request, the kernel has enough information to "
+"determine what programs you can run and what files you can access."
+"<footnote><placeholder-1/> sudo-tutorial.xml After a successfully "
+"authentication the system uses your UID and GID to control your access to "
+"system resources. ======= . After a successful authentication the system "
+"uses your uid and gid to control your access to system resources. >>"
+">>>>> 1.3 File Access Permissions Every system resource, "
+"whether an application program, directory, or file, has a unique filename. A "
+"filename (including the directory path) is a unique identifier for that "
+"system resource. The part of Linux that manages these named system resources "
+"is known as the file system. In addition to the file content itself, the "
+"file system keeps extra information about every file. This metadata includes "
+"the file's size, disk block locations, and modification and access "
+"timestamps. You can see most of this metadata using the ls(1) program: Using "
+"ls(1) to examine file permissions $ ls -l /bin/mail -rwxr-xr-x 1 root mail "
+"73588 Apr 4 07:03 /bin/mail Consider two pieces of metadata for a file, its "
+"ownership and its access permissions. When a user creates a file, the user "
+"credentials are attached to the file, giving that user ownership of that "
+"file The chown(1) program allows the ownership credentials to be changed. . "
+"In our example, /bin/mail is owned by user root and group mail. The created "
+"file also gets a set of file access permissions that describe who may access "
+"that file and what kind of access they can get. There are exactly three "
+"types of access: read, write, or execute. These are usually abbreviated as "
+"rwx. Permissions for a file which could be read, but neither written nor "
+"executed, would be written as r--. Remember, the notation is positional and "
+"order matters. Files actually have three sets of permissions. One set is for "
+"the file owner, one set is for members of the owner's group, and one set is "
+"for everyone else, in that order. May I Access This File, Please? Before a "
+"user accesses any file, including running an application program, the kernel "
+"must validate the attempt against the file system. It uses a simple but very "
+"powerful method to determine whether access should be granted or denied. "
+"This algorithm is shown below: Determining File Access if( u.uid == f.uid ) "
+"{ rwx = perms.owner; } else if( u.gid == f.gid ) { rwx = perms.group; } else "
+"{ rwx = perms.world; } if( !accessok( access_wanted, rwx ) ) { errno = "
+"EPERM; return( -1 ); } do_access(); Assuming the following definitions: u "
+"Represents the user credentials containing both the uid and gid. f "
+"Represents the file ownership credentials, as shown by the ls -l command. "
+"Contains both the uid and gid values identifying the owner of the file. "
+"perms The file access permissions for the file, including all three sets of "
+"permissions: owner, group and world. The key point here is that, although "
+"there are three sets of file access permissions associated with the file, "
+"exactly one set is used to arbitrate the file access. Emphatically, the sets "
+"are not tried in sequence until the access is granted or we run out of sets: "
+"you get one and only one try at accessing the file. If you are the owner of "
+"the file, the system uses the file owner permissions. If you are not the "
+"owner, but a member of the same group as the file, the system uses the group "
+"permissions. If you are neither of these, the system checks against the "
+"world permissions. </footnote>"
msgstr ""
-"Depois de uma autenticação bem-sucedida, o sistema usa o seu UID e GID para "
-"controlar o seu acesso aos recursos do sistema."
-
-#: en_US/sudo-tutorial.xml:86(title)
-msgid "File Access Permissions"
-msgstr "Permissões de Acesso aos Ficheiros"
-
-#: en_US/sudo-tutorial.xml:87(para)
-msgid ""
-"Every system resource, whether an application program, directory, or file, "
-"has a unique name: its <firstterm>filename</firstterm>. You can think of a "
-"filename has a unique identifier for that system resource. The part of Linux "
-"that manages these named system resources is known as the <firstterm>file "
-"system</firstterm>."
-msgstr ""
-"Todos os recursos do sistema, sejam um programa de uma aplicação, uma pasta "
-"ou um ficheiro, têm um nome único: o seu <firstterm>nome de ficheiro</"
-"firstterm>. Poderá pensar num nome de ficheiros como um identificador único "
-"para esse recurso do sistema. A parte do Linux que gere esses recursos do "
-"sistema com nome é conhecido como um <firstterm>sistema de ficheiros</"
-"firstterm>."
-
-#: en_US/sudo-tutorial.xml:92(para)
-msgid ""
-"In addition to the file content itself, the file system keeps extra "
-"information about every file: its size; disk block locations; and "
-"modification and access timestamps. You can see most of this \"meta-data\" "
-"using the <application>ls(1)</application> program:"
-msgstr "Para além do conteúdo do ficheiro em si, o sistema de ficheiros mantém alguma informação extra sobre todos os ficheiros: o seu tamanho; os blocos de dados em disco, as datas de acesso e modificação do ficheiro. Poderá ver a maior parte destes \"meta-dados\" com o programa <application>ls(1)</application>:"
-
-#: en_US/sudo-tutorial.xml:97(title)
-msgid "Using ls(1) to examine file permissions"
-msgstr "Usar o ls(1) para examinar as permissões de acesso"
-
-#: en_US/sudo-tutorial.xml:98(screen)
-#, no-wrap
-msgid ""
-"$ ls -l /bin/mail\n"
-"-rwxr-xr-x 1 root mail 73588 Apr 4 07:03 /bin/mail"
-msgstr ""
-"$ ls -l /bin/mail\n"
-"-rwxr-xr-x 1 root mail 73588 Abr 4 07:03 /bin/mail"
-
-#: en_US/sudo-tutorial.xml:101(para)
-msgid ""
-"We are most interested in two groups of information about the file: its "
-"ownership and its access permissions."
-msgstr ""
-"O interesse maior está em dois grupos de informação do ficheiro: o seu dono "
-"e as suas permissões de acesso."
-
-#: en_US/sudo-tutorial.xml:106(para)
-msgid ""
-"The <application>chown(1)</application> program allows the ownership "
-"credentials to be changed, but that is another HOWTO."
-msgstr "O programa <application>chown(1)</application> permite mudar as credenciais de pertença, mas isso é outro HOWTO."
-
-#: en_US/sudo-tutorial.xml:104(para)
-msgid ""
-"When a user creates a file, the user credentials are attached to the file, "
-"giving that user <emphasis>ownership</emphasis> of that "
-"file<footnote><placeholder-1/></footnote>. In our example, <filename>/bin/"
-"mail</filename> is owned by user <userinput>root</userinput> and group "
-"<userinput>mail</userinput>."
-msgstr "Quando um utilizador cria um ficheiro, as credenciais do utilizador ficam associadas ao ficheiro, tornando esse o utilizador o <emphasis>dono</emphasis> desse ficheiro<footnote><placeholder-1/></footnote>. No nosso exemplo, o <filename>/bin/mail</filename> pertence ao utilizador <userinput>root</userinput> e ao grupo <userinput>mail</userinput>."
-
-#: en_US/sudo-tutorial.xml:112(para)
-msgid ""
-"The created file also gets a set of file access permissions that describe "
-"who may access that file and what kind of access they can get. There are "
-"exactly three types of access: read, write, or execute ‐ usually "
-"abbreviated as <abbrev>rwx</abbrev>. Permissions for a file which could be "
-"read, but neither written nor executed, would be written as <abbrev>r--</"
-"abbrev>. Remember, the notation is positional and order matters."
-msgstr "O ficheiro criado também recebe um conjunto de permissões de acesso ao ficheiro que descrevem quem poderá aceder a mesmo, e qual o tipo de acesso que poderão ter. Existem exactamente três tipos de acesso: leitura, escrita e execução ‐ abreviados normalmente como <abbrev>rwx</abbrev>. As permissões de um ficheiro que possa ser lido, mas não possa ser gravado nem executado, seriam algo do género <abbrev>r--</abbrev>. Lembre-se, esta notação guia-se pela posição, e a ordem interessa."
-
-#: en_US/sudo-tutorial.xml:118(para)
-msgid ""
-"Files actually have three sets of permissions: one set for the file owner, "
-"one set for members of the owner's group; and one set for everyone else; "
-"again order matters, the owner permissions are first, followed by the group "
-"and then the world permissions. In the next section, we shall see how Linux "
-"puts all this together."
-msgstr ""
-"Os ficheiros têm de facto três conjuntos de permissões: uma para o dono do "
-"ficheiro, outra para os membros do grupo do dono; e outra para todos os "
-"outros; mais uma vez, a ordem interessa, sendo primeiro as permissões do "
-"dono, depois as do grupo e, finalmente, as dos restantes utilizadores. Na "
-"próxima secção, vejamos como é que o Linux coloca tudo isto em conjunto."
-
-#: en_US/sudo-tutorial.xml:124(title)
-msgid "May I Access This File, Please?"
-msgstr "Posso Aceder a Este Ficheiro, por Favor?"
-
-#: en_US/sudo-tutorial.xml:125(para)
-msgid ""
-"Before any file is accessed, and this includes running an application "
-"program, the file system must validate the attempt. There is a very simple, "
-"but very powerful, method used to determine whether access should be granted "
-"or denied. This algorithm is shown below:"
-msgstr ""
-"Antes de aceder a qualquer ficheiro, e isto inclui a execução do programa de "
-"uma aplicação, o sistema de ficheiros tem de validar a tentativa. Isto é um "
-"método muito simples, mas muito poderoso, de determinar se o acesso deverá "
-"ser cedido ou negado. Este algoritmo é apresentado abaixo:"
-
-#: en_US/sudo-tutorial.xml:131(title)
-msgid "Determining File Access"
-msgstr "Determinar o Acesso aos Ficheiros"
-
-#: en_US/sudo-tutorial.xml:132(programlisting)
-#, no-wrap
-msgid ""
-"if( u.uid == f.uid ) {\n"
-" rwx = perms.owner;\n"
-"} else if( u.gid == f.gid ) {\n"
-" rwx = perms.group;\n"
-"} else {\n"
-" rwx = perms.world;\n"
-"}\n"
-"if( !accessok( access_wanted, rwx ) ) {\n"
-" errno = EPERM;\n"
-" return( -1 );\n"
-"}\n"
-"do_access();"
-msgstr ""
-"if( u.uid == f.uid ) {\n"
-" rwx = perms.dono;\n"
-"} else if( u.gid == f.gid ) {\n"
-" rwx = perms.grupo;\n"
-"} else {\n"
-" rwx = perms.mundo;\n"
-"}\n"
-"if( !accessok( acesso_desejado, rwx ) ) {\n"
-" errno = EPERM;\n"
-" return( -1 );\n"
-"}\n"
-"fazer_acesso();"
-
-#: en_US/sudo-tutorial.xml:145(para)
-msgid "Assuming the following definitions:"
-msgstr "Assumindo as seguintes definições:"
-
-#: en_US/sudo-tutorial.xml:150(glossterm)
-msgid "u"
-msgstr "u"
-
-#: en_US/sudo-tutorial.xml:152(para)
-msgid ""
-"Represents the user credentials containing both the <abbrev>uid</abbrev> and "
-"<abbrev>gid</abbrev>."
-msgstr ""
-"Representa as credenciais do utilizador, que contêm tanto o <abbrev>UID</"
-"abbrev> como o <abbrev>GID</abbrev>."
-
-#: en_US/sudo-tutorial.xml:158(glossterm)
-msgid "f"
-msgstr "f"
-
-#: en_US/sudo-tutorial.xml:160(para)
-msgid ""
-"Represents the file ownership credentials, as shown by the <command>ls -l</"
-"command> command. Contains both the <abbrev>uid</abbrev> and <abbrev>gid</"
-"abbrev> values identifying the owner of the file."
-msgstr ""
-"Representa as credenciais de pertença do ficheiro, como aparece no comando "
-"<command>ls -l</command>. Contém tanto os valores do <abbrev>UID</abbrev> "
-"como do <abbrev>GID</abbrev>, identificando o dono do ficheiro."
-
-#: en_US/sudo-tutorial.xml:167(glossterm)
-msgid "perms"
-msgstr "perms"
-
-#: en_US/sudo-tutorial.xml:168(para)
-msgid ""
-"The file access permissions for the file, including all three sets of "
-"permissions: owner, group and world."
-msgstr ""
-"As permissões de acesso ao ficheiro, incluindo os três conjuntos de "
-"permissões: dono, grupo e mundo."
-
-#: en_US/sudo-tutorial.xml:173(para)
-msgid ""
-"The key point here is that, although there are three sets of file access "
-"permissions associated with the file, exactly <emphasis>one</emphasis> set "
-"is used to arbitrate the file access. Emphatically, the sets are "
-"<emphasis>not</emphasis> tried in sequence until the access is granted or we "
-"run out of sets: you get one and only one try at accessing the file."
-msgstr ""
-"O ponto-chave aqui é que, ainda que existam três conjunto de permissões de "
-"acesso ao ficheiro associados ao ficheiro, apenas exactamente <emphasis>um</"
-"emphasis> conjunto é usado para arbitrar o acesso ao ficheiro. Para "
-"enfatizar, os conjuntos <emphasis>não</emphasis> testados em sequência, até "
-"que o acesso seja acedido ou esgote os conjuntos: tem uma e só uma tentativa "
-"de aceder ao ficheiro."
-
-#: en_US/sudo-tutorial.xml:177(para)
-msgid ""
-"If you are the owner of the file, the system uses the file owner "
-"permissions. If you are not the owner, but a member of the same group as the "
-"file, the system uses the group permissions. If you are neither of these, "
-"the system checks against the world permissions."
-msgstr ""
-"Se for o dono do ficheiro, o sistema usa as permissões do dono do ficheiro. "
-"Se não for o dono, mas sim um membro do mesmo grupo do ficheiro, o sistema "
-"irá usar as permissões do grupo. Se não for nenhum deles, o sistema verifica "
-"as permissões para o mundo."
-
-#: en_US/sudo-tutorial.xml:186(title)
-msgid "What Not To Do"
-msgstr "O que Não Deve Fazer"
-
-#: en_US/sudo-tutorial.xml:188(para)
-msgid ""
-"As desirable as enforcing file access permissions are on a Linux system, "
-"there are valid reasons for needing to bypass the checking. Several users "
-"run the same program to generate project files that must be accessible to "
-"all; a printer queue is hung and the sysadmin has given a local user "
-"authority to restart the printer daemon; an ordinary user wants to mount an "
-"NFS hierarchy from a file server; a mail delivery program must be able to "
-"write into mail files writable only by the mail recipient; and finally, a "
-"local user is empowered to perform designated sysadmin functions but the "
-"real sysadmin does not want to grant blanket permission to alter everything "
-"on the system."
-msgstr ""
-"Apesar de ser desejada a aplicação das permissões de acesso aos ficheiros "
-"num sistema Linux, existem razões válidas para necessitar de dar a volta à "
-"verificação. Vários utilizadores executam o mesmo programa para gerar os "
-"ficheiros do projecto que deverão ser acessÃveis para todos; uma fila de "
-"impressão está bloqueada e ao administrador do sistema foi dada autorização "
-"para reiniciar o servidor da impressora; um utilizador normal precisa de "
-"montar uma hierarquia de NFS de um servidor de ficheiros; um programa de "
-"entrega de correio precisa de gravar nos ficheiros das caixas de correio, "
-"que só podem ser gravados pelo destinatário do e-mail; finalmente, um "
-"utilizador local tem permissões para poder efectuar algumas funções "
-"designadas de administração do sistema, mas o administrador verdadeiro não "
-"quer dar 'carta branca' para alterar tudo no sistema."
-
-#: en_US/sudo-tutorial.xml:197(para)
-msgid ""
-"Below we will look at common methods of working around the Linux file access "
-"permissions scheme and point out some short-comings of each technique. All "
-"these methods \"work\", in the sense that they function correctly but incur "
-"unnecessary security risks. In the next section, we show how "
-"<application>sudo(8)</application> controls most of these risks."
-msgstr ""
-"Em baixo, irá ver alguns métodos comuns de dar a volta ao esquema de "
-"permissões de acesso aos ficheiros do Linux e apontar algumas deficiências "
-"de cada uma das técnicas. Todos estes métodos "funcionam", na "
-"medida em que funcionam correctamente, mas incorrem em riscos de segurança "
-"desnecessários. Na secção seguinte, ver-se-á como o <application>sudo(8)</"
-"application> controla a maior parte destes riscos."
-
-#: en_US/sudo-tutorial.xml:204(title)
-msgid "Perhaps You Have Heard Of The su(1) Application?"
-msgstr "Talvez já Tenha Ouvido Falar da Aplicação su(1)?"
-
-#: en_US/sudo-tutorial.xml:205(para)
-msgid ""
-"One technique, used since <trademark>UNIX</trademark> systems began, is for "
-"the user to temporarily assume the privileges of the superuser account. The "
-"<application>su(1)</application> changes the identification for the current "
-"user by <emphasis>s</emphasis>ubstituting <emphasis>u</emphasis>ser "
-"credentials."
-msgstr ""
-"Uma técnica, usada desde que os sistemas <trademark>UNIX</trademark> tiveram "
-"inÃcio, é o utilizador assumir temporariamente os privilégios da conta de "
-"super-utilizador. O <application>su(1)</application> muda a identificação do "
-"utilizador actual, <emphasis>s</emphasis>ubstituindo as credenciais do "
-"<emphasis>u</emphasis>tilizador."
-
-#: en_US/sudo-tutorial.xml:211(title)
-msgid "Traditional Approach Using su(1)"
-msgstr "Aproximação Tradicional com o su(1)"
-
-#: en_US/sudo-tutorial.xml:212(screen)
-#, no-wrap
-msgid ""
-"$ id\n"
-"uid=500(reynolds) gid=500(reynolds) groups=500(reynolds)\n"
-"$ su -c id\n"
-"Password:\n"
-"uid=0(root) gid=0(root) groups=0(root),1(bin)..."
-msgstr ""
-"$ id\n"
-"uid=500(ze) gid=500(ze) groups=500(ze)\n"
-"$ su -c id\n"
-"Password:\n"
-"uid=0(root) gid=0(root) groups=0(root),1(bin)..."
-
-#: en_US/sudo-tutorial.xml:219(para)
-msgid "There are some problems with this approach:"
-msgstr "Existem alguns problemas com esta aproximação:"
-
-#: en_US/sudo-tutorial.xml:225(para)
-msgid "The superuser password is compromised."
-msgstr "A senha do super-utilizador fica comprometida."
-
-#: en_US/sudo-tutorial.xml:228(para)
-msgid ""
-"Once anyone other than the system administrator knows the superuser "
-"password, everyone will know it. He that wishes to keep a secret must keep "
-"it a secret that he has a secret to keep. Promises not to tell are not "
-"sufficient security."
-msgstr ""
-"A partir do momento em que alguém que não o administrador do sistema saiba a "
-"senha de administração, todos ficarão a sabê-la. Aquele que deseja manter um "
-"segredo, precisa de manter o segredo de que tem um segredo a manter. As "
-"promessas de não dizer a ninguém não são segurança suficiente."
-
-#: en_US/sudo-tutorial.xml:235(para)
-msgid "There is no audit trail."
-msgstr "Não existe um registo para auditoria."
-
-#: en_US/sudo-tutorial.xml:241(para)
-msgid "In security parlance, \"to trust\" is identical to \"be at risk from\"."
-msgstr "Em vocabulário de segurança, \"confiar\" é igual a \"estar em risco de\"."
-
-#: en_US/sudo-tutorial.xml:238(para)
-msgid ""
-"With a superuser shell, a user can do anything that the root account can do. "
-"We must trust<footnote><placeholder-1/></footnote>the user to access only "
-"the files and programs they claimed to need."
-msgstr "Com uma linha de comandos de super-utilizador, um utilizador poderá fazer tudo o que a conta do 'root' poderá fazer. Terá de confiar<footnote><placeholder-1/></footnote>que o utilizador só irá aceder aos ficheiros e programas que disseram ter."
-
-#: en_US/sudo-tutorial.xml:251(title)
-msgid "Please, No Setuid Shell Scripts"
-msgstr "Por Favor, Não Tenha Programas com Setuid"
-
-#: en_US/sudo-tutorial.xml:252(para)
-msgid ""
-"Another technology, used by the <application>su(1)</application> program, "
-"takes advantage of a neat feature."
-msgstr ""
-"Outra tecnologia, usada pelo programa <application>su(1)</application>, tira "
-"partido de uma funcionalidade gira."
-
-#: en_US/sudo-tutorial.xml:255(para)
-msgid ""
-"Normally, the files accessible to an application or shell depend on who is "
-"executing that program. Recall those <emphasis>credentials</emphasis> "
-"mentioned earlier? An application executes using the credentials of the user "
-"who runs the program."
-msgstr ""
-"Normalmente, os ficheiros acessÃveis por uma dada aplicação ou linha de "
-"comando dependem de quem executa esse programa. Lembra-se das "
-"<emphasis>credenciais</emphasis> mencionadas anteriormente? Uma aplicação "
-"executa-se com as credenciais do utilizador que executa o programa."
-
-#: en_US/sudo-tutorial.xml:260(para)
-msgid "Stop, wait, there's more!"
-msgstr "Espere, há mais!"
-
-#: en_US/sudo-tutorial.xml:263(para)
-msgid ""
-"Files have access permissions but since a program is stored in a file, the "
-"program has file access permissions, too."
-msgstr ""
-"Os ficheiros tem permissões de acesso, mas dado que um programa está "
-"guardado num ficheiro, o programa também tem permissões de acesso aos "
-"ficheiros."
-
-#: en_US/sudo-tutorial.xml:268(para)
-msgid "The commands:"
-msgstr "Os comandos:"
-
-#: en_US/sudo-tutorial.xml:273(para)
-msgid ""
-"would give whomever runs <filename>/bin/foo</filename> the same privileges "
-"that the superuser account would have while running the same application."
-msgstr "iria dar os mesmos privilégios, a quem executar o <filename>/bin/xpto</filename>, da conta do super-utilizador, se executasse a mesma aplicação."
-
-#: en_US/sudo-tutorial.xml:266(para)
-msgid ""
-"By setting a special flag, called the <firstterm>set user id bit</firstterm> "
-"or <function>setuid(2)</function>, we can cause the system to check "
-"\"credentials\" made from the program file access permissions, instead of "
-"using the credentials for the user running the "
-"application<footnote><placeholder-1/><screen width=\"60\"># chown root:root /"
-"bin/foo\n"
-"# chmod 06555 /bin/foo</screen><placeholder-2/></footnote>."
-msgstr ""
-"Ao definir uma opção especial, chamada de <firstterm>bit de definição do ID de utilizador</firstterm> ou <function>setuid(2)</function>, poderá fazer com que o sistema verifique as "credenciais" feitas com base nas permissões de acesso ao ficheiro, em vez de usar as credenciais do utilizador que executa a aplicação<footnote><screen width=\"60\"># chown root:root /bin/xpto\n"
-"# chmod 06555 /bin/xpto</screen><placeholder-2/></footnote>."
-
-#: en_US/sudo-tutorial.xml:278(para)
-msgid ""
-"This ability to use the credentials of an application, instead of those of "
-"the user, can be a great boon to multiuser applications such as databases or "
-"email delivery agents. The feature has its proper use on a Linux system."
-msgstr ""
-"Esta capacidade de usar as credenciais de uma aplicação, em vez das do "
-"utilizador, poderá ser uma grande ajuda para as aplicações multi-utilizador, "
-"como as bases de dados ou os agentes de entrega de e-mail. A funcionalidade "
-"tem o seu uso próprio num sistema Linux."
-
-#: en_US/sudo-tutorial.xml:282(para)
-msgid ""
-"As useful as it is, one must resist the temptation to make a shell program, "
-"such as <filename>/bin/bash</filename>, or a shell script, such as "
-"<filename>/usr/local/bin/run_as_root</filename>, be set user ID to root."
-msgstr ""
-"Dada a sua utilidade, uma pessoa deverá resistir à tentação de mudar um "
-"programa, como a <filename>/bin/bash</filename>, ou outro programa, como a "
-"<filename>/usr/local/bin/correr_como_root</filename>, para ser 'setuid' para "
-"'root'."
-
-#: en_US/sudo-tutorial.xml:285(para)
-msgid ""
-"If this were to be done, then <emphasis>any</emphasis> user running that "
-"script or application would be able to access any file that the root account "
-"could access."
-msgstr ""
-"Se isso fosse feito, então <emphasis>qualquer</emphasis> utilizador que "
-"corresse esse programa ou aplicação seria capaz de aceder a qualquer "
-"ficheiro que a conta de 'root' conseguisse aceder."
-
-#: en_US/sudo-tutorial.xml:288(para)
-msgid ""
-"Again, the objections to this method a similar to those we mentioned for the "
-"<application>su(1)</application> program: no control, and no traceability."
-msgstr ""
-"Mais uma vez, as objecções a este método são semelhantes às mencionadas para "
-"o programa <application>su(1)</application>: sem controlo, e sem qualquer "
-"registo."
-
-#: en_US/sudo-tutorial.xml:296(title)
-msgid "A Safer Alternative: sudo(8)"
-msgstr "Uma Alternativa Mais Segura: sudo(8)"
-
-#: en_US/sudo-tutorial.xml:297(para)
-msgid ""
-"The <application>sudo(8)</application> program solves the dilemma of how to "
-"allow ordinary users access to certain privileged system resources yet still "
-"keep the superuser password secret."
-msgstr ""
-"O programa <application>sudo(8)</application> resolve o dilema de como "
-"permitir aos utilizadores normais o acesso a certos recursos privilegiados "
-"do sistema, mantendo à mesma a senha do super-utilizador em segredo."
-
-#: en_US/sudo-tutorial.xml:300(para)
-msgid ""
-"Before granting privileges to a user, the <application>sudo(8)</application> "
-"program checks the configuration file <filename>/etc/sudoers</filename> and:"
-msgstr ""
-"Antes de aceder os privilégios a um utilizador, o programa <application>sudo"
-"(8)</application> verifica o ficheiro de configuração <filename>/etc/"
-"sudoers</filename> e:"
-
-#: en_US/sudo-tutorial.xml:305(para)
-msgid "Grants privileges to the user without requiring any password at all."
-msgstr "Cede os privilégios ao utilizador sem necessitar de qualquer senha."
-
-#: en_US/sudo-tutorial.xml:310(para)
-msgid ""
-"Grants privileges to the user if, and only if, the user supplies the correct "
-"password to prove their identity. Note that this is the password for the "
-"user account, <emphasis>not</emphasis> the superuser password."
-msgstr ""
-"Cede os privilégios ao utilizador se, e só se, o utilizador indicar a sua "
-"senha correcta, para provar a sua identidade. Lembre-se que esta é a senha "
-"da conta do utilizador, <emphasis>não</emphasis> a senha do super-utilizador."
-
-#: en_US/sudo-tutorial.xml:316(para)
-msgid ""
-"Deny the access and notify the system administrator of the failed attempt "
-"via an email sent to the root account."
-msgstr ""
-"Negar o acesso e notificar o administrador do sistema da tentativa falhada "
-"com um e-mail enviado para a conta do 'root'."
-
-#: en_US/sudo-tutorial.xml:320(para)
-msgid ""
-"Log the command, its arguments, and timestamp into the <filename>/var/log/"
-"secure</filename> file."
-msgstr ""
-"Regista o comando, os seus argumentos e a hora no ficheiro <filename>/var/"
-"log/secure</filename>."
-
-#: en_US/sudo-tutorial.xml:324(para)
-msgid ""
-"<application>Sudo(8)</application> keeps a log of all activity in the "
-"<filename>/var/log/secure</filename> file. Thus, there is an audit trail "
-"recording everything done in the name of the system administrator."
-msgstr ""
-"O <application>sudo(8)</application> mantém um registo de toda a actividade "
-"no ficheiro <filename>/var/log/secure</filename>. Deste modo, existe um "
-"registo para auditoria que guarda tudo o que é feito em nome do "
-"administrador do sistema."
-
-#: en_US/sudo-tutorial.xml:330(title)
-msgid "Controlling Access To sudo(8)"
-msgstr "controlar o Acesso ao sudo(8)"
-
-#: en_US/sudo-tutorial.xml:331(para)
-msgid ""
-"The <filename>/etc/sudoers</filename> file configures the programs that "
-"users can access using <application>sudo(8)</application>, along with "
-"whether or not a password will be needed."
-msgstr ""
-"O ficheiro <filename>/etc/sudoers</filename> configura os programas que os "
-"utilizadores poderão aceder com o <application>sudo(8)</application>, para "
-"além do facto de ser necessária uma senha ou não."
-
-#: en_US/sudo-tutorial.xml:334(para)
-msgid ""
-"The system administrator adds users to this file using the <filename>/usr/"
-"sbin/visudo</filename> command. Each non-comment line in the file has two "
-"parts:"
-msgstr ""
-"O administrador do sistema adiciona os utilizadores a este ficheiro com o "
-"comando <filename>/usr/sbin/visudo</filename>. Cada linha, sem ser os "
-"comentários, tem duas partes:"
-
-#: en_US/sudo-tutorial.xml:340(para)
-msgid "A username (\"reynolds\"), or a group name (\"%wheel\")."
-msgstr "Um utilizador (\"ze\"), ou um nome de grupo (\"%utilizadores\")."
-
-#: en_US/sudo-tutorial.xml:343(para)
-msgid ""
-"A list of machine names where a program may be run, or the keyword "
-"<literal>ALL</literal>. Following an equal sign (<literal>=</literal>), a "
-"list of user identities the command may be run as, enclosed in round "
-"brackets (parenthesis); the wildcard <literal>ALL</literal> may also appear. "
-"Finally, a list of applications which may be run as the named users; the "
-"keyword <literal>ALL</literal> is a wildcard."
-msgstr ""
-"Uma lista com os nomes de máquinas onde um programa poderá ser executado, ou "
-"a palavra-chave <literal>ALL</literal>. A seguir a um sinal de igual "
-"(<literal>=</literal>), existe uma lista de utilizadores que identifica quem "
-"pode executar o comando, entre parêntesis; a palavra-chave <literal>ALL</"
-"literal> também poderá aparecer. Finalmente, uma lista de aplicações que "
-"poderão ser executadas com os utilizadores indicados; a palavra-chave "
-"<literal>ALL</literal> é uma sequência especial."
-
-#: en_US/sudo-tutorial.xml:350(para)
-msgid "The following examples should help make this clear:"
-msgstr "Os exemplos seguintes deverão clarificar isto:"
-
-#: en_US/sudo-tutorial.xml:355(title)
-msgid "/etc/sudoers Examples"
-msgstr "Exemplos do /etc/sudoers"
-
-#: en_US/sudo-tutorial.xml:359(computeroutput)
-#, no-wrap
-msgid "reynolds ALL=(ALL) ALL"
-msgstr "ze ALL=(ALL) ALL"
-
-#: en_US/sudo-tutorial.xml:362(para)
-msgid ""
-"User reynolds can execute any command as any user, but must know the "
-"password to the reynolds account."
-msgstr ""
-"O utilizador 'ze' poderá executar qualquer comando, como qualquer "
-"utilizador, mas precisa de saber a senha da conta 'ze'."
-
-#: en_US/sudo-tutorial.xml:369(computeroutput)
-#, no-wrap
-msgid "reynolds ALL=(root) shutdown"
-msgstr "ze ALL=(root) shutdown"
-
-#: en_US/sudo-tutorial.xml:372(para)
-msgid ""
-"User reynolds can execute only command <application>shutdown</application>, "
-"but must know the password to the reynolds account."
-msgstr ""
-"O utilizador 'ze' poderá executar apenas o comando <application>shutdown</"
-"application>, mas precisa de saber a senha da conta 'ze'."
-
-#: en_US/sudo-tutorial.xml:379(computeroutput)
-#, no-wrap
-msgid "reynolds ALL=(root) NOPASSWD: /usr/bin/id"
-msgstr "ze ALL=(root) NOPASSWD: /usr/bin/id"
-
-#: en_US/sudo-tutorial.xml:382(para)
-msgid ""
-"User reynolds can execute only the application <filename>/usr/bin/id</"
-"filename>; no password will be needed."
-msgstr ""
-"O utilizador 'ze' poderá executar apenas a aplicação <filename>/usr/bin/id</"
-"filename>; não será necessária qualquer senha."
-
-#: en_US/sudo-tutorial.xml:393(title)
-msgid "Using sudo(8)"
-msgstr "Usar o sudo(8)"
-
-#: en_US/sudo-tutorial.xml:394(para)
-msgid ""
-"Once the system administrator has entered the necessary setup into the "
-"<filename>/etc/sudoers</filename> file, users can safely access privileged "
-"system resources and activities like this:"
-msgstr ""
-"Logo que o administrador do sistema tenha introduzido a configuração "
-"necessária no ficheiro <filename>/etc/sudoers</filename>, os utilizadores "
-"poderão aceder em segurança aos recursos do sistema privilegiados e a "
-"actividades da seguinte forma:"
-
-#: en_US/sudo-tutorial.xml:397(screen)
-#, no-wrap
-msgid ""
-"$ sudo reboot\n"
-"Password:"
-msgstr ""
-"$ sudo reboot\n"
-"Password:"
-
-#: en_US/sudo-tutorial.xml:399(para)
-msgid ""
-"No awkward quoting on the command line, just prefix the command you want "
-"with the word <userinput>sudo</userinput>. If you want to run the command as "
-"a user other than <userinput>root</userinput>, just add the <option>-u </"
-"option><replaceable>username</replaceable> switch:"
-msgstr ""
-"Não precisa de colocar a linha de comandos entre aspas, basta anteceder o "
-"comando que deseja com a palavra <userinput>sudo</userinput>. Se quiser "
-"executar o comando com um utilizador que não o <userinput>root</userinput>, "
-"basta adicionar a opção <option>-u </option><replaceable>utilizador</"
-"replaceable>:"
-
-#: en_US/sudo-tutorial.xml:403(screen)
-#, no-wrap
-msgid "$ sudo -u reynolds id"
-msgstr "$ sudo -u ze id"
-
-#: en_US/sudo-tutorial.xml:404(para)
-msgid ""
-"There will be a log entry written to the <filename>/var/log/secure</"
-"filename> file to show who did the deed."
-msgstr ""
-"Existirá um elemento gravado no registo do ficheiro <filename>/var/log/"
-"secure</filename>, a mostrar quem fez tal acção."
-
-#: en_US/sudo-tutorial.xml:407(para)
-msgid ""
-"Of course, the sysadmin may have configured <application>sudo(8)</"
-"application> not to request a password. In this case, the command is "
-"immediately executed although the audit trail entry will still be written."
-msgstr ""
-"Obviamente, o administrador do sistema poderá ter configurado o "
-"<application>sudo(8)</application> para não pedir uma senha. Nesse caso, o "
-"comando é executado imediatamente, ainda que o item de registo para "
-"auditoria será gravado à mesma."
-
-#: en_US/sudo-tutorial.xml:415(title)
-msgid "And, In Conclusion"
-msgstr "E, como Conclusão"
-
-#: en_US/sudo-tutorial.xml:416(para)
-msgid ""
-"The <application>sudo(8)</application> program provides a safe, controlled "
-"facility that allows a user to run a defined set of programs using the "
-"credentials of a defined set of users. The superuser password need never be "
-"publicised or compromised, since <application>sudo(8)</application> is "
-"controlled from a configuration file crafted by the system administrator."
-msgstr ""
-"O programa <application>sudo(8)</application> oferece uma funcionalidade "
-"segura e controlada que permite a um utilizador executar um conjunto "
-"definido de programas com as credenciais de um conjunto também bem definido "
-"de utilizadores. A senha do super-utilizador nunca poderá ser publicada ou "
-"comprometida, dado que o <application>sudo(8)</application> é controlado por "
-"um ficheiro de configuração criado pelo administrador do sistema."
-
-#: en_US/sudo-tutorial.xml:420(para)
-msgid ""
-"All commands run by <application>sudo(8)</application> are logged to the "
-"<filename>/var/log/secure</filename> file, while access violations are "
-"reported via email. Traceability results."
-msgstr ""
-"Todos os comandos executados pelo <application>sudo(8)</application> são "
-"registados no ficheiro <filename>/var/log/secure</filename>, enquanto as "
-"violações de acesso são comunicadas por e-mail. O acompanhamento resulta."
-
-#: en_US/sudo-tutorial.xml:424(para)
-msgid ""
-"From a user perspective, <application>sudo(8)</application> is easy to use: "
-"simply prefix the desired command line with the word <wordasword>sudo</"
-"wordasword>, press return, and possibly enter a password (but <emphasis>not</"
-"emphasis> the superuser password)."
-msgstr ""
-"Da perspectiva de um utilizador, o <application>sudo(8)</application> é "
-"simples de usar: basta anteceder o comando desejado com a palavra "
-"<wordasword>sudo</wordasword>, carregar em Return e, possivelmente, "
-"introduzir uma senha (mas <emphasis>não</emphasis> a senha do super-"
-"utilizador)."
-
-#: en_US/sudo-tutorial.xml:427(para)
-msgid "End Of Document"
-msgstr "Fim do Documento"
#. Put one translator per line, in the form of NAME <EMAIL>, YEAR1, YEAR2.
#: en_US/sudo-tutorial.xml:0(None)
msgid "translator-credits"
msgstr "José Nuno Pires <jncp at netcabo.pt>, 2006."
+#~ msgid ""
+#~ "To better understand the benefit that <application>sudo(8)</application> "
+#~ "brings, let us review how Linux provides access security to the system "
+#~ "resources. If you like, skip this section but come back if you need."
+#~ msgstr ""
+#~ "Para compreender melhor o benefÃcio que o <application>sudo(8)</"
+#~ "application> traz, façamos uma revisão da forma como o Linux oferece a "
+#~ "segurança de acesso aos recursos do sistema. Se preferir, salte esta "
+#~ "secção, mas volte se necessitar."
+
+#~ msgid ""
+#~ "Linux is a multiuser system. There is more to this than simply having a "
+#~ "<application>login(1)</application> program: every time a system resource "
+#~ "is accessed, care must be taken to ensure that the user attempting the "
+#~ "access is permitted to do so."
+#~ msgstr ""
+#~ "O Linux é um sistema multi-utilizador. Isto é muito mais do que ter "
+#~ "simplesmente um programa <application>login(1)</application>: de cada vez "
+#~ "que acede a um recurso do sistema, deverá ter cuidado para garantir que o "
+#~ "utilizador que tenta o acesso tem permissões para tal."
+
+#~ msgid ""
+#~ "This process of proving your identity to the system is known as "
+#~ "<firstterm>authentication</firstterm>. Many schemes are available to the "
+#~ "system administrator, but once the system authenticates your login "
+#~ "request, the kernel has enough information to determine what programs you "
+#~ "can run or what files you can access<footnote><placeholder-1/></footnote>."
+#~ msgstr ""
+#~ "Este processo de prova da sua identidade no sistema é conhecido por "
+#~ "<firstterm>autenticação</firstterm>. Estão disponÃveis muitos esquemas "
+#~ "para o administrador do sistema, mas uma vez que o sistema autentique o "
+#~ "seu pedido de autenticação, o 'kernel' fica com informações suficientes "
+#~ "para determinar os programas que poderá executar ou os ficheiros a que "
+#~ "poderá aceder <footnote><placeholder-1/></footnote>."
+
+#~ msgid ""
+#~ "After a successful authentication the system uses your uid and gid to "
+#~ "control your access to system resources."
+#~ msgstr ""
+#~ "Depois de uma autenticação bem-sucedida, o sistema usa o seu UID e GID "
+#~ "para controlar o seu acesso aos recursos do sistema."
+
+#~ msgid "File Access Permissions"
+#~ msgstr "Permissões de Acesso aos Ficheiros"
+
+#~ msgid ""
+#~ "Every system resource, whether an application program, directory, or "
+#~ "file, has a unique name: its <firstterm>filename</firstterm>. You can "
+#~ "think of a filename has a unique identifier for that system resource. The "
+#~ "part of Linux that manages these named system resources is known as the "
+#~ "<firstterm>file system</firstterm>."
+#~ msgstr ""
+#~ "Todos os recursos do sistema, sejam um programa de uma aplicação, uma "
+#~ "pasta ou um ficheiro, têm um nome único: o seu <firstterm>nome de "
+#~ "ficheiro</firstterm>. Poderá pensar num nome de ficheiros como um "
+#~ "identificador único para esse recurso do sistema. A parte do Linux que "
+#~ "gere esses recursos do sistema com nome é conhecido como um "
+#~ "<firstterm>sistema de ficheiros</firstterm>."
+
+#~ msgid ""
+#~ "In addition to the file content itself, the file system keeps extra "
+#~ "information about every file: its size; disk block locations; and "
+#~ "modification and access timestamps. You can see most of this \"meta-data"
+#~ "\" using the <application>ls(1)</application> program:"
+#~ msgstr ""
+#~ "Para além do conteúdo do ficheiro em si, o sistema de ficheiros mantém "
+#~ "alguma informação extra sobre todos os ficheiros: o seu tamanho; os "
+#~ "blocos de dados em disco, as datas de acesso e modificação do ficheiro. "
+#~ "Poderá ver a maior parte destes \"meta-dados\" com o programa "
+#~ "<application>ls(1)</application>:"
+
+#~ msgid "Using ls(1) to examine file permissions"
+#~ msgstr "Usar o ls(1) para examinar as permissões de acesso"
+
+#~ msgid ""
+#~ "$ ls -l /bin/mail\n"
+#~ "-rwxr-xr-x 1 root mail 73588 Apr 4 07:03 /bin/mail"
+#~ msgstr ""
+#~ "$ ls -l /bin/mail\n"
+#~ "-rwxr-xr-x 1 root mail 73588 Abr 4 07:03 /bin/mail"
+
+#~ msgid ""
+#~ "We are most interested in two groups of information about the file: its "
+#~ "ownership and its access permissions."
+#~ msgstr ""
+#~ "O interesse maior está em dois grupos de informação do ficheiro: o seu "
+#~ "dono e as suas permissões de acesso."
+
+#~ msgid ""
+#~ "The <application>chown(1)</application> program allows the ownership "
+#~ "credentials to be changed, but that is another HOWTO."
+#~ msgstr ""
+#~ "O programa <application>chown(1)</application> permite mudar as "
+#~ "credenciais de pertença, mas isso é outro HOWTO."
+
+#~ msgid ""
+#~ "When a user creates a file, the user credentials are attached to the "
+#~ "file, giving that user <emphasis>ownership</emphasis> of that "
+#~ "file<footnote><placeholder-1/></footnote>. In our example, <filename>/bin/"
+#~ "mail</filename> is owned by user <userinput>root</userinput> and group "
+#~ "<userinput>mail</userinput>."
+#~ msgstr ""
+#~ "Quando um utilizador cria um ficheiro, as credenciais do utilizador ficam "
+#~ "associadas ao ficheiro, tornando esse o utilizador o <emphasis>dono</"
+#~ "emphasis> desse ficheiro<footnote><placeholder-1/></footnote>. No nosso "
+#~ "exemplo, o <filename>/bin/mail</filename> pertence ao utilizador "
+#~ "<userinput>root</userinput> e ao grupo <userinput>mail</userinput>."
+
+#~ msgid ""
+#~ "The created file also gets a set of file access permissions that describe "
+#~ "who may access that file and what kind of access they can get. There are "
+#~ "exactly three types of access: read, write, or execute ‐ usually "
+#~ "abbreviated as <abbrev>rwx</abbrev>. Permissions for a file which could "
+#~ "be read, but neither written nor executed, would be written as <abbrev>r--"
+#~ "</abbrev>. Remember, the notation is positional and order matters."
+#~ msgstr ""
+#~ "O ficheiro criado também recebe um conjunto de permissões de acesso ao "
+#~ "ficheiro que descrevem quem poderá aceder a mesmo, e qual o tipo de "
+#~ "acesso que poderão ter. Existem exactamente três tipos de acesso: "
+#~ "leitura, escrita e execução ‐ abreviados normalmente como "
+#~ "<abbrev>rwx</abbrev>. As permissões de um ficheiro que possa ser lido, "
+#~ "mas não possa ser gravado nem executado, seriam algo do género <abbrev>r--"
+#~ "</abbrev>. Lembre-se, esta notação guia-se pela posição, e a ordem "
+#~ "interessa."
+
+#~ msgid ""
+#~ "Files actually have three sets of permissions: one set for the file "
+#~ "owner, one set for members of the owner's group; and one set for everyone "
+#~ "else; again order matters, the owner permissions are first, followed by "
+#~ "the group and then the world permissions. In the next section, we shall "
+#~ "see how Linux puts all this together."
+#~ msgstr ""
+#~ "Os ficheiros têm de facto três conjuntos de permissões: uma para o dono "
+#~ "do ficheiro, outra para os membros do grupo do dono; e outra para todos "
+#~ "os outros; mais uma vez, a ordem interessa, sendo primeiro as permissões "
+#~ "do dono, depois as do grupo e, finalmente, as dos restantes utilizadores. "
+#~ "Na próxima secção, vejamos como é que o Linux coloca tudo isto em "
+#~ "conjunto."
+
+#~ msgid "May I Access This File, Please?"
+#~ msgstr "Posso Aceder a Este Ficheiro, por Favor?"
+
+#~ msgid ""
+#~ "Before any file is accessed, and this includes running an application "
+#~ "program, the file system must validate the attempt. There is a very "
+#~ "simple, but very powerful, method used to determine whether access should "
+#~ "be granted or denied. This algorithm is shown below:"
+#~ msgstr ""
+#~ "Antes de aceder a qualquer ficheiro, e isto inclui a execução do programa "
+#~ "de uma aplicação, o sistema de ficheiros tem de validar a tentativa. Isto "
+#~ "é um método muito simples, mas muito poderoso, de determinar se o acesso "
+#~ "deverá ser cedido ou negado. Este algoritmo é apresentado abaixo:"
+
+#~ msgid "Determining File Access"
+#~ msgstr "Determinar o Acesso aos Ficheiros"
+
+#~ msgid ""
+#~ "if( u.uid == f.uid ) {\n"
+#~ " rwx = perms.owner;\n"
+#~ "} else if( u.gid == f.gid ) {\n"
+#~ " rwx = perms.group;\n"
+#~ "} else {\n"
+#~ " rwx = perms.world;\n"
+#~ "}\n"
+#~ "if( !accessok( access_wanted, rwx ) ) {\n"
+#~ " errno = EPERM;\n"
+#~ " return( -1 );\n"
+#~ "}\n"
+#~ "do_access();"
+#~ msgstr ""
+#~ "if( u.uid == f.uid ) {\n"
+#~ " rwx = perms.dono;\n"
+#~ "} else if( u.gid == f.gid ) {\n"
+#~ " rwx = perms.grupo;\n"
+#~ "} else {\n"
+#~ " rwx = perms.mundo;\n"
+#~ "}\n"
+#~ "if( !accessok( acesso_desejado, rwx ) ) {\n"
+#~ " errno = EPERM;\n"
+#~ " return( -1 );\n"
+#~ "}\n"
+#~ "fazer_acesso();"
+
+#~ msgid "Assuming the following definitions:"
+#~ msgstr "Assumindo as seguintes definições:"
+
+#~ msgid "u"
+#~ msgstr "u"
+
+#~ msgid ""
+#~ "Represents the user credentials containing both the <abbrev>uid</abbrev> "
+#~ "and <abbrev>gid</abbrev>."
+#~ msgstr ""
+#~ "Representa as credenciais do utilizador, que contêm tanto o <abbrev>UID</"
+#~ "abbrev> como o <abbrev>GID</abbrev>."
+
+#~ msgid "f"
+#~ msgstr "f"
+
+#~ msgid ""
+#~ "Represents the file ownership credentials, as shown by the <command>ls -"
+#~ "l</command> command. Contains both the <abbrev>uid</abbrev> and "
+#~ "<abbrev>gid</abbrev> values identifying the owner of the file."
+#~ msgstr ""
+#~ "Representa as credenciais de pertença do ficheiro, como aparece no "
+#~ "comando <command>ls -l</command>. Contém tanto os valores do <abbrev>UID</"
+#~ "abbrev> como do <abbrev>GID</abbrev>, identificando o dono do ficheiro."
+
+#~ msgid "perms"
+#~ msgstr "perms"
+
+#~ msgid ""
+#~ "The file access permissions for the file, including all three sets of "
+#~ "permissions: owner, group and world."
+#~ msgstr ""
+#~ "As permissões de acesso ao ficheiro, incluindo os três conjuntos de "
+#~ "permissões: dono, grupo e mundo."
+
+#~ msgid ""
+#~ "The key point here is that, although there are three sets of file access "
+#~ "permissions associated with the file, exactly <emphasis>one</emphasis> "
+#~ "set is used to arbitrate the file access. Emphatically, the sets are "
+#~ "<emphasis>not</emphasis> tried in sequence until the access is granted or "
+#~ "we run out of sets: you get one and only one try at accessing the file."
+#~ msgstr ""
+#~ "O ponto-chave aqui é que, ainda que existam três conjunto de permissões "
+#~ "de acesso ao ficheiro associados ao ficheiro, apenas exactamente "
+#~ "<emphasis>um</emphasis> conjunto é usado para arbitrar o acesso ao "
+#~ "ficheiro. Para enfatizar, os conjuntos <emphasis>não</emphasis> testados "
+#~ "em sequência, até que o acesso seja acedido ou esgote os conjuntos: tem "
+#~ "uma e só uma tentativa de aceder ao ficheiro."
+
+#~ msgid ""
+#~ "If you are the owner of the file, the system uses the file owner "
+#~ "permissions. If you are not the owner, but a member of the same group as "
+#~ "the file, the system uses the group permissions. If you are neither of "
+#~ "these, the system checks against the world permissions."
+#~ msgstr ""
+#~ "Se for o dono do ficheiro, o sistema usa as permissões do dono do "
+#~ "ficheiro. Se não for o dono, mas sim um membro do mesmo grupo do "
+#~ "ficheiro, o sistema irá usar as permissões do grupo. Se não for nenhum "
+#~ "deles, o sistema verifica as permissões para o mundo."
+
+#~ msgid "What Not To Do"
+#~ msgstr "O que Não Deve Fazer"
+
+#~ msgid ""
+#~ "As desirable as enforcing file access permissions are on a Linux system, "
+#~ "there are valid reasons for needing to bypass the checking. Several users "
+#~ "run the same program to generate project files that must be accessible to "
+#~ "all; a printer queue is hung and the sysadmin has given a local user "
+#~ "authority to restart the printer daemon; an ordinary user wants to mount "
+#~ "an NFS hierarchy from a file server; a mail delivery program must be able "
+#~ "to write into mail files writable only by the mail recipient; and "
+#~ "finally, a local user is empowered to perform designated sysadmin "
+#~ "functions but the real sysadmin does not want to grant blanket permission "
+#~ "to alter everything on the system."
+#~ msgstr ""
+#~ "Apesar de ser desejada a aplicação das permissões de acesso aos ficheiros "
+#~ "num sistema Linux, existem razões válidas para necessitar de dar a volta "
+#~ "à verificação. Vários utilizadores executam o mesmo programa para gerar "
+#~ "os ficheiros do projecto que deverão ser acessÃveis para todos; uma fila "
+#~ "de impressão está bloqueada e ao administrador do sistema foi dada "
+#~ "autorização para reiniciar o servidor da impressora; um utilizador normal "
+#~ "precisa de montar uma hierarquia de NFS de um servidor de ficheiros; um "
+#~ "programa de entrega de correio precisa de gravar nos ficheiros das caixas "
+#~ "de correio, que só podem ser gravados pelo destinatário do e-mail; "
+#~ "finalmente, um utilizador local tem permissões para poder efectuar "
+#~ "algumas funções designadas de administração do sistema, mas o "
+#~ "administrador verdadeiro não quer dar 'carta branca' para alterar tudo no "
+#~ "sistema."
+
+#~ msgid ""
+#~ "Below we will look at common methods of working around the Linux file "
+#~ "access permissions scheme and point out some short-comings of each "
+#~ "technique. All these methods \"work\", in the sense that they function "
+#~ "correctly but incur unnecessary security risks. In the next section, we "
+#~ "show how <application>sudo(8)</application> controls most of these risks."
+#~ msgstr ""
+#~ "Em baixo, irá ver alguns métodos comuns de dar a volta ao esquema de "
+#~ "permissões de acesso aos ficheiros do Linux e apontar algumas "
+#~ "deficiências de cada uma das técnicas. Todos estes métodos ""
+#~ "funcionam", na medida em que funcionam correctamente, mas incorrem "
+#~ "em riscos de segurança desnecessários. Na secção seguinte, ver-se-á como "
+#~ "o <application>sudo(8)</application> controla a maior parte destes riscos."
+
+#~ msgid "Perhaps You Have Heard Of The su(1) Application?"
+#~ msgstr "Talvez já Tenha Ouvido Falar da Aplicação su(1)?"
+
+#~ msgid ""
+#~ "One technique, used since <trademark>UNIX</trademark> systems began, is "
+#~ "for the user to temporarily assume the privileges of the superuser "
+#~ "account. The <application>su(1)</application> changes the identification "
+#~ "for the current user by <emphasis>s</emphasis>ubstituting <emphasis>u</"
+#~ "emphasis>ser credentials."
+#~ msgstr ""
+#~ "Uma técnica, usada desde que os sistemas <trademark>UNIX</trademark> "
+#~ "tiveram inÃcio, é o utilizador assumir temporariamente os privilégios da "
+#~ "conta de super-utilizador. O <application>su(1)</application> muda a "
+#~ "identificação do utilizador actual, <emphasis>s</emphasis>ubstituindo as "
+#~ "credenciais do <emphasis>u</emphasis>tilizador."
+
+#~ msgid "Traditional Approach Using su(1)"
+#~ msgstr "Aproximação Tradicional com o su(1)"
+
+#~ msgid ""
+#~ "$ id\n"
+#~ "uid=500(reynolds) gid=500(reynolds) groups=500(reynolds)\n"
+#~ "$ su -c id\n"
+#~ "Password:\n"
+#~ "uid=0(root) gid=0(root) groups=0(root),1(bin)..."
+#~ msgstr ""
+#~ "$ id\n"
+#~ "uid=500(ze) gid=500(ze) groups=500(ze)\n"
+#~ "$ su -c id\n"
+#~ "Password:\n"
+#~ "uid=0(root) gid=0(root) groups=0(root),1(bin)..."
+
+#~ msgid "There are some problems with this approach:"
+#~ msgstr "Existem alguns problemas com esta aproximação:"
+
+#~ msgid "The superuser password is compromised."
+#~ msgstr "A senha do super-utilizador fica comprometida."
+
+#~ msgid ""
+#~ "Once anyone other than the system administrator knows the superuser "
+#~ "password, everyone will know it. He that wishes to keep a secret must "
+#~ "keep it a secret that he has a secret to keep. Promises not to tell are "
+#~ "not sufficient security."
+#~ msgstr ""
+#~ "A partir do momento em que alguém que não o administrador do sistema "
+#~ "saiba a senha de administração, todos ficarão a sabê-la. Aquele que "
+#~ "deseja manter um segredo, precisa de manter o segredo de que tem um "
+#~ "segredo a manter. As promessas de não dizer a ninguém não são segurança "
+#~ "suficiente."
+
+#~ msgid "There is no audit trail."
+#~ msgstr "Não existe um registo para auditoria."
+
+#~ msgid ""
+#~ "In security parlance, \"to trust\" is identical to \"be at risk from\"."
+#~ msgstr ""
+#~ "Em vocabulário de segurança, \"confiar\" é igual a \"estar em risco de\"."
+
+#~ msgid ""
+#~ "With a superuser shell, a user can do anything that the root account can "
+#~ "do. We must trust<footnote><placeholder-1/></footnote>the user to access "
+#~ "only the files and programs they claimed to need."
+#~ msgstr ""
+#~ "Com uma linha de comandos de super-utilizador, um utilizador poderá fazer "
+#~ "tudo o que a conta do 'root' poderá fazer. Terá de "
+#~ "confiar<footnote><placeholder-1/></footnote>que o utilizador só irá "
+#~ "aceder aos ficheiros e programas que disseram ter."
+
+#~ msgid "Please, No Setuid Shell Scripts"
+#~ msgstr "Por Favor, Não Tenha Programas com Setuid"
+
+#~ msgid ""
+#~ "Another technology, used by the <application>su(1)</application> program, "
+#~ "takes advantage of a neat feature."
+#~ msgstr ""
+#~ "Outra tecnologia, usada pelo programa <application>su(1)</application>, "
+#~ "tira partido de uma funcionalidade gira."
+
+#~ msgid ""
+#~ "Normally, the files accessible to an application or shell depend on who "
+#~ "is executing that program. Recall those <emphasis>credentials</emphasis> "
+#~ "mentioned earlier? An application executes using the credentials of the "
+#~ "user who runs the program."
+#~ msgstr ""
+#~ "Normalmente, os ficheiros acessÃveis por uma dada aplicação ou linha de "
+#~ "comando dependem de quem executa esse programa. Lembra-se das "
+#~ "<emphasis>credenciais</emphasis> mencionadas anteriormente? Uma aplicação "
+#~ "executa-se com as credenciais do utilizador que executa o programa."
+
+#~ msgid "Stop, wait, there's more!"
+#~ msgstr "Espere, há mais!"
+
+#~ msgid ""
+#~ "Files have access permissions but since a program is stored in a file, "
+#~ "the program has file access permissions, too."
+#~ msgstr ""
+#~ "Os ficheiros tem permissões de acesso, mas dado que um programa está "
+#~ "guardado num ficheiro, o programa também tem permissões de acesso aos "
+#~ "ficheiros."
+
+#~ msgid "The commands:"
+#~ msgstr "Os comandos:"
+
+#~ msgid ""
+#~ "would give whomever runs <filename>/bin/foo</filename> the same "
+#~ "privileges that the superuser account would have while running the same "
+#~ "application."
+#~ msgstr ""
+#~ "iria dar os mesmos privilégios, a quem executar o <filename>/bin/xpto</"
+#~ "filename>, da conta do super-utilizador, se executasse a mesma aplicação."
+
+#~ msgid ""
+#~ "By setting a special flag, called the <firstterm>set user id bit</"
+#~ "firstterm> or <function>setuid(2)</function>, we can cause the system to "
+#~ "check \"credentials\" made from the program file access permissions, "
+#~ "instead of using the credentials for the user running the "
+#~ "application<footnote><placeholder-1/><screen width=\"60\"># chown root:"
+#~ "root /bin/foo\n"
+#~ "# chmod 06555 /bin/foo</screen><placeholder-2/></footnote>."
+#~ msgstr ""
+#~ "Ao definir uma opção especial, chamada de <firstterm>bit de definição do "
+#~ "ID de utilizador</firstterm> ou <function>setuid(2)</function>, poderá "
+#~ "fazer com que o sistema verifique as "credenciais" feitas com "
+#~ "base nas permissões de acesso ao ficheiro, em vez de usar as credenciais "
+#~ "do utilizador que executa a aplicação<footnote><screen width=\"60\"># "
+#~ "chown root:root /bin/xpto\n"
+#~ "# chmod 06555 /bin/xpto</screen><placeholder-2/></footnote>."
+
+#~ msgid ""
+#~ "This ability to use the credentials of an application, instead of those "
+#~ "of the user, can be a great boon to multiuser applications such as "
+#~ "databases or email delivery agents. The feature has its proper use on a "
+#~ "Linux system."
+#~ msgstr ""
+#~ "Esta capacidade de usar as credenciais de uma aplicação, em vez das do "
+#~ "utilizador, poderá ser uma grande ajuda para as aplicações multi-"
+#~ "utilizador, como as bases de dados ou os agentes de entrega de e-mail. A "
+#~ "funcionalidade tem o seu uso próprio num sistema Linux."
+
+#~ msgid ""
+#~ "As useful as it is, one must resist the temptation to make a shell "
+#~ "program, such as <filename>/bin/bash</filename>, or a shell script, such "
+#~ "as <filename>/usr/local/bin/run_as_root</filename>, be set user ID to "
+#~ "root."
+#~ msgstr ""
+#~ "Dada a sua utilidade, uma pessoa deverá resistir à tentação de mudar um "
+#~ "programa, como a <filename>/bin/bash</filename>, ou outro programa, como "
+#~ "a <filename>/usr/local/bin/correr_como_root</filename>, para ser 'setuid' "
+#~ "para 'root'."
+
+#~ msgid ""
+#~ "If this were to be done, then <emphasis>any</emphasis> user running that "
+#~ "script or application would be able to access any file that the root "
+#~ "account could access."
+#~ msgstr ""
+#~ "Se isso fosse feito, então <emphasis>qualquer</emphasis> utilizador que "
+#~ "corresse esse programa ou aplicação seria capaz de aceder a qualquer "
+#~ "ficheiro que a conta de 'root' conseguisse aceder."
+
+#~ msgid ""
+#~ "Again, the objections to this method a similar to those we mentioned for "
+#~ "the <application>su(1)</application> program: no control, and no "
+#~ "traceability."
+#~ msgstr ""
+#~ "Mais uma vez, as objecções a este método são semelhantes às mencionadas "
+#~ "para o programa <application>su(1)</application>: sem controlo, e sem "
+#~ "qualquer registo."
+
+#~ msgid "A Safer Alternative: sudo(8)"
+#~ msgstr "Uma Alternativa Mais Segura: sudo(8)"
+
+#~ msgid ""
+#~ "The <application>sudo(8)</application> program solves the dilemma of how "
+#~ "to allow ordinary users access to certain privileged system resources yet "
+#~ "still keep the superuser password secret."
+#~ msgstr ""
+#~ "O programa <application>sudo(8)</application> resolve o dilema de como "
+#~ "permitir aos utilizadores normais o acesso a certos recursos "
+#~ "privilegiados do sistema, mantendo à mesma a senha do super-utilizador em "
+#~ "segredo."
+
+#~ msgid ""
+#~ "Before granting privileges to a user, the <application>sudo(8)</"
+#~ "application> program checks the configuration file <filename>/etc/"
+#~ "sudoers</filename> and:"
+#~ msgstr ""
+#~ "Antes de aceder os privilégios a um utilizador, o programa "
+#~ "<application>sudo(8)</application> verifica o ficheiro de configuração "
+#~ "<filename>/etc/sudoers</filename> e:"
+
+#~ msgid "Grants privileges to the user without requiring any password at all."
+#~ msgstr "Cede os privilégios ao utilizador sem necessitar de qualquer senha."
+
+#~ msgid ""
+#~ "Grants privileges to the user if, and only if, the user supplies the "
+#~ "correct password to prove their identity. Note that this is the password "
+#~ "for the user account, <emphasis>not</emphasis> the superuser password."
+#~ msgstr ""
+#~ "Cede os privilégios ao utilizador se, e só se, o utilizador indicar a sua "
+#~ "senha correcta, para provar a sua identidade. Lembre-se que esta é a "
+#~ "senha da conta do utilizador, <emphasis>não</emphasis> a senha do super-"
+#~ "utilizador."
+
+#~ msgid ""
+#~ "Deny the access and notify the system administrator of the failed attempt "
+#~ "via an email sent to the root account."
+#~ msgstr ""
+#~ "Negar o acesso e notificar o administrador do sistema da tentativa "
+#~ "falhada com um e-mail enviado para a conta do 'root'."
+
+#~ msgid ""
+#~ "Log the command, its arguments, and timestamp into the <filename>/var/log/"
+#~ "secure</filename> file."
+#~ msgstr ""
+#~ "Regista o comando, os seus argumentos e a hora no ficheiro <filename>/var/"
+#~ "log/secure</filename>."
+
+#~ msgid ""
+#~ "<application>Sudo(8)</application> keeps a log of all activity in the "
+#~ "<filename>/var/log/secure</filename> file. Thus, there is an audit trail "
+#~ "recording everything done in the name of the system administrator."
+#~ msgstr ""
+#~ "O <application>sudo(8)</application> mantém um registo de toda a "
+#~ "actividade no ficheiro <filename>/var/log/secure</filename>. Deste modo, "
+#~ "existe um registo para auditoria que guarda tudo o que é feito em nome do "
+#~ "administrador do sistema."
+
+#~ msgid "Controlling Access To sudo(8)"
+#~ msgstr "controlar o Acesso ao sudo(8)"
+
+#~ msgid ""
+#~ "The <filename>/etc/sudoers</filename> file configures the programs that "
+#~ "users can access using <application>sudo(8)</application>, along with "
+#~ "whether or not a password will be needed."
+#~ msgstr ""
+#~ "O ficheiro <filename>/etc/sudoers</filename> configura os programas que "
+#~ "os utilizadores poderão aceder com o <application>sudo(8)</application>, "
+#~ "para além do facto de ser necessária uma senha ou não."
+
+#~ msgid ""
+#~ "The system administrator adds users to this file using the <filename>/usr/"
+#~ "sbin/visudo</filename> command. Each non-comment line in the file has two "
+#~ "parts:"
+#~ msgstr ""
+#~ "O administrador do sistema adiciona os utilizadores a este ficheiro com o "
+#~ "comando <filename>/usr/sbin/visudo</filename>. Cada linha, sem ser os "
+#~ "comentários, tem duas partes:"
+
+#~ msgid "A username (\"reynolds\"), or a group name (\"%wheel\")."
+#~ msgstr "Um utilizador (\"ze\"), ou um nome de grupo (\"%utilizadores\")."
+
+#~ msgid ""
+#~ "A list of machine names where a program may be run, or the keyword "
+#~ "<literal>ALL</literal>. Following an equal sign (<literal>=</literal>), a "
+#~ "list of user identities the command may be run as, enclosed in round "
+#~ "brackets (parenthesis); the wildcard <literal>ALL</literal> may also "
+#~ "appear. Finally, a list of applications which may be run as the named "
+#~ "users; the keyword <literal>ALL</literal> is a wildcard."
+#~ msgstr ""
+#~ "Uma lista com os nomes de máquinas onde um programa poderá ser executado, "
+#~ "ou a palavra-chave <literal>ALL</literal>. A seguir a um sinal de igual "
+#~ "(<literal>=</literal>), existe uma lista de utilizadores que identifica "
+#~ "quem pode executar o comando, entre parêntesis; a palavra-chave "
+#~ "<literal>ALL</literal> também poderá aparecer. Finalmente, uma lista de "
+#~ "aplicações que poderão ser executadas com os utilizadores indicados; a "
+#~ "palavra-chave <literal>ALL</literal> é uma sequência especial."
+
+#~ msgid "The following examples should help make this clear:"
+#~ msgstr "Os exemplos seguintes deverão clarificar isto:"
+
+#~ msgid "/etc/sudoers Examples"
+#~ msgstr "Exemplos do /etc/sudoers"
+
+#~ msgid "reynolds ALL=(ALL) ALL"
+#~ msgstr "ze ALL=(ALL) ALL"
+
+#~ msgid ""
+#~ "User reynolds can execute any command as any user, but must know the "
+#~ "password to the reynolds account."
+#~ msgstr ""
+#~ "O utilizador 'ze' poderá executar qualquer comando, como qualquer "
+#~ "utilizador, mas precisa de saber a senha da conta 'ze'."
+
+#~ msgid "reynolds ALL=(root) shutdown"
+#~ msgstr "ze ALL=(root) shutdown"
+
+#~ msgid ""
+#~ "User reynolds can execute only command <application>shutdown</"
+#~ "application>, but must know the password to the reynolds account."
+#~ msgstr ""
+#~ "O utilizador 'ze' poderá executar apenas o comando <application>shutdown</"
+#~ "application>, mas precisa de saber a senha da conta 'ze'."
+
+#~ msgid "reynolds ALL=(root) NOPASSWD: /usr/bin/id"
+#~ msgstr "ze ALL=(root) NOPASSWD: /usr/bin/id"
+
+#~ msgid ""
+#~ "User reynolds can execute only the application <filename>/usr/bin/id</"
+#~ "filename>; no password will be needed."
+#~ msgstr ""
+#~ "O utilizador 'ze' poderá executar apenas a aplicação <filename>/usr/bin/"
+#~ "id</filename>; não será necessária qualquer senha."
+
+#~ msgid "Using sudo(8)"
+#~ msgstr "Usar o sudo(8)"
+
+#~ msgid ""
+#~ "Once the system administrator has entered the necessary setup into the "
+#~ "<filename>/etc/sudoers</filename> file, users can safely access "
+#~ "privileged system resources and activities like this:"
+#~ msgstr ""
+#~ "Logo que o administrador do sistema tenha introduzido a configuração "
+#~ "necessária no ficheiro <filename>/etc/sudoers</filename>, os utilizadores "
+#~ "poderão aceder em segurança aos recursos do sistema privilegiados e a "
+#~ "actividades da seguinte forma:"
+
+#~ msgid ""
+#~ "$ sudo reboot\n"
+#~ "Password:"
+#~ msgstr ""
+#~ "$ sudo reboot\n"
+#~ "Password:"
+
+#~ msgid ""
+#~ "No awkward quoting on the command line, just prefix the command you want "
+#~ "with the word <userinput>sudo</userinput>. If you want to run the command "
+#~ "as a user other than <userinput>root</userinput>, just add the <option>-u "
+#~ "</option><replaceable>username</replaceable> switch:"
+#~ msgstr ""
+#~ "Não precisa de colocar a linha de comandos entre aspas, basta anteceder o "
+#~ "comando que deseja com a palavra <userinput>sudo</userinput>. Se quiser "
+#~ "executar o comando com um utilizador que não o <userinput>root</"
+#~ "userinput>, basta adicionar a opção <option>-u </"
+#~ "option><replaceable>utilizador</replaceable>:"
+
+#~ msgid "$ sudo -u reynolds id"
+#~ msgstr "$ sudo -u ze id"
+
+#~ msgid ""
+#~ "There will be a log entry written to the <filename>/var/log/secure</"
+#~ "filename> file to show who did the deed."
+#~ msgstr ""
+#~ "Existirá um elemento gravado no registo do ficheiro <filename>/var/log/"
+#~ "secure</filename>, a mostrar quem fez tal acção."
+
+#~ msgid ""
+#~ "Of course, the sysadmin may have configured <application>sudo(8)</"
+#~ "application> not to request a password. In this case, the command is "
+#~ "immediately executed although the audit trail entry will still be written."
+#~ msgstr ""
+#~ "Obviamente, o administrador do sistema poderá ter configurado o "
+#~ "<application>sudo(8)</application> para não pedir uma senha. Nesse caso, "
+#~ "o comando é executado imediatamente, ainda que o item de registo para "
+#~ "auditoria será gravado à mesma."
+
+#~ msgid "And, In Conclusion"
+#~ msgstr "E, como Conclusão"
+
+#~ msgid ""
+#~ "The <application>sudo(8)</application> program provides a safe, "
+#~ "controlled facility that allows a user to run a defined set of programs "
+#~ "using the credentials of a defined set of users. The superuser password "
+#~ "need never be publicised or compromised, since <application>sudo(8)</"
+#~ "application> is controlled from a configuration file crafted by the "
+#~ "system administrator."
+#~ msgstr ""
+#~ "O programa <application>sudo(8)</application> oferece uma funcionalidade "
+#~ "segura e controlada que permite a um utilizador executar um conjunto "
+#~ "definido de programas com as credenciais de um conjunto também bem "
+#~ "definido de utilizadores. A senha do super-utilizador nunca poderá ser "
+#~ "publicada ou comprometida, dado que o <application>sudo(8)</application> "
+#~ "é controlado por um ficheiro de configuração criado pelo administrador do "
+#~ "sistema."
+
+#~ msgid ""
+#~ "All commands run by <application>sudo(8)</application> are logged to the "
+#~ "<filename>/var/log/secure</filename> file, while access violations are "
+#~ "reported via email. Traceability results."
+#~ msgstr ""
+#~ "Todos os comandos executados pelo <application>sudo(8)</application> são "
+#~ "registados no ficheiro <filename>/var/log/secure</filename>, enquanto as "
+#~ "violações de acesso são comunicadas por e-mail. O acompanhamento resulta."
+
+#~ msgid ""
+#~ "From a user perspective, <application>sudo(8)</application> is easy to "
+#~ "use: simply prefix the desired command line with the word "
+#~ "<wordasword>sudo</wordasword>, press return, and possibly enter a "
+#~ "password (but <emphasis>not</emphasis> the superuser password)."
+#~ msgstr ""
+#~ "Da perspectiva de um utilizador, o <application>sudo(8)</application> é "
+#~ "simples de usar: basta anteceder o comando desejado com a palavra "
+#~ "<wordasword>sudo</wordasword>, carregar em Return e, possivelmente, "
+#~ "introduzir uma senha (mas <emphasis>não</emphasis> a senha do super-"
+#~ "utilizador)."
+
#~ msgid "<glossterm>u</glossterm>"
#~ msgstr "<glossterm>u</glossterm>"
#~ msgid "<glossterm>f</glossterm>"
#~ msgstr "<glossterm>f</glossterm>"
-
-#~ msgid "Tommy Reynolds"
-#~ msgstr "Tommy Reynolds"
-
-#~ msgid "Sudo Tutorial"
-#~ msgstr "Tutorial do Sudo"
More information about the docs-commits
mailing list