Skip to content

Commit 6a18af5

Browse files
OctomergerOctomerger
authored
Merge pull request #21747 from github/repo-sync
repo sync
2 parents 8d53746 + 0260167 commit 6a18af5

File tree

156 files changed

+277
-4611
lines changed

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

156 files changed

+277
-4611
lines changed

‎translations/es-ES/content/authentication/connecting-to-github-with-ssh/about-ssh.md‎

Lines changed: 18 additions & 16 deletions
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
---
2-
title: About SSH
3-
intro: 'Using the SSH protocol, you can connect and authenticate to remote servers and services. With SSH keys, you can connect to {% data variables.product.product_name %} without supplying your username and {% data variables.product.pat_generic %} at each visit.{% ifversion ssh-commit-verification %} You can also use an SSH key to sign commits.{% endif %}'
2+
title: Acerca de SSH
3+
intro: 'Usando el protocolo SSH, te puedes conectar y autenticar con servicios y servidores remotos. Con las claves SSH puedes conectarte a {% data variables.product.product_name %} sin necesidad de proporcionar el nombre de usuario y el {% data variables.product.pat_generic %} en cada visita.{% ifversion ssh-commit-verification %} También puedes usar una clave SSH para firmar confirmaciones.{% endif %}'
44
redirect_from:
55
- /articles/about-ssh
66
- /github/authenticating-to-github/about-ssh
@@ -12,27 +12,29 @@ versions:
1212
ghec: '*'
1313
topics:
1414
- SSH
15+
ms.openlocfilehash: 51a72821217e5d47092ed77e923b38f4cf248010
16+
ms.sourcegitcommit: a0ad3bfe2a99c3092e76ca9b3d476cf30988ca55
17+
ms.translationtype: HT
18+
ms.contentlocale: es-ES
19+
ms.lasthandoff: 10/28/2022
20+
ms.locfileid: '148118983'
1521
---
22+
{% data reusables.ssh.about-ssh %} Para obtener más información sobre SSH, consulta [Secure Shell](https://en.wikipedia.org/wiki/Secure_Shell) en Wikipedia.
1623

17-
{% data reusables.ssh.about-ssh %} For more information about SSH, see [Secure Shell](https://en.wikipedia.org/wiki/Secure_Shell) on Wikipedia.
24+
Cuando configures SSH, necesitarás generar una clave SSH privada nueva y agregarla al agente SSH. También debes agregar la clave SSH pública a tu cuenta en {% data variables.product.product_name %} antes de utilizarla para autenticarte{% ifversion ssh-commit-verification %} o firmar confirmaciones{% endif %}. Para obtener más información, consulta "[Generación de una nueva clave SSH e incorporación al agente ssh](/authentication/connecting-to-github-with-ssh/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent)"{% ifversion ssh-commit-verification %}, {% else %} e{% endif %} "[Incorporación de una nueva clave SSH a la cuenta de {% data variables.product.prodname_dotcom %}](/authentication/connecting-to-github-with-ssh/adding-a-new-ssh-key-to-your-github-account){% ifversion ssh-commit-verification %}" y "[Acerca de la verificación de firma de confirmación](/articles/about-commit-signature-verification){% endif %}".
1825

19-
When you set up SSH, you will need to generate a new private SSH key and add it to the SSH agent. You must also add the public SSH key to your account on {% data variables.product.product_name %} before you use the key to authenticate{% ifversion ssh-commit-verification %} or sign commits{% endif %}. For more information, see "[Generating a new SSH key and adding it to the ssh-agent](/authentication/connecting-to-github-with-ssh/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent)"{% ifversion ssh-commit-verification %}, {% else %} and{% endif %} "[Adding a new SSH key to your {% data variables.product.prodname_dotcom %} account](/authentication/connecting-to-github-with-ssh/adding-a-new-ssh-key-to-your-github-account){% ifversion ssh-commit-verification %}" and "[About commit signature verification](/articles/about-commit-signature-verification){% endif %}."
26+
Puedes asegurar tu llave SSH aún más si utilizas una llave de seguridad de hardware, la cual requiere que esta última se conecte físicamente a tu computadora cuando se utilice el par de llaves para autenticarte con SSH. También puedes asegurar tu llave SSH si la agregas al ssh-agent y utiliza una contraseña. Para obtener más información, consulta "[Trabajo con frases de contraseña de clave de SSH](/authentication/connecting-to-github-with-ssh/working-with-ssh-key-passphrases)".
2027

21-
You can further secure your SSH key by using a hardware security key, which requires the physical hardware security key to be attached to your computer when the key pair is used to authenticate with SSH. You can also secure your SSH key by adding your key to the ssh-agent and using a passphrase. For more information, see "[Working with SSH key passphrases](/authentication/connecting-to-github-with-ssh/working-with-ssh-key-passphrases)."
28+
{% ifversion fpt or ghec %}Para usar la clave SSH con un repositorio propiedad de una organización que usa el inicio de sesión único de SAML, debes autorizar la clave. Para obtener más información, consulta "[Autorización de una clave SSH para usarla con el inicio de sesión único de SAML](/enterprise-cloud@latest/authentication/authenticating-with-saml-single-sign-on/authorizing-an-ssh-key-for-use-with-saml-single-sign-on){% ifversion fpt %}" en la documentación de {% data variables.product.prodname_ghe_cloud %}.{% else %}".{% endif %}{% endif %}
2229

23-
{% ifversion fpt or ghec %}To use your SSH key with a repository owned by an organization that uses SAML single sign-on, you must authorize the key. For more information, see "[Authorizing an SSH key for use with SAML single sign-on](/enterprise-cloud@latest/authentication/authenticating-with-saml-single-sign-on/authorizing-an-ssh-key-for-use-with-saml-single-sign-on){% ifversion fpt %}" in the {% data variables.product.prodname_ghe_cloud %} documentation.{% else %}."{% endif %}{% endif %}
30+
Para mantener la seguridad de cuenta, puedes revisar tu lista de llaves SSH frecuentemente y retirar cualquier llave que sea inválida o que se haya puesto en riesgo. Para obtener más información, consulta "[Revisión de las claves SSH](/github/authenticating-to-github/reviewing-your-ssh-keys)".
2431

25-
To maintain account security, you can regularly review your SSH keys list and revoke any keys that are invalid or have been compromised. For more information, see "[Reviewing your SSH keys](/github/authenticating-to-github/reviewing-your-ssh-keys)."
26-
27-
{% ifversion fpt or ghec %}
28-
If you haven't used your SSH key for a year, then {% data variables.product.prodname_dotcom %} will automatically delete your inactive SSH key as a security precaution. For more information, see "[Deleted or missing SSH keys](/articles/deleted-or-missing-ssh-keys)."
32+
{% ifversion fpt or ghec %} Si no has usado tu clave SSH por un año, entonces {% data variables.product.prodname_dotcom %} automáticamente eliminará tu clave SSH inactiva, como medida de seguridad. Para obtener más información, consulta "[Claves SSH eliminadas o ausentes](/articles/deleted-or-missing-ssh-keys)".
2933
{% endif %}
3034

31-
{% ifversion fpt %}
32-
Organizations that use {% data variables.product.prodname_ghe_cloud %} can provide SSH certificates, which members can use to access that organization's repositories without adding the certificate to their account on {% data variables.product.product_name %}. If you're using an SSH certificate, you cannot use the certificate to access forks of the organization's repositories, if the fork is owned by your personal account. For more information, see "[About SSH certificate authorities](/enterprise-cloud@latest/organizations/managing-git-access-to-your-organizations-repositories/about-ssh-certificate-authorities)" in the {% data variables.product.prodname_ghe_cloud %} documentation.
33-
{% else ghec or ghes or ghae %}
34-
If you're a member of an organization that provides SSH certificates, you can use your certificate to access that organization's repositories without adding the certificate to your account on {% data variables.product.product_name %}. You cannot use your certificate to access forks of the organization's repositories, if the forks is owned by your personal account. For more information, see "[About SSH certificate authorities](/organizations/managing-git-access-to-your-organizations-repositories/about-ssh-certificate-authorities)."
35+
{% ifversion fpt %} Las organizaciones que usan {% data variables.product.prodname_ghe_cloud %} pueden proporcionar certificados SSH, que los miembros pueden usar para acceder a los repositorios de estas sin tener que agregar el certificado a su cuenta de {% data variables.product.product_name %}. Si usas un certificado SSH, no puedes acceder con él a bifurcaciones de los repositorios de la organización, si la bifurcación es propiedad de tu cuenta personal. Para más información, consulta "[Acerca de las entidades de certificación de SSH](/enterprise-cloud@latest/organizations/managing-git-access-to-your-organizations-repositories/about-ssh-certificate-authorities) en la documentación de {% data variables.product.prodname_ghe_cloud %}.
36+
{% else ghec or ghes or ghae %} Si eres miembro de una organización que proporciona certificados SSH, puedes usar tu certificado para acceder a los repositorios de esa organización sin agregar el certificado a tu cuenta de {% data variables.product.product_name %}. No puedes utilizar tu certificado para acceder a bifurcaciones de los repositorios de la organización, si estas pertenecen a tu cuenta personal. Para más información, vea "[Acerca de las entidades de certificación de SSH](/organizations/managing-git-access-to-your-organizations-repositories/about-ssh-certificate-authorities)".
3537
{% endif %}
36-
## Further reading
38+
## Información adicional
3739

38-
- "[Troubleshooting SSH](/articles/troubleshooting-ssh)"
40+
- "[Solucionar problemas de SSH](/articles/troubleshooting-ssh)"

‎translations/es-ES/content/authentication/managing-commit-signature-verification/telling-git-about-your-signing-key.md‎

Lines changed: 35 additions & 48 deletions
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
---
2-
title: Telling Git about your signing key
3-
intro: 'To sign commits locally, you need to inform Git that there''s a GPG{% ifversion ssh-commit-verification %}, SSH,{% endif %} or X.509 key you''d like to use.'
2+
title: Informarle a Git acerca de tu clave de firma
3+
intro: 'Para firmar las confirmaciones localmente, necesitas informar a Git que hay una clave de GPG{% ifversion ssh-commit-verification %}, SSH,{% endif %} o X.509 que quieres utilizar.'
44
redirect_from:
55
- /articles/telling-git-about-your-gpg-key
66
- /articles/telling-git-about-your-signing-key
@@ -15,38 +15,39 @@ topics:
1515
- Identity
1616
- Access management
1717
shortTitle: Tell Git your signing key
18+
ms.openlocfilehash: e78306bb1519f2b7f51ab6bc039bff0b982e48cf
19+
ms.sourcegitcommit: a0ad3bfe2a99c3092e76ca9b3d476cf30988ca55
20+
ms.translationtype: HT
21+
ms.contentlocale: es-ES
22+
ms.lasthandoff: 10/28/2022
23+
ms.locfileid: '148118999'
1824
---
1925
{% mac %}
2026

21-
## Telling Git about your GPG key
27+
## Informarle a Git acerca de tu llave GPG
2228

23-
If you're using a GPG key that matches your committer identity and your verified email address associated with your account on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.location.product_location %}{% endif %}, then you can begin signing commits and signing tags.
29+
Si estás utilizando una clave GPG que coincide con tu identidad de confirmante y tu dirección de correo electrónico verificada asociada a tu cuenta de {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.location.product_location %}{% endif %}, entonces puedes comenzar a firmar confirmaciones y etiquetas.
2430

2531
{% note %}
2632

27-
If you don't have a GPG key that matches your committer identity, you need to associate an email with an existing key. For more information, see "[Associating an email with your GPG key](/articles/associating-an-email-with-your-gpg-key)".
33+
Si no tienes una llave GPG que coincida con la identidad de la persona que confirma el cambio, debes asociar un correo electrónico a una llave existente. Para más información, vea "[Asociación de un correo electrónico con la clave de GPG](/articles/associating-an-email-with-your-gpg-key)".
2834

2935
{% endnote %}
3036

31-
If you have multiple GPG keys, you need to tell Git which one to use.
37+
Si tienes múltiples llaves GPG, le debes decir a Git cuál utilizar.
3238

33-
{% data reusables.command_line.open_the_multi_os_terminal %}
34-
{% data reusables.gpg.configure-gpg-signing %}
35-
{% data reusables.gpg.list-keys-with-note %}
36-
{% data reusables.gpg.copy-gpg-key-id %}
37-
{% data reusables.gpg.paste-gpg-key-id %}
38-
{% data reusables.gpg.set-auto-sign %}
39-
1. If you aren't using the GPG suite, run the following command in the `zsh` shell to add the GPG key to your `.zshrc` file, if it exists, or your `.zprofile` file:
39+
{% data reusables.command_line.open_the_multi_os_terminal %} {% data reusables.gpg.configure-gpg-signing %} {% data reusables.gpg.list-keys-with-note %} {% data reusables.gpg.copy-gpg-key-id %} {% data reusables.gpg.paste-gpg-key-id %} {% data reusables.gpg.set-auto-sign %}
40+
1. Si no usa el conjunto de GPG, ejecute el comando siguiente en el shell de `zsh` para agregar la clave de GPG al archivo `.zshrc`, si existe, o bien al archivo `.zprofile`:
4041
```shell
4142
$ if [ -r ~/.zshrc ]; then echo 'export GPG_TTY=$(tty)' >> ~/.zshrc; \
4243
else echo 'export GPG_TTY=$(tty)' >> ~/.zprofile; fi
4344
```
44-
Alternatively, if you use the `bash` shell, run this command:
45+
Como alternativa, si usa el shell de `bash`, ejecute este comando:
4546
```shell
4647
$ if [ -r ~/.bash_profile ]; then echo 'export GPG_TTY=$(tty)' >> ~/.bash_profile; \
4748
else echo 'export GPG_TTY=$(tty)' >> ~/.profile; fi
4849
```
49-
1. Optionally, to prompt you to enter a PIN or passphrase when required, install `pinentry-mac`. For example, using [Homebrew](https://brew.sh/):
50+
1. Opcionalmente, para que se le solicite que escriba un PIN o una frase de contraseña cuando sea necesario, instale `pinentry-mac`. Por ejemplo, con [Homebrew](https://brew.sh/):
5051
```shell
5152
$ brew install pinentry-mac
5253
$ echo "pinentry-program $(which pinentry-mac)" >> ~/.gnupg/gpg-agent.conf
@@ -57,70 +58,56 @@ If you have multiple GPG keys, you need to tell Git which one to use.
5758

5859
{% windows %}
5960

60-
## Telling Git about your GPG key
61+
## Informarle a Git acerca de tu llave GPG
6162

62-
If you're using a GPG key that matches your committer identity and your verified email address associated with your account on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.location.product_location %}{% endif %}, then you can begin signing commits and signing tags.
63+
Si estás utilizando una clave GPG que coincide con tu identidad de confirmante y tu dirección de correo electrónico verificada asociada a tu cuenta de {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.location.product_location %}{% endif %}, entonces puedes comenzar a firmar confirmaciones y etiquetas.
6364

6465
{% note %}
6566

66-
If you don't have a GPG key that matches your committer identity, you need to associate an email with an existing key. For more information, see "[Associating an email with your GPG key](/articles/associating-an-email-with-your-gpg-key)".
67+
Si no tienes una llave GPG que coincida con la identidad de la persona que confirma el cambio, debes asociar un correo electrónico a una llave existente. Para más información, vea "[Asociación de un correo electrónico con la clave de GPG](/articles/associating-an-email-with-your-gpg-key)".
6768

6869
{% endnote %}
6970

70-
If you have multiple GPG keys, you need to tell Git which one to use.
71+
Si tienes múltiples llaves GPG, le debes decir a Git cuál utilizar.
7172

72-
{% data reusables.command_line.open_the_multi_os_terminal %}
73-
{% data reusables.gpg.configure-gpg-signing %}
74-
{% data reusables.gpg.list-keys-with-note %}
75-
{% data reusables.gpg.copy-gpg-key-id %}
76-
{% data reusables.gpg.paste-gpg-key-id %}
77-
{% data reusables.gpg.set-auto-sign %}
73+
{% data reusables.command_line.open_the_multi_os_terminal %} {% data reusables.gpg.configure-gpg-signing %} {% data reusables.gpg.list-keys-with-note %} {% data reusables.gpg.copy-gpg-key-id %} {% data reusables.gpg.paste-gpg-key-id %} {% data reusables.gpg.set-auto-sign %}
7874

7975
{% endwindows %}
8076

8177
{% linux %}
8278

83-
## Telling Git about your GPG key
79+
## Informarle a Git acerca de tu llave GPG
8480

85-
If you're using a GPG key that matches your committer identity and your verified email address associated with your account on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.location.product_location %}{% endif %}, then you can begin signing commits and signing tags.
81+
Si estás utilizando una clave GPG que coincide con tu identidad de confirmante y tu dirección de correo electrónico verificada asociada a tu cuenta de {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.location.product_location %}{% endif %}, entonces puedes comenzar a firmar confirmaciones y etiquetas.
8682

8783
{% note %}
8884

89-
If you don't have a GPG key that matches your committer identity, you need to associate an email with an existing key. For more information, see "[Associating an email with your GPG key](/articles/associating-an-email-with-your-gpg-key)".
85+
Si no tienes una llave GPG que coincida con la identidad de la persona que confirma el cambio, debes asociar un correo electrónico a una llave existente. Para más información, vea "[Asociación de un correo electrónico con la clave de GPG](/articles/associating-an-email-with-your-gpg-key)".
9086

9187
{% endnote %}
9288

93-
If you have multiple GPG keys, you need to tell Git which one to use.
89+
Si tienes múltiples llaves GPG, le debes decir a Git cuál utilizar.
9490

95-
{% data reusables.command_line.open_the_multi_os_terminal %}
96-
{% data reusables.gpg.configure-gpg-signing %}
97-
{% data reusables.gpg.list-keys-with-note %}
98-
{% data reusables.gpg.copy-gpg-key-id %}
99-
{% data reusables.gpg.paste-gpg-key-id %}
100-
{% data reusables.gpg.set-auto-sign %}
101-
1. To add your GPG key to your `.bashrc` startup file, run the following command:
91+
{% data reusables.command_line.open_the_multi_os_terminal %} {% data reusables.gpg.configure-gpg-signing %} {% data reusables.gpg.list-keys-with-note %} {% data reusables.gpg.copy-gpg-key-id %} {% data reusables.gpg.paste-gpg-key-id %} {% data reusables.gpg.set-auto-sign %}
92+
1. Para agregar la clave de GPG al archivo de inicio de `.bashrc`, ejecute el comando siguiente:
10293
```bash
10394
$ [ -f ~/.bashrc ] && echo 'export GPG_TTY=$(tty)' >> ~/.bashrc
10495
```
105-
{% endlinux %}
106-
{% ifversion ssh-commit-verification %}
96+
{% endlinux %} {% ifversion ssh-commit-verification %}
10797

108-
## Telling Git about your SSH key
98+
## Indicación a Git acerca de tu clave SSH
10999

110-
You can use an existing SSH key to sign commits and tags, or generate a new one specifically for signing. For more information, see "[Generating a new SSH key and adding it to the ssh-agent](/github/authenticating-to-github/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent)."
100+
Puedes usar una clave SSH existente para firmar confirmaciones y etiquetas, o generar una nueva específicamente para firmar. Para obtener más información, consulta "[Generación de una nueva clave SSH y adición a ssh-agent](/github/authenticating-to-github/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent)".
111101

112102
{% data reusables.gpg.ssh-git-version %}
113103

114-
{% data reusables.command_line.open_the_multi_os_terminal %}
115-
{% data reusables.gpg.configure-ssh-signing %}
116-
{% data reusables.gpg.copy-ssh-public-key %}
117-
{% data reusables.gpg.paste-ssh-public-key %}
104+
{% data reusables.command_line.open_the_multi_os_terminal %} {% data reusables.gpg.configure-ssh-signing %} {% data reusables.gpg.copy-ssh-public-key %} {% data reusables.gpg.paste-ssh-public-key %}
118105

119106
{% endif %}
120107

121108
{% data reusables.gpg.x-509-key %}
122-
## Further reading
109+
## Información adicional
123110

124-
- "[Adding a new SSH key to your GitHub account](/authentication/connecting-to-github-with-ssh/adding-a-new-ssh-key-to-your-github-account)."
125-
- "[Signing commits](/articles/signing-commits)"
126-
- "[Signing tags](/articles/signing-tags)"
111+
- "[incorporación de una clave SSH nueva a tu cuenta de GitHub](/authentication/connecting-to-github-with-ssh/adding-a-new-ssh-key-to-your-github-account)".
112+
- "[Firma de confirmaciones](/articles/signing-commits)"
113+
- "[Firma de etiquetas](/articles/signing-tags)"

0 commit comments

Comments
 (0)