keybase / keybase/keybase-issues

"You need a passphrase to unlock the secret key"

Open
#1,214 17 comments 0 reactions 0 assignees View on GitHub
Dominant language
No language data
Stars
899
Forks
40
PR merge metrics
No merged PRs in 30d

Description

Having just joined keybase and encrypted my first test message:

```
$ keybase encrypt -m "This is a secret message" joelteon > message
$ keybase decrypt message -o message.txt

You need a passphrase to unlock the secret key for
user: "keybase.io/joelteon "
2048-bit RSA key, ID 5C168495C8328D1E, created 2014-11-04
(subkey on main key ID 4FB87AFD575DFF5D)

warn: [GNUPG:] ENC_TO 5C168495C8328D1E 1 0
warn: [GNUPG:] USERID_HINT 5C168495C8328D1E keybase.io/joelteon
warn: [GNUPG:] NEED_PASSPHRASE 5C168495C8328D1E 4FB87AFD575DFF5D 1 0
warn: gpg: cancelled by user
warn: [GNUPG:] MISSING_PASSPHRASE
warn: gpg: encrypted with 2048-bit RSA key, ID 5C168495C8328D1E, created 2014-11-04
warn: "keybase.io/joelteon "
warn: gpg: public key decryption failed: Operation cancelled
warn: [GNUPG:] ERROR pkdecrypt_failed 99
warn: [GNUPG:] BEGIN_DECRYPTION
warn: [GNUPG:] DECRYPTION_FAILED
warn: gpg: decryption failed: No secret key
warn: [GNUPG:] END_DECRYPTION
error: `gpg` exited with code 2
```

Contributor guide

No contributing guide indexed for this repository

Research direction

Start by reproducing the documented `keybase encrypt` and `keybase decrypt` commands and inspect how the client invokes GPG during decryption. The issue does not identify a source file or test; done should mean determining why the secret key is unavailable or unexpectedly prompts for a passphrase and confirming the command's decryption behavior.

Written by the indexing model from the issue text.

Assessment

Domain
cli, security
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.