Olá! No momento, esta página ainda está sendo desenvolvida ou traduzida. Para obter as informações mais recentes, acesse a documentação em inglês.

Explorar por produto

Enterprise Server 2.15
"Português do Brasil (Portuguese)
Versão do artigo: Enterprise Server 2.15
GitHub.com Enterprise Server 2.18 Enterprise Server 2.17 Enterprise Server 2.16 Enterprise Server 2.15

Esta versão do GitHub Enterprise será descontinuada em Esta versão do GitHub Enterprise foi descontinuada em 2019-10-16. No patch releases will be made, even for critical security issues. For better performance, improved security, and new features, upgrade to the latest version of GitHub Enterprise. For help with the upgrade, contact GitHub Enterprise support.

Informar ao Git sobre a chave de assinatura

Para assinar commits localmente, é preciso informar ao Git que há uma chave GPG ou X.509 que você deseja usar.

Informar ao Git sobre a chave GPG

Se você estiver usando uma chave GPG que corresponda à identidade do committer (autor do commit) e ao endereço de e-mail associado à conta do GitHub Enterprise, você poderá começar a assinar commits e tags.

Se você não tiver uma chave GPG que corresponda à identidade do committer, precisará associar um e-mail a uma chave existente. Para obter mais informações, consulte "Associar e-mail à chave GPG".

Se você tiver várias chaves GPG, precisará informar ao Git qual deve ser usada.

  1. Abra Terminal (Terminal)Terminal (Terminal)Git Basho terminal.

  2. Use the gpg --list-secret-keys --keyid-format LONG command to list GPG keys for which you have both a public and private key. A private key is required for signing commits or tags.

$ gpg --list-secret-keys --keyid-format LONG

Note: Some GPG installations on Linux may require you to use gpg2 --list-keys --keyid-format LONG to view a list of your existing keys instead. In this case you will also need to configure Git to use gpg2 by running git config --global gpg.program gpg2.

1. From the list of GPG keys, copy the GPG key ID you'd like to use. In this example, the GPG key ID is `3AA5C34371567BD2`: 
$ gpg --list-secret-keys --keyid-format LONG
  /Users/hubot/.gnupg/secring.gpg
  ------------------------------------
  sec   4096R/3AA5C34371567BD2 2016-03-10 [expires: 2017-03-10]
  uid                          Hubot 
  ssb   4096R/42B317FD4BA89E7A 2016-03-10

  1. To set your GPG signing key in Git, paste the text below, substituting in the GPG key ID you'd like to use. In this example, the GPG key ID is 3AA5C34371567BD2:

    $ git config --global user.signingkey 3AA5C34371567BD2

  2. Se você não estiver usando o conjunto de GPG, cole o texto abaixo para adicionar a chave GPG ao seu perfil de bash:

    $ test -r ~/.bash_profile && echo 'export GPG_TTY=$(tty)' >> ~/.bash_profile
$ echo 'export GPG_TTY=$(tty)' >> ~/.profile

    Observação: se você não tiver .bash_profile, este comando adicionará sua chave GPG a .profile.

Telling Git about your X.509 key

You can use smimesign to sign commits and tags using S/MIME instead of GPG.

Note: S/MIME signature verification is available in Git 2.19 or later. To update your version of Git, see the Git website.

  1. Install smimesign. 1. Abra Terminal (Terminal)Terminal (Terminal)Git Basho terminal.

  2. Configure Git to use S/MIME to sign commits and tags. In Git 2.19 or later, use the git config gpg.x509.program and git config gpg.format commands:

  • To use S/MIME to sign for all repositories: shell $ git config --global gpg.x509.program smimesign $ git config --global gpg.format x509

  • To use S/MIME to sign for a single repository: shell $ cd /path/to/my/repository$ git config --local gpg.x509.program smimesign $ git config --local gpg.format x509 In Git 2.18 or earlier, use the 

    `git config gpg.program` command:

  • To use S/MIME to sign for all repositories: shell $ git config --global gpg.program smimesign

  • To use S/MIME to sign for a single repository: shell $ cd /path/to/my/repository$ git config --local gpg.program smimesign If you're using an X.509 key that matches your committer identity, you can begin signing commits and tags.

  1. If you're not using an X.509 key that matches your commiter identity, list X.509 keys for which you have both a certificate and private key using the smimesign --list-keys command. shell $ smimesign --list-keys

  2. From the list of X.509 keys, copy the certificate ID of the X.509 key you'd like to use. In this example, the certificate ID is 0ff455a2708394633e4bb2f88002e3cd80cbd76f: shell $ smimesign --list-keys ID: 0ff455a2708394633e4bb2f88002e3cd80cbd76f S/N: a2dfa7e8c9c4d1616f1009c988bb70f Algorithm: SHA256-RSA Validity: 2017-11-22 00:00:00 +0000 UTC - 2020-11-22 12:00:00 +0000 UTC Issuer: CN=DigiCert SHA2 Assured ID CA,OU=www.digicert.com,O=DigiCert Inc,C=US Subject: CN=Octocat,O=GitHub\, Inc.,L=San Francisco,ST=California,C=US Emails: octocat@github.com

  3. To set your X.509 signing key in Git, paste the text below, substituting in the certificate ID you copied earlier.

  • To use your X.509 key to sign for all repositories: shell $ git config --global user.signingkey 0ff455a2708394633e4bb2f88002e3cd80cbd76f

  • To use your X.509 key to sign for a single repository: shell $ cd /path/to/my/repository$ git config --local user.signingkey 0ff455a2708394633e4bb2f88002e3cd80cbd76f

Informar ao Git sobre a chave GPG

Se você estiver usando uma chave GPG que corresponda à identidade do committer (autor do commit) e ao endereço de e-mail associado à conta do GitHub Enterprise, você poderá começar a assinar commits e tags.

Se você não tiver uma chave GPG que corresponda à identidade do committer, precisará associar um e-mail a uma chave existente. Para obter mais informações, consulte "Associar e-mail à chave GPG".

Se você tiver várias chaves GPG, precisará informar ao Git qual deve ser usada.

  1. Abra Terminal (Terminal)Terminal (Terminal)Git Basho terminal.

  2. Use the gpg --list-secret-keys --keyid-format LONG command to list GPG keys for which you have both a public and private key. A private key is required for signing commits or tags.

$ gpg --list-secret-keys --keyid-format LONG

Note: Some GPG installations on Linux may require you to use gpg2 --list-keys --keyid-format LONG to view a list of your existing keys instead. In this case you will also need to configure Git to use gpg2 by running git config --global gpg.program gpg2.

1. From the list of GPG keys, copy the GPG key ID you'd like to use. In this example, the GPG key ID is `3AA5C34371567BD2`: 
$ gpg --list-secret-keys --keyid-format LONG
  /Users/hubot/.gnupg/secring.gpg
  ------------------------------------
  sec   4096R/3AA5C34371567BD2 2016-03-10 [expires: 2017-03-10]
  uid                          Hubot 
  ssb   4096R/42B317FD4BA89E7A 2016-03-10

  1. To set your GPG signing key in Git, paste the text below, substituting in the GPG key ID you'd like to use. In this example, the GPG key ID is 3AA5C34371567BD2:

    $ git config --global user.signingkey 3AA5C34371567BD2

Telling Git about your X.509 key

You can use smimesign to sign commits and tags using S/MIME instead of GPG.

Note: S/MIME signature verification is available in Git 2.19 or later. To update your version of Git, see the Git website.

  1. Install smimesign. 1. Abra Terminal (Terminal)Terminal (Terminal)Git Basho terminal.

  2. Configure Git to use S/MIME to sign commits and tags. In Git 2.19 or later, use the git config gpg.x509.program and git config gpg.format commands:

  • To use S/MIME to sign for all repositories: shell $ git config --global gpg.x509.program smimesign $ git config --global gpg.format x509

  • To use S/MIME to sign for a single repository: shell $ cd /path/to/my/repository$ git config --local gpg.x509.program smimesign $ git config --local gpg.format x509 In Git 2.18 or earlier, use the 

    `git config gpg.program` command:

  • To use S/MIME to sign for all repositories: shell $ git config --global gpg.program smimesign

  • To use S/MIME to sign for a single repository: shell $ cd /path/to/my/repository$ git config --local gpg.program smimesign If you're using an X.509 key that matches your committer identity, you can begin signing commits and tags.

  1. If you're not using an X.509 key that matches your commiter identity, list X.509 keys for which you have both a certificate and private key using the smimesign --list-keys command. shell $ smimesign --list-keys

  2. From the list of X.509 keys, copy the certificate ID of the X.509 key you'd like to use. In this example, the certificate ID is 0ff455a2708394633e4bb2f88002e3cd80cbd76f: shell $ smimesign --list-keys ID: 0ff455a2708394633e4bb2f88002e3cd80cbd76f S/N: a2dfa7e8c9c4d1616f1009c988bb70f Algorithm: SHA256-RSA Validity: 2017-11-22 00:00:00 +0000 UTC - 2020-11-22 12:00:00 +0000 UTC Issuer: CN=DigiCert SHA2 Assured ID CA,OU=www.digicert.com,O=DigiCert Inc,C=US Subject: CN=Octocat,O=GitHub\, Inc.,L=San Francisco,ST=California,C=US Emails: octocat@github.com

  3. To set your X.509 signing key in Git, paste the text below, substituting in the certificate ID you copied earlier.

  • To use your X.509 key to sign for all repositories: shell $ git config --global user.signingkey 0ff455a2708394633e4bb2f88002e3cd80cbd76f

  • To use your X.509 key to sign for a single repository: shell $ cd /path/to/my/repository$ git config --local user.signingkey 0ff455a2708394633e4bb2f88002e3cd80cbd76f

Observação: as chaves X.509 não são compatíveis com Linux. Embora seja possível configurar gpgsm para fornecer serviços de assinatura e criptografia, não há suporte para isso no GitHub Enterprise. Para obter mais informações, consulte o tópico gpgsm na documentação do GnuPG.

Informar ao Git sobre a chave GPG

Se você estiver usando uma chave GPG que corresponda à identidade do committer (autor do commit) e ao endereço de e-mail associado à conta do GitHub Enterprise, você poderá começar a assinar commits e tags.

Se você não tiver uma chave GPG que corresponda à identidade do committer, precisará associar um e-mail a uma chave existente. Para obter mais informações, consulte "Associar e-mail à chave GPG".

Se você tiver várias chaves GPG, precisará informar ao Git qual deve ser usada.

  1. Abra Terminal (Terminal)Terminal (Terminal)Git Basho terminal.

  2. Use the gpg --list-secret-keys --keyid-format LONG command to list GPG keys for which you have both a public and private key. A private key is required for signing commits or tags.

$ gpg --list-secret-keys --keyid-format LONG

Note: Some GPG installations on Linux may require you to use gpg2 --list-keys --keyid-format LONG to view a list of your existing keys instead. In this case you will also need to configure Git to use gpg2 by running git config --global gpg.program gpg2.

1. From the list of GPG keys, copy the GPG key ID you'd like to use. In this example, the GPG key ID is `3AA5C34371567BD2`: 
$ gpg --list-secret-keys --keyid-format LONG
  /Users/hubot/.gnupg/secring.gpg
  ------------------------------------
  sec   4096R/3AA5C34371567BD2 2016-03-10 [expires: 2017-03-10]
  uid                          Hubot 
  ssb   4096R/42B317FD4BA89E7A 2016-03-10

  1. To set your GPG signing key in Git, paste the text below, substituting in the GPG key ID you'd like to use. In this example, the GPG key ID is 3AA5C34371567BD2:

    $ git config --global user.signingkey 3AA5C34371567BD2

  2. Para adicionar a chave GPG ao seu perfil de bash, cole o texto abaixo:

    $ test -r ~/.bash_profile && echo 'export GPG_TTY=$(tty)' >> ~/.bash_profile
$ echo 'export GPG_TTY=$(tty)' >> ~/.profile

    Observação: se você não tiver .bash_profile, este comando adicionará sua chave GPG a .profile.

Leia mais

Pergunte a uma pessoa

Não consegue encontrar o que procura?

Entrar em contato

Produto

Plataforma

Suporte

Empresa