"ERROR exec: "gpg": executable file not found in %PATH%" - keybase pgp select

Abierto
  • ¿Algo no está bien?
#4,275 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
4/5
Tiempo estimado
3-5 días
Aptitud para principiantes
20/100
Tipo de issue
Error
Claridad
Necesita aclaración
Estado de actividad
Estancado
Área
cryptography

Línea de trabajo

Comienza con el punto de entrada keybase pgp select y reproduce el comando de Windows con GPG4WIN instalado mientras gpg no esté disponible en %PATH%. Comprueba el uso documentado de la consulta de claves o de la ruta del archivo y considera resuelto el issue cuando la selección de claves funcione sin los errores reportados del ejecutable o del análisis de argumentos.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

Tried to import my public key, but it showed an error.

Keybase Import PGP Public Key

You are selecting a PGP key from your local GnuPG keychain, and
will publish a statement signed with this key to make it part of
your Keybase.io identity.

Note that GnuPG will prompt you to perform this signature.

You can also import the secret key to *local*, *encrypted* Keybase
keyring, enabling decryption and signing with the Keybase client.
To do that, use "--import" flag.

Learn more: keybase pgp help select

- ERROR exec: "gpg": executable file not found in %PATH%

By the way, it's OpenPGP now, and since I used Thunderbird to generate the key pair(which has had OpenPGP built in for several years now), would the cmd have to be on one of the Thunderbird folders? Or would my public key have to be in that folder?

Is there a specific folder that I have to place my public key file in?

And I just installed GPG4WIN again, would I need to change the cmd to one of the GPG4WIN directories?

Also when it shows

Note that GnuPG will prompt you to perform this signature.

what does it mean by "perform" ?

Thank you, Shalom.

my log id: e111096b20c576addf5c691c

Actually I found the GnuPG folder.

C:\Program Files (x86)\GnuPG\bin>keybase pgp select C:\Program Files (x86)\GnuPG\bin\^^^^^^^^^^^^-public.asc
Error parsing command line arguments: PGP select takes 0 or 1 arguments

NAME:
   keybase pgp select - Select a key from GnuPG as your own and register the public half with Keybase

USAGE:
   keybase pgp select [command options] [key query]

DESCRIPTION:
   "keybase pgp select" looks at the local GnuPG keychain for all
   available secret keys. It then makes those keys available for use with keybase.
   The steps involved are: (1a) sign a signature chain link with the selected PGP
   key and the existing device key; (1b) push this signature and the public PGP
   key to the server; and if "--import" flag is passed: (2a) copy the PGP secret half
   into your local Keybase keyring; and (2b) encrypt this secret key with Keybase's
   local key security mechanism.

   By default, Keybase suggests only one PGP public key, but if you want to,
   you can supply the "--multi" flag to override this restriction. If you
   want your secret key imported into the local Keybase keyring, then use
   the "--import" flag. Importing your secret key to Keybase keyring makes
   it possible to use Keybase PGP commands like "pgp decrypt" or "pgp sign".

   If you don't want to publish signature chain link to Keybase servers, use
   "--no-publish" flag. It's only valid when both "--no-publish" and "--import"
   flags are used.

   This operation will never push your secret key, encrypted or otherwise,
   to the Keybase server.

OPTIONS:
   --multi      Allow multiple PGP keys.
   --import     Import private key to the local Keybase keyring.
   --no-publish Only import to Keybase keyring, do not publish on user profile.



C:\Program Files (x86)\GnuPG\bin>
Lenguaje dominante
Sin datos de lenguaje
Estrellas
899
Forks
40
Sin PR fusionados en 30 d

Preparar el entorno

Este proyecto no incluye contenedor de desarrollo, Dockerfile ni guía de contribución, así que la configuración corre por tu cuenta: empieza por su README y consulta nuestra guía para la primera contribución para los pasos generales.

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de keybase/keybase-issues

Todos los issues de keybase/keybase-issues

Issues similares

Más issues de Cryptography

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.