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

Translation

(itstool) path: section/screen
English
<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>
Context English Spanish State
A chunk of information associated with the account, such as a password or passphrase, which the applicant must provide to prove his identity. Un chunk de información asociado con la cuenta, como una contraseña o frase, que el applicant debe proporcionar para probar su identidad.
transaction transaction
A sequence of requests from the same applicant to the same instance of the same server, beginning with authentication and session set-up and ending with session tear-down. Una secuencia de solicitudes del mismo applicant a la misma instancia del mismo servidor, comenzando con la autenticación y la configuración de la sesión y terminando con el desmantelamiento de la sesión.
Usage Examples Ejemplos de uso
This section aims to illustrate the meanings of some of the terms defined above by way of a handful of simple examples. Esta sección tiene como objetivo ilustrar los significados de algunos de los términos definidos anteriormente mediante un puñado de ejemplos simples.
Client and Server Are One El cliente y el servidor son uno
This simple example shows <literal>alice</literal> <citerefentry><refentrytitle>su</refentrytitle><manvolnum>1</manvolnum></citerefentry>'ing to <literal>root</literal>. Este ejemplo sencillo muestra a <literal>alice</literal> usando el comando <citerefentry><refentrytitle>su</refentrytitle><manvolnum>1</manvolnum></citerefentry> para convertirse en <literal>root</literal>.
<prompt>%</prompt> <userinput>whoami</userinput>
alice
<prompt>%</prompt> <userinput>ls -l `which su`</userinput>
-r-sr-xr-x 1 root wheel 10744 Dec 6 19:06 /usr/bin/su
<prompt>%</prompt> <userinput>su -</userinput>
Password: <userinput>xi3kiune</userinput>
<prompt>#</prompt> whoami
root
<prompt>%</prompt> <userinput>whoami</userinput>
alice
<prompt>%</prompt> <userinput>ls -l `which su`</userinput>
-r-sr-xr-x 1 root wheel 10744 Dec 6 19:06 /usr/bin/su
<prompt>%</prompt> <userinput>su -</userinput>
Password: <userinput>xi3kiune</userinput>
<prompt>#</prompt> whoami
root
The applicant is <literal>alice</literal>. El applicant es <literal>alice</literal>.
The account is <literal>root</literal>. El account es <literal>root</literal>.
The <citerefentry><refentrytitle>su</refentrytitle><manvolnum>1</manvolnum></citerefentry> process is both client and server. El proceso de utilizar <citerefentry><refentrytitle>su</refentrytitle><manvolnum>1</manvolnum></citerefentry> es tanto cliente como servidor.
The authentication token is <literal>xi3kiune</literal>. El token de autenticación es <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>. El arbitrator es <literal>root</literal>, por lo que el comando <citerefentry><refentrytitle>su</refentrytitle><manvolnum>1</manvolnum></citerefentry> es setuid <literal>root</literal>.
Client and Server Are Separate El cliente y el servidor están separados
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! El siguiente ejemplo muestra a <literal>eve</literal> intentando iniciar una conexión por <citerefentry><refentrytitle>ssh</refentrytitle><manvolnum>1</manvolnum></citerefentry> a <literal>login.example.com</literal>, solicita iniciar sesión como <literal>bob</literal>, y tiene éxito. ¡Bob debería de haber elegido una contraseña mejor!
<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>
<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>. El applicant es <literal>eve</literal>.
The client is Eve's <citerefentry><refentrytitle>ssh</refentrytitle><manvolnum>1</manvolnum></citerefentry> process. El client es el proceso <citerefentry><refentrytitle>ssh</refentrytitle><manvolnum>1</manvolnum></citerefentry> de Eve.
The server is the <citerefentry><refentrytitle>sshd</refentrytitle><manvolnum>8</manvolnum></citerefentry> process on <literal>login.example.com</literal> El server es el proceso <citerefentry><refentrytitle>sshd</refentrytitle><manvolnum>8</manvolnum></citerefentry> en <literal>login.example.com</literal>
The account is <literal>bob</literal>. El account es <literal>bob</literal>.
The authentication token is <literal>god</literal>. El token de autenticación es <literal>god</literal>.
Although this is not shown in this example, the arbitrator is <literal>root</literal>. Aunque esto no se muestra en este ejemplo, el arbitrator es <literal>root</literal>.
Sample Policy Política de ejemplo
The following is FreeBSD's default policy for <literal>sshd</literal>: Lo que se muestra a continuación, es la política predeterminada de FreeBSD para <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
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.) Esta política se aplica al servicio <literal>sshd</literal> (que no está restringido necesariamente al servidor <citerefentry><refentrytitle>sshd</refentrytitle><manvolnum>8</manvolnum></citerefentry>).
<literal>auth</literal>, <literal>account</literal>, <literal>session</literal> and <literal>password</literal> are facilities. <literal>auth</literal>, <literal>account</literal>, <literal>session</literal> y <literal>password</literal> son 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.) <filename>pam_nologin.so</filename>, <filename>pam_unix.so</filename>, <filename>pam_login_access.so</filename>, <filename>pam_lastlog.so</filename> y <filename>pam_permit.so</filename> son modules. Está claro que a partir de este ejemplo, <filename>pam_unix.so</filename> proporciona al menos dos funciones (autenticación y administración de cuentas).
PAM Essentials PAM Essentials
Facilities and Primitives Facilities y primitives
The PAM API offers six different authentication primitives grouped in four facilities, which are described below. La API de PAM ofrece seis primitives de autenticación diferentes agrupadas en cuatro facilities, que se describen a continuación.

Loading…

User avatar None

New source string

FreeBSD Doc (Archived) / articles_pamSpanish

New source string a year ago
Browse all component changes

Things to check

Unchanged translation

Source and translation are identical

Reset

Glossary

English Spanish
No related strings found in the glossary.

Source information

Source string comment
(itstool) path: section/screen
Flags
no-wrap
Source string location
article.translate.xml:322
String age
a year ago
Source string age
a year ago
Translation file
articles/es_ES/pam.po, string 58