The translation is temporarily closed for contributions due to maintenance, please come back later.
The translation was automatically locked due to following alerts: Could not merge the repository.
Zen

Translation

English type: Plain text
If you are working on a system other than a new default installation, check that [command]#PubkeyAuthentication no# has *not* been set in neither `/etc/ssh/sshd_config` nor any included file from drop-in directory. If connected remotely, not using console or out-of-band access, testing the key-based log in process before disabling password authentication is advised.
415/3680 · 368

This translation is currently locked.

English Spanish Actions
If you want the daemon to start automatically at the boot time, type as `root`:
Si desea que el demonio se inicie automáticamente en el momento del arranque teclee como `root`:
~]#{nbsp}systemctl enable sshd.service
ln -s '/usr/lib/systemd/system/sshd.service' '/etc/systemd/system/multi-user.target.wants/sshd.service'
~]#{nbsp}systemctl enable sshd.service
ln -s '/usr/lib/systemd/system/sshd.service' '/etc/systemd/system/multi-user.target.wants/sshd.service'
See xref:infrastructure-services/Services_and_Daemons.adoc#ch-Services_and_Daemons[Services and Daemons] for more information on how to configure services in {MAJOROS}.
Vea en xref:infrastructure-services/Services_and_Daemons.adoc#ch-Services_and_Daemons[Servicios y Demonios] más información sobre como configurar servicios en {MAJOROS}.
Note that if you reinstall the system, a new set of identification keys will be created. As a result, clients who had connected to the system with any of the OpenSSH tools before the reinstall will see the following message:
Tenga en cuenta que si reinstala el sistema se creará un nuevo conjunto de claves de identificación. Como consecuencia los clientes qu se hubieran conectado al sistema con cualquiera de las herramientas OpenSSH antes de la instalación verán el siguiente mensaje:
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
@ WARNING: REMOTE HOST IDENTIFICATION HAS CHANGED! @
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
IT IS POSSIBLE THAT SOMEONE IS DOING SOMETHING NASTY!
Someone could be eavesdropping on you right now (man-in-the-middle attack)!
It is also possible that the RSA host key has just been changed.
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
@ WARNING: REMOTE HOST IDENTIFICATION HAS CHANGED! @
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
IT IS POSSIBLE THAT SOMEONE IS DOING SOMETHING NASTY!
Someone could be eavesdropping on you right now (man-in-the-middle attack)!
It is also possible that the RSA host key has just been changed.
To prevent this, you can backup the relevant files from the `/etc/ssh/` directory (see xref:table-ssh-configuration-configs-system[System-wide configuration files] for a complete list), and restore them whenever you reinstall the system.
Para evitar esto, usted puede hacer copia de seguridad de los archivos relevantes del directorio `/etc/ssh/` (vea en xref:table-ssh-configuration-configs-system[Archivos de configuración de todo el sistema] una lista completa) y recupérelos siempre que reinstale el sistema.
Requiring SSH for Remote Connections
Requerimientos de SSH para Conexiones Remotas
indexterm:[SSH protocol,insecure protocols]indexterm:[SSH protocol,requiring for remote login] For SSH to be truly effective, using insecure connection protocols should be prohibited. Otherwise, a user's password may be protected using SSH for one session, only to be captured later while logging in using Telnet. Some services to disable include [command]#telnet#, [command]#rsh#, [command]#rlogin#, and [command]#vsftpd#.
indexterm:[SSH protocol,insecure protocols]indexterm:[SSH protocol,requiring for remote login] Para que SSH sea verdaderamente efectivo la utilización de protocolos de conexión inseguros debería estar prohibida. De lo contrario una contraseña de usuario se puede proteger usando SSH para una sesión, solo para ser capturada más tarde al iniciar una sesión usando Telnet. Algunos servicios a deshabilitar son [command]#telnet#, [command]#rsh#, [command]#rlogin# y [command]#vsftpd#.
These services are not installed by default in {MAJOROS}. If required, to make sure these services are not running, type the following commands at a shell prompt:
Estos servicios no están instalados de modo predeterminado en {MAJOROS}. Si es necesario, para asegurarse de que estos servicios no están corriendo, teclee los siguientes comandos en el símbolo del sistema:
[command]#systemctl stop telnet.service#
[command]#systemctl stop rsh.service#
[command]#systemctl stop rlogin.service#
[command]#systemctl stop vsftpd.service#
[command]#systemctl stop telnet.service#
[command]#systemctl stop rsh.service#
[command]#systemctl stop rlogin.service#
[command]#systemctl stop vsftpd.service#
To disable running these services at startup, type:
Para deshabilitar que corran estos servicios en el arranque teclee:
[command]#systemctl disable telnet.service#
[command]#systemctl disable rsh.service#
[command]#systemctl disable rlogin.service#
[command]#systemctl disable vsftpd.service#
[command]#systemctl disable telnet.service#
[command]#systemctl disable rsh.service#
[command]#systemctl disable rlogin.service#
[command]#systemctl disable vsftpd.service#
Using Key-based Authentication
Utilizando Autenticación Basada en Clave
indexterm:[OpenSSH,using key-based authentication] To improve the system security even further, generate SSH key pairs and then enforce key-based authentication by disabling password authentication. To do so, create a drop-in configuration file, for example `/etc/ssh/sshd_config.d/01-local.conf`. Make sure it is lexicographically before the `50-redhat.conf` file, providing Fedora defaults. In a text editor such as [application]*vi* or [application]*nano* insert the [option]`PasswordAuthentication` option as follows:
indexterm:[OpenSSH,using key-based authentication] Para mejorar la seguridad del sistema aún más genere los pares de claves SSH y después fuerce la autenticación basada en clave deshabilitando la autenticación por contraseña. Para hacerlo, cree un archivo de configuración desplegable, por ejemplo `/etc/ssh/sshd_config.d/01-local.conf`. Asegúrese de que esté lexicográficamente antes del archivo `50-redhat.conf`, proporcionando los valores predeterminados de Fedora. En un editor de texto como [application]*vi* o [application]*nano* inserte la opción [option]`PasswordAuthentication` como sigue:
PasswordAuthentication no
PasswordAuthentication no
If you are working on a system other than a new default installation, check that [command]#PubkeyAuthentication no# has *not* been set in neither `/etc/ssh/sshd_config` nor any included file from drop-in directory. If connected remotely, not using console or out-of-band access, testing the key-based log in process before disabling password authentication is advised.
Si está trabajando en un sistema que no sea una nueva instalación predeterminada, compruebe que [command]#PubkeyAuthentication no# *no* ha sido establecida ni en `/etc/ssh/sshd_config` ni en ningún archivo incluido en el directorio desplegable. Si se conecta remotamente, no usando consola o acceso fuera de banda, pruebe el acceso basado en clave en ejecución antes de deshabilitar la autenticación por contraseña.
To be able to use [command]#ssh#, [command]#scp#, or [command]#sftp# to connect to the server from a client machine, generate an authorization key pair by following the steps below. Note that keys must be generated for each user separately.
Para ser capaz de utilizar [command]#ssh#, [command]#scp# o [command]#sftp# para conectarse al servidor desde una máquina cliente, genere un par de claves de autorización siguiendo los pasos de abajo. Tenga en cuenta que las claves se deben generar por cada usuario por separado.
{MAJOROSVER} uses SSH Protocol 2 and RSA keys by default (see xref:s2-ssh-versions[Protocol Versions] for more information).
{MAJOROSVER} utiliza SSH Protocol 2 y claves RSA de modo predeterminado (vea más información en see xref:s2-ssh-versions[Versiones del Protocolo]).
Do not generate key pairs as root
No genere los pares de claves como root
If you complete the steps as `root`, only `root` will be able to use the keys.
Si completa los pasos como `root`, solo `root` será capaz de usar las claves.
Backup your ~/.ssh/ directory
Haga copia de seguridad de su directorio ~/.ssh/
If you reinstall your system and want to keep previously generated key pairs, backup the `~/.ssh/` directory. After reinstalling, copy it back to your home directory. This process can be done for all users on your system, including `root`.
Si desea reinstalar su sistema y mantener los pares de claves generadas previamente, haga copia de seguridad de su directorio `~/.ssh/`. Después de reinstalar recupere la copia en su directorio home. Este proceso puede ser hecho por todos los usuarios de su sistema incluido `root`.
Generating Key Pairs
Generando los Pares de Claves
indexterm:[RSA keys,generating]indexterm:[OpenSSH,RSA keys,generating] To generate an RSA key pair for version 2 of the SSH protocol, follow these steps: indexterm:[OpenSSH,ssh-keygen,RSA]
indexterm:[RSA keys,generating]indexterm:[OpenSSH,RSA keys,generating] Para generar un par de claves RSA para la versión 2 del protocolo SSH, siga estos pasos: indexterm:[OpenSSH,ssh-keygen,RSA]
Generate an RSA key pair by typing the following at a shell prompt:
Generar un par de claves RSA tecleando lo siguiente en el símbolo del sistema:
~]${nbsp}ssh-keygen -t rsa
Generating public/private rsa key pair.
Enter file in which to save the key (/home/USER/.ssh/id_rsa):
~]${nbsp}ssh-keygen -t rsa
Generating public/private rsa key pair.
Enter file in which to save the key (/home/USER/.ssh/id_rsa):
Press kbd:[Enter] to confirm the default location, `~/.ssh/id_rsa`, for the newly created key.
Pulse kbd:[Enter] para confirmar la localización predeterminada, `~/.ssh/id_rsa`, para la clave recientemente creada.
Enter a passphrase, and confirm it by entering it again when prompted to do so. For security reasons, avoid using the same password as you use to log in to your account.
Introduzca una frase de paso y confírmela introduciéndola otra vez cuando se le pida. Por razones de seguridad evite usar la misma contraseña que utiliza para acceder a su cuenta.
After this, you will be presented with a message similar to this:
Después de esto se le presentará un mensaje similar a este:
Your identification has been saved in /home/USER/.ssh/id_rsa.
Your public key has been saved in /home/USER/.ssh/id_rsa.pub.
The key fingerprint is:
SHA256:y6f0DGlHe28YWotEypnhfk3WLYQ5TgaQwoSlOFwmmm0 USER@penguin.example.com
The key's randomart image is:
+--[ RSA 2048]----+
| E. |
| . . |
| o . |
| . .|
| S . . |
| + o o ..|
| * * +oo|
| O +..=|
| o* o.|
+-----------------+
Your identification has been saved in /home/USER/.ssh/id_rsa.
Your public key has been saved in /home/USER/.ssh/id_rsa.pub.
The key fingerprint is:
SHA256:y6f0DGlHe28YWotEypnhfk3WLYQ5TgaQwoSlOFwmmm0 USER@penguin.example.com
The key's randomart image is:
+--[ RSA 2048]----+
| E. |
| . . |
| o . |
| . .|
| S . . |
| + o o ..|
| * * +oo|
| O +..=|
| o* o.|
+-----------------+
By default, the permissions of the `~/.ssh/` directory are set to `rwx------` or `700` expressed in octal notation. This is to ensure that only the _USER_ can view the contents. If required, this can be confirmed with the following command:
De modo predeterminado los permisos del directorio `~/.ssh/` están establecidos a `rwx------` o `700` expresado en anotación octal. Esto es para asegurar que solo el _USER_ puede ver los contenidos. Si se requiere esto se puede confirmar con el siguiente comando:

Loading…

User avatar None

Automatically translated
If you are working on a system other than a new default installation, check that [command]#PubkeyAuthentication no# has *not* been set in neither `/etc/ssh/sshd_config` nor any included file from drop-in directory. If connected remotely, not using console or out-of-band access, testing the key-based log in process before disabling password authentication is advised.
Si está trabajando en un sistema que no sea una nueva instalación predeterminada, compruebe que [command]#PubkeyAuthentication no# *no* ha sido establecida ni en `/etc/ssh/sshd_config` ni en ningún archivo incluido en el directorio desplegable. Si se conecta remotamente, no usando consola o acceso fuera de banda, pruebe el acceso basado en clave en ejecución antes de deshabilitar la autenticación por contraseña.
6 months ago
User avatar None

String added in the repository
If you are working on a system other than a new default installation, check that [command]#PubkeyAuthentication no# has *not* been set in neither `/etc/ssh/sshd_config` nor any included file from drop-in directory. If connected remotely, not using console or out-of-band access, testing the key-based log in process before disabling password authentication is advised.
 
6 months ago
Browse all string changes

Things to check

Consecutive duplicated words

Text contains the same word twice in a row: no

Reset

Glossary

English Spanish
No related strings found in the glossary.

17995362 String information

Source string description
type: Plain text
Labels
Automatically translated
Source string location
./pages/infrastructure-services/OpenSSH.adoc:264
String age
6 months ago
Last updated
6 months ago
Source string age
a year ago
Translation file
po/es/rawhide/pages/infrastructure-services/OpenSSH.po, string 94