keybase / keybase/client

Prompt for PGP passphrase isn't effective

Open
#2,048 5 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Go
Stars
9.2k
Forks
1.3k
Avg merge
12h 58m
Merged PRs (30d)
56

Description

> keybase version
Client:  1.0.12-0
Service: 1.0.12-0

I'm trying to encrypt and sign a file:

keybase pgp encrypt --sign --infile regions

I'm prompted for the passphrase for my PGP key:

              ┌──────────────────────────────────────────────────────────────┐
              │ Please enter the passphrase to unlock the secret key for:    │
              │ PGP key Brian Lalor <blalor@bravo5.org> AC54EE282DBC1921     │
              │                                                              │
              │ Reason: command-line signature                               │
              │                                                              │
              │ Your key passphrase ________________________________________ │
              │                                                              │
              │         <OK>                                  <Cancel>       │
              └──────────────────────────────────────────────────────────────┘

I enter the password (correctly, honest!) and get the error Failed to unlock key; bad passphrase.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Reproduce the failure with keybase version 1.0.12-0 using keybase pgp encrypt --sign --infile regions and the reported PGP key. Trace the command-line signature passphrase-unlock path; done means a correct passphrase unlocks the key and the encryption and signing command completes successfully.

Written by the indexing model from the issue text.

Assessment

Tech stack
go
Domain
cli, cryptography, security
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.