# translation of kppp_security.po to 
# translation of kppp_security.po to
# Copyright (C) 2002 Free Software Foundation, Inc.
# Lwandle Mgidlana <lwandle@translate.org.za>, 2002
#
msgid ""
msgstr ""
"Project-Id-Version: kppp_security\n"
"POT-Creation-Date: 2001-02-09 01:25+0100\n"
"PO-Revision-Date: 2002-09-26 12:34+0200\n"
"Last-Translator: Lwandle Mgidlana <lwandle@translate.org.za>\n"
"Language-Team:  <xh@li.org>\n"
"MIME-Version: 1.0\n"
"Content-Type: application/x-xml2pot; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
"X-Generator: KBabel 1.0beta2\n"

#: index.docbook:2
#, no-c-format
msgid "&kppp; and security issues"
msgstr ""

#: index.docbook:4
#, no-c-format
msgid ""
"This section is mainly for superusers (<systemitem>root</systemitem>"
") people with high security demands, or simply technically interested "
"people. It is not necessary to read this if you only use &Linux; at home for "
"yourself, although you may learn a thing or two in any case."
msgstr ""

#: index.docbook:10
#, no-c-format
msgid "Restricting access to &kppp;"
msgstr ""

#: index.docbook:12
#, no-c-format
msgid ""
"A system administrator might want to restrict access as to who is allowed to "
"use &kppp;. There are two ways to accomplish this."
msgstr ""

#: index.docbook:16
#, no-c-format
msgid "Restricting access with group permissions"
msgstr ""

#: index.docbook:18
#, no-c-format
msgid ""
"Create a new group (you might want to name it "
"<systemitem>dialout</systemitem>"
" or similar), and put every user that should be allowed to use &kppp; into "
"that group. Then type at the prompt:"
msgstr ""

#: index.docbook:22
#, no-c-format
msgid ""
"<prompt>#</prompt> <userinput><command>chown</command> "
"<option>root.dialout</option> "
"<filename>/opt/kde/bin/kppp</filename></userinput>\n"
"<prompt>#</prompt> <userinput><command>chmod</command> <option>4750</option>"
" <filename>/opt/kde/bin/kppp</filename></userinput>"
msgstr ""

#: index.docbook:26
#, no-c-format
msgid ""
"This assumes that &kde; was installed in <filename class=\"directory\"> "
"/opt/kde/</filename> and that your new group is named "
"<systemitem>dialout</systemitem>."
msgstr ""

#: index.docbook:33
#, no-c-format
msgid "Restricting access &kppp;'s way"
msgstr ""

#: index.docbook:35
#, no-c-format
msgid ""
"Before doing anything, &kppp; checks if there is a file named "
"<filename>/etc/kppp.allow</filename>. If such a file exists, only users "
"named in this file are allowed to dial out. This file must be readable by "
"everyone (but of course <emphasis>NOT</emphasis>"
" writable.) Only login names are recognized, so you cannot use "
"<acronym>UID</acronym>'s in this file. Here is a short example:"
msgstr ""

#: index.docbook:42
#, no-c-format
msgid ""
"# /etc/kppp.allow\n"
"# comment lines like this are ignored\n"
"# as well as empty lines\n"
"\n"
"fred\n"
"karl\n"
"daisy"
msgstr ""

#: index.docbook:52
#, no-c-format
msgid ""
"In the example above, only the users <systemitem>fred</systemitem>, "
"<systemitem>karl</systemitem> and <systemitem>daisy</systemitem>"
" are allowed to dial out, as well as every user with a "
"<acronym>UID</acronym> of 0 (so you don't have to explicitly list root in "
"the file)."
msgstr ""

#: index.docbook:62
#, no-c-format
msgid "&kppp; has the <acronym>SUID</acronym> bit on? What about security?"
msgstr ""

#: index.docbook:65
#, no-c-format
msgid ""
"It's virtually impossible to write a dialler without the "
"<acronym>SUID</acronym> bit that is both safe and easy to use for "
"inexperienced users. &kppp; addresses the security issues with the following "
"strategy."
msgstr ""

#: index.docbook:69
#, no-c-format
msgid "Immediately after the program starts, &kppp; forks."
msgstr ""

#: index.docbook:69
#, no-c-format
msgid ""
"The master process, which handles all the <acronym>GUI</acronym> operations "
"(such as user interaction), drops the <acronym>SUID</acronym> state after "
"the fork, and runs with normal user privileges."
msgstr ""

#: index.docbook:69
#, no-c-format
msgid ""
"The slave process keeps its privileges, and is responsible for all actions "
"that need <systemitem>root</systemitem> privileges. To keep this part safe, "
"no &kde; or &Qt; library calls are used here, just simple library calls. The "
"source code for this process is short (around 500 lines) and well "
"documented, so it's easy for you to check it for security holes."
msgstr ""

#: index.docbook:69
#, no-c-format
msgid ""
"Master and slave processes communicate with standard &UNIX; "
"<acronym>IPC</acronym>."
msgstr ""

#: index.docbook:91
#, no-c-format
msgid ""
"Special thanks to Harri Porten for writing this excellent piece of code. It "
"was thought to be impossible, but he managed it within a week."
msgstr ""
