sudo-tutorial/po de.po,1.3,1.4
Fabian Affolter (fab)
fedora-docs-commits at redhat.com
Sun Oct 21 11:50:13 UTC 2007
Author: fab
Update of /cvs/docs/sudo-tutorial/po
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv23600
Added Files:
de.po
Log Message:
initial version
Index: de.po
===================================================================
RCS file: de.po
diff -N de.po
--- /dev/null 1 Jan 1970 00:00:00 -0000
+++ de.po 21 Oct 2007 11:50:11 -0000 1.4
@@ -0,0 +1,517 @@
+msgid ""
+msgstr ""
+"Project-Id-Version: sudo-tutorial\n"
+"POT-Creation-Date: 2006-08-05 20:04-0400\n"
+"PO-Revision-Date: 2007-10-21 13:49+0100\n"
+"Last-Translator: Fabian Affolter <fab at fedoraproject.org>\n"
+"Language-Team: german <fedora-trans.de at redhat.com>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"X-Poedit-Language: german\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 "Dokument Name"
+
+#: en_US/doc-entities.xml:8(text)
+msgid "sudo-tutorial"
+msgstr "sudo-tutorial"
+
+#: en_US/doc-entities.xml:11(comment)
+msgid "Version number"
+msgstr "Versions-Nummer"
+
+#: en_US/doc-entities.xml:12(text)
+msgid "0.0.2"
+msgstr "0.0.2"
+
+#: en_US/doc-entities.xml:15(comment)
+msgid "Date of last revision"
+msgstr "Datum der letzten Revision"
+
+#: en_US/doc-entities.xml:16(text)
+msgid "2006-08-05"
+msgstr "2006-08-05"
+
+#: en_US/doc-entities.xml:19(comment)
+msgid "Document ID"
+msgstr "Document ID"
+
+#: en_US/doc-entities.xml:20(text)
+msgid "<use entity=\"DOCNAME\"/>-<use entity=\"DOCVERSION\"/> (<use entity=\"DOCDATE\"/>)"
+msgstr "<use entity=\"DOCNAME\"/>-<use entity=\"DOCVERSION\"/> (<use entity=\"DOCDATE\"/>)"
+
+#: en_US/doc-entities.xml:26(comment)
+msgid "Name of program"
+msgstr "Programmname"
+
+#: en_US/doc-entities.xml:27(text)
+msgid "<command>sudo(8)</command>"
+msgstr "<command>sudo(8)</command>"
+
+#: en_US/rpm-info.xml:13(rights)
+msgid "OPL"
+msgstr "OPL"
+
+#: en_US/rpm-info.xml:14(version)
+msgid "1.0"
+msgstr "1.0"
+
+#: en_US/rpm-info.xml:17(year)
+msgid "2005"
+msgstr "2005"
+
+#: en_US/rpm-info.xml:18(year)
+msgid "2006"
+msgstr "2006"
+
+#: en_US/rpm-info.xml:19(holder)
+msgid "Tommy Reynolds"
+msgstr "Tommy Reynolds"
+
+#: en_US/rpm-info.xml:20(holder)
+msgid "Paul W. Frields"
+msgstr "Paul W. Frields"
+
+#: en_US/rpm-info.xml:22(title)
+msgid "Sudo Tutorial"
+msgstr "Sudo Tutorial"
+
+#: en_US/rpm-info.xml:23(desc)
+msgid "Guide to using sudo to perform tasks as another user"
+msgstr ""
+
+#: en_US/rpm-info.xml:27(details)
+msgid "Some editing work completed, not ready for translation yet."
+msgstr ""
+
+#: en_US/rpm-info.xml:31(details)
+msgid "Dummy version"
+msgstr "Dummy Version"
+
+#: en_US/sudo-tutorial.xml:18(title)
+msgid "Introduction"
+msgstr "Einführung"
+
+#: en_US/sudo-tutorial.xml:20(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:32(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:41(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:39(para)
+msgid ""
+"Although <command>sudo(8)</command><footnote><placeholder-1/><screen>\n"
+"<command>man 2 exit</command>\n"
+"<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_US/sudo-tutorial.xml:64(title)
+#, fuzzy
+msgid "How Linux Controls Access"
+msgstr "Linux-native asynchronous I/O Zugriffs-Bibliothek"
+
+#: en_US/sudo-tutorial.xml:65(para)
+msgid "To better understand the benefits of <command>sudo(8)</command>, 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:73(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_US/sudo-tutorial.xml:82(title)
+msgid "Who Are You?"
+msgstr "Wer sind Sie?"
+
+#: en_US/sudo-tutorial.xml:83(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:97(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:90(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/></footnote>."
+msgstr ""
+
+#: en_US/sudo-tutorial.xml:105(para)
+msgid "After a successful authentication the system uses your uid and gid to control your access to system resources."
+msgstr ""
+
+#: en_US/sudo-tutorial.xml:110(title)
+msgid "File Access Permissions"
+msgstr "Datei-Zugriffsrechte"
+
+#: en_US/sudo-tutorial.xml:111(para)
+msgid "Every system resource, whether an application program, directory, or file, has a unique <firstterm>filename</firstterm>. 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 <firstterm>file system</firstterm>."
+msgstr ""
+
+#: en_US/sudo-tutorial.xml:118(para)
+msgid "In addition to the file content itself, the file system keeps extra information about every file. This <firstterm>metadata</firstterm> includes the file's size, disk block locations, and modification and access timestamps. You can see most of this metadata using the <command>ls(1)</command> program:"
+msgstr ""
+
+#: en_US/sudo-tutorial.xml:127(title)
+msgid "Using ls(1) to examine file permissions"
+msgstr ""
+
+#: en_US/sudo-tutorial.xml:130(userinput)
+#, no-wrap
+msgid "ls -l /bin/mail"
+msgstr "ls -l /bin/mail"
+
+#: en_US/sudo-tutorial.xml:131(computeroutput)
+#, no-wrap
+msgid "-rwxr-xr-x 1 root mail 73588 Apr 4 07:03 /bin/mail"
+msgstr "-rwxr-xr-x 1 root mail 73588 Apr 4 07:03 /bin/mail"
+
+#: en_US/sudo-tutorial.xml:141(para)
+msgid "The <command>chown(1)</command> program allows the ownership credentials to be changed."
+msgstr ""
+
+#: en_US/sudo-tutorial.xml:135(para)
+msgid "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 <emphasis>ownership</emphasis> of that file<footnote><placeholder-1/></footnote>. In our example, <filename>/bin/mail</filename> is owned by user <systemitem class=\"username\">root</systemitem> and group <systemitem class=\"groupname\">mail</systemitem>."
+msgstr ""
+
+#: en_US/sudo-tutorial.xml:149(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. These are usually abbreviated as <computeroutput>rwx</computeroutput>. Permissions for a file which could be read, but neither written nor executed, would be written as <computeroutput>r--</computeroutput>. Remember, the notation is positional and order matters."
+msgstr ""
+
+#: en_US/sudo-tutorial.xml:158(para)
+msgid "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."
+msgstr ""
+
+#: en_US/sudo-tutorial.xml:166(title)
+#, fuzzy
+msgid "May I Access This File, Please?"
+msgstr "diese Datei darf keine »domain«-Anweisung enthalten"
+
+#: en_US/sudo-tutorial.xml:167(para)
+msgid "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:"
+msgstr ""
+
+#: en_US/sudo-tutorial.xml:174(title)
+#, fuzzy
+msgid "Determining File Access"
+msgstr "Kann auf die Datei %s nicht zugreifen\n"
+
+#: en_US/sudo-tutorial.xml:175(programlisting)
+#, no-wrap
+msgid ""
+"if( u.uid == f.uid ) { rwx = perms.owner; }\n"
+"\t else if( u.gid == f.gid ) { rwx = perms.group; } else { rwx =\n"
+"\t perms.world; } if( !accessok( access_wanted, rwx ) ) { errno = EPERM;\n"
+"\t return( -1 ); } do_access();"
+msgstr ""
+
+#: en_US/sudo-tutorial.xml:180(para)
+#, fuzzy
+msgid "Assuming the following definitions:"
+msgstr "Gefundene Definitionen verwerfen"
+
+#: en_US/sudo-tutorial.xml:185(glossterm)
+msgid "u"
+msgstr "u"
+
+#: en_US/sudo-tutorial.xml:187(para)
+msgid "Represents the user credentials containing both the <abbrev>uid</abbrev> and <abbrev>gid</abbrev>."
+msgstr ""
+
+#: en_US/sudo-tutorial.xml:194(glossterm)
+msgid "f"
+msgstr "f"
+
+#: en_US/sudo-tutorial.xml:196(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 ""
+
+#: en_US/sudo-tutorial.xml:205(glossterm)
+msgid "perms"
+msgstr "perms"
+
+#: en_US/sudo-tutorial.xml:206(para)
+msgid "The file access permissions for the file, including all three sets of permissions: owner, group and world."
+msgstr ""
+
+#: en_US/sudo-tutorial.xml:212(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_US/sudo-tutorial.xml:220(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_US/sudo-tutorial.xml:230(title)
+#, fuzzy
+msgid "What Not To Do"
+msgstr "Nicht versuchen, X zu verwenden"
+
+#: en_US/sudo-tutorial.xml:232(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_US/sudo-tutorial.xml:245(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_US/sudo-tutorial.xml:255(title)
+msgid "Perhaps You Have Heard Of The su(1) Application?"
+msgstr ""
+
+#: en_US/sudo-tutorial.xml:256(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_US/sudo-tutorial.xml:265(title)
+#, fuzzy
+msgid "Traditional Approach Using su(1)"
+msgstr "es wird empfohlen, in traditionellem C nicht #elif zu verwenden"
+
+#: en_US/sudo-tutorial.xml:266(screen)
+#, no-wrap
+msgid ""
+"$ id uid=500(reynolds) gid=500(reynolds)\n"
+"\t groups=500(reynolds) $ su -c id Password: uid=0(root) gid=0(root)\n"
+"\t groups=0(root),1(bin)..."
+msgstr ""
+"$ id uid=500(reynolds) gid=500(reynolds)\n"
+"\t groups=500(reynolds) $ su -c id Password: uid=0(root) gid=0(root)\n"
+"\t groups=0(root),1(bin)..."
+
+#: en_US/sudo-tutorial.xml:271(para)
+msgid "There are some problems with this approach:"
+msgstr ""
+
+#: en_US/sudo-tutorial.xml:277(para)
+#, fuzzy
+msgid "The superuser password is compromised."
+msgstr "Ein Passwortübergang ist notwendig"
+
+#: en_US/sudo-tutorial.xml:280(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_US/sudo-tutorial.xml:288(para)
+#, fuzzy
+msgid "There is no audit trail."
+msgstr "%s: momentan existiert keine Aktion"
+
+#: en_US/sudo-tutorial.xml:294(para)
+msgid "In security parlance, \"to trust\" is identical to \"be at risk from\"."
+msgstr ""
+
+#: en_US/sudo-tutorial.xml:291(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_US/sudo-tutorial.xml:306(title)
+msgid "Please, No Setuid Shell Scripts"
+msgstr ""
+
+#: en_US/sudo-tutorial.xml:307(para)
+msgid "Another technology, used by the <application>su(1)</application> program, takes advantage of a neat feature."
+msgstr ""
+
+#: en_US/sudo-tutorial.xml:311(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_US/sudo-tutorial.xml:317(para)
+#, fuzzy
+msgid "Stop, wait, there's more!"
+msgstr "Es gibt keine gültigen Züge mehr."
+
+#: en_US/sudo-tutorial.xml:320(para)
+msgid "Files have access permissions but since a program is stored in a file, the program has file access permissions, too."
+msgstr ""
+
+#: en_US/sudo-tutorial.xml:330(para)
+msgid "The commands:"
+msgstr "Die Befehle :"
+
+#: en_US/sudo-tutorial.xml:335(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_US/sudo-tutorial.xml:324(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 # chmod 06555\n"
+"\t /bin/foo</screen><placeholder-2/></footnote>."
+msgstr ""
+
+#: en_US/sudo-tutorial.xml:342(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_US/sudo-tutorial.xml:348(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_US/sudo-tutorial.xml:354(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_US/sudo-tutorial.xml:359(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_US/sudo-tutorial.xml:369(title)
+#, fuzzy
+msgid "A Safer Alternative: sudo(8)"
+msgstr "Alternative Installationsmethoden "
+
+#: en_US/sudo-tutorial.xml:370(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_US/sudo-tutorial.xml:375(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_US/sudo-tutorial.xml:382(para)
+msgid "Grants privileges to the user without requiring any password at all."
+msgstr ""
+
+#: en_US/sudo-tutorial.xml:387(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_US/sudo-tutorial.xml:395(para)
+msgid "Deny the access and notify the system administrator of the failed attempt via an email sent to the root account."
+msgstr ""
+
+#: en_US/sudo-tutorial.xml:400(para)
+msgid "Log the command, its arguments, and timestamp into the <filename>/var/log/secure</filename> file."
+msgstr ""
+
+#: en_US/sudo-tutorial.xml:405(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_US/sudo-tutorial.xml:412(title)
+#, fuzzy
+msgid "Controlling Access To sudo(8)"
+msgstr "Zugriff auf den Datenträger nicht möglich."
+
+#: en_US/sudo-tutorial.xml:413(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_US/sudo-tutorial.xml:418(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_US/sudo-tutorial.xml:425(para)
+msgid "A username (\"reynolds\"), or a group name (\"%wheel\")."
+msgstr ""
+
+#: en_US/sudo-tutorial.xml:429(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_US/sudo-tutorial.xml:440(para)
+msgid "The following examples should help make this clear:"
+msgstr ""
+
+#: en_US/sudo-tutorial.xml:445(title)
+msgid "/etc/sudoers Examples"
+msgstr "/etc/sudoers Beispiele"
+
+#: en_US/sudo-tutorial.xml:449(computeroutput)
+#, no-wrap
+msgid "reynolds ALL=(ALL) ALL"
+msgstr "reynolds ALL=(ALL) ALL"
+
+#: en_US/sudo-tutorial.xml:452(para)
+msgid "User reynolds can execute any command as any user, but must know the password to the reynolds account."
+msgstr ""
+
+#: en_US/sudo-tutorial.xml:460(computeroutput)
+#, no-wrap
+msgid "reynolds ALL=(root) shutdown"
+msgstr "reynolds ALL=(root) shutdown"
+
+#: en_US/sudo-tutorial.xml:463(para)
+msgid "User reynolds can execute only command <application>shutdown</application>, but must know the password to the reynolds account."
+msgstr ""
+
+#: en_US/sudo-tutorial.xml:472(computeroutput)
+#, no-wrap
+msgid ""
+"reynolds ALL=(root) NOPASSWD:\n"
+"\t\t/usr/bin/id"
+msgstr ""
+"reynolds ALL=(root) NOPASSWD:\n"
+"\t\t/usr/bin/id"
+
+#: en_US/sudo-tutorial.xml:476(para)
+msgid "User reynolds can execute only the application <filename>/usr/bin/id</filename>; no password will be needed."
+msgstr ""
+
+#: en_US/sudo-tutorial.xml:488(title)
+msgid "Using sudo(8)"
+msgstr "Using sudo(8)"
+
+#: en_US/sudo-tutorial.xml:489(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_US/sudo-tutorial.xml:494(screen)
+#, no-wrap
+msgid "$ sudo reboot Password:"
+msgstr "$ sudo reboot Password:"
+
+#: en_US/sudo-tutorial.xml:495(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_US/sudo-tutorial.xml:501(screen)
+#, no-wrap
+msgid "$ sudo -u reynolds id"
+msgstr "$ sudo -u reynolds id"
+
+#: en_US/sudo-tutorial.xml:502(para)
+msgid "There will be a log entry written to the <filename>/var/log/secure</filename> file to show who did the deed."
+msgstr ""
+
+#: en_US/sudo-tutorial.xml:506(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 ""
+
+#: en_US/sudo-tutorial.xml:516(title)
+msgid "And, In Conclusion"
+msgstr "Und, in der Zusammenfassung"
+
+#: en_US/sudo-tutorial.xml:517(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 ""
+
+#: en_US/sudo-tutorial.xml:524(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 ""
+
+#: en_US/sudo-tutorial.xml:529(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 ""
+
+#: en_US/sudo-tutorial.xml:535(para)
+msgid "End Of Document"
+msgstr "Ende des Dokuments"
+
+#. Put one translator per line, in the form of NAME <EMAIL>, YEAR1, YEAR2.
+#: en_US/sudo-tutorial.xml:0(None)
+msgid "translator-credits"
+msgstr "Fabian Affolter <fab at fedoraproject.org>, 2007."
+
More information about the Fedora-docs-commits
mailing list