The translation is temporarily closed for contributions due to maintenance, please come back later.

Source string Read only

(itstool) path: listitem/para
Context English State
The <citerefentry><refentrytitle>su</refentrytitle><manvolnum>1</manvolnum></citerefentry> process is both client and server.
The authentication token is <literal>xi3kiune</literal>.
The arbitrator is <literal>root</literal>, which is why <citerefentry><refentrytitle>su</refentrytitle><manvolnum>1</manvolnum></citerefentry> is setuid <literal>root</literal>.
Client and Server Are Separate
The example below shows <literal>eve</literal> try to initiate an <citerefentry><refentrytitle>ssh</refentrytitle><manvolnum>1</manvolnum></citerefentry> connection to <literal>login.example.com</literal>, ask to log in as <literal>bob</literal>, and succeed. Bob should have chosen a better password!
<prompt>%</prompt> <userinput>whoami</userinput>
eve
<prompt>%</prompt> <userinput>ssh bob@login.example.com</userinput>
bob@login.example.com's password: <userinput>god</userinput>
Last login: Thu Oct 11 09:52:57 2001 from 192.168.0.1
Copyright (c) 1980, 1983, 1986, 1988, 1990, 1991, 1993, 1994
The Regents of the University of California. All rights reserved.
FreeBSD 4.4-STABLE (LOGIN) #4: Tue Nov 27 18:10:34 PST 2001

Welcome to FreeBSD!
<prompt>%</prompt>
The applicant is <literal>eve</literal>.
The client is Eve's <citerefentry><refentrytitle>ssh</refentrytitle><manvolnum>1</manvolnum></citerefentry> process.
The server is the <citerefentry><refentrytitle>sshd</refentrytitle><manvolnum>8</manvolnum></citerefentry> process on <literal>login.example.com</literal>
The account is <literal>bob</literal>.
The authentication token is <literal>god</literal>.
Although this is not shown in this example, the arbitrator is <literal>root</literal>.
Sample Policy
The following is FreeBSD's default policy for <literal>sshd</literal>:
sshd auth required pam_nologin.so no_warn
sshd auth required pam_unix.so no_warn try_first_pass
sshd account required pam_login_access.so
sshd account required pam_unix.so
sshd session required pam_lastlog.so no_fail
sshd password required pam_permit.so
This policy applies to the <literal>sshd</literal> service (which is not necessarily restricted to the <citerefentry><refentrytitle>sshd</refentrytitle><manvolnum>8</manvolnum></citerefentry> server.)
<literal>auth</literal>, <literal>account</literal>, <literal>session</literal> and <literal>password</literal> are facilities.
<filename>pam_nologin.so</filename>, <filename>pam_unix.so</filename>, <filename>pam_login_access.so</filename>, <filename>pam_lastlog.so</filename> and <filename>pam_permit.so</filename> are modules. It is clear from this example that <filename>pam_unix.so</filename> provides at least two facilities (authentication and account management.)
PAM Essentials
Facilities and Primitives
The PAM API offers six different authentication primitives grouped in four facilities, which are described below.
<literal>auth</literal>
<emphasis>Authentication.</emphasis> This facility concerns itself with authenticating the applicant and establishing the account credentials. It provides two primitives:
<citerefentry><refentrytitle>pam_authenticate</refentrytitle><manvolnum>3</manvolnum></citerefentry> authenticates the applicant, usually by requesting an authentication token and comparing it with a value stored in a database or obtained from an authentication server.
<citerefentry><refentrytitle>pam_setcred</refentrytitle><manvolnum>3</manvolnum></citerefentry> establishes account credentials such as user ID, group membership and resource limits.
<literal>account</literal>
<emphasis>Account management.</emphasis> This facility handles non-authentication-related issues of account availability, such as access restrictions based on the time of day or the server's work load. It provides a single primitive:
<citerefentry><refentrytitle>pam_acct_mgmt</refentrytitle><manvolnum>3</manvolnum></citerefentry> verifies that the requested account is available.
<literal>session</literal>
<emphasis>Session management.</emphasis> This facility handles tasks associated with session set-up and tear-down, such as login accounting. It provides two primitives:
<citerefentry><refentrytitle>pam_open_session</refentrytitle><manvolnum>3</manvolnum></citerefentry> performs tasks associated with session set-up: add an entry in the <filename>utmp</filename> and <filename>wtmp</filename> databases, start an SSH agent, etc.

Loading…

No matching activity found.

Browse all component changes

Things to check

Multiple failing checks

Following checks are failing:
Mismatched full stop: Spanish, Portuguese (Brazil)

Reset

Source information

Source string comment
(itstool) path: listitem/para
Flags
read-only
Source string location
article.translate.xml:374
String age
a year ago
Source string age
a year ago
Translation file
articles/pam.pot, string 68