keybase / keybase/client

can't select pgp key

Open
#5,872 11 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

When running "keybase pgp select" I run into the following error:

2017-02-14T23:34:48.762280 ▶ [DEBU keybase log.go:30] 0a8 | running Gpg: /usr/local/bin/gpg2 --no-tty --armor --export-secret-key 1fbf7b37653768b12532a4cb0994094621dbefd4
2017-02-14T23:34:48.762585 ▶ [DEBU keybase log.go:30] 0a9 | setting GPG_TTY=/dev/ttys001
2017-02-14T23:34:48.769913 ▶ [WARN keybase log.go:34] 0aa Bad subkey: openpgp: invalid data: subkey signature invalid: openpgp: invalid signature: RSA verification failure
2017-02-14T23:34:48.771662 ▶ [DEBU keybase log.go:30] 0ab GPG version:
gpg (GnuPG) 2.0.30
libgcrypt 1.7.6
Copyright (C) 2015 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.

Home: ~/.gnupg
Supported algorithms:
Pubkey: RSA, RSA, RSA, ELG, DSA
Cipher: IDEA, 3DES, CAST5, BLOWFISH, AES, AES192, AES256, TWOFISH,
        CAMELLIA128, CAMELLIA192, CAMELLIA256
Hash: MD5, SHA1, RIPEMD160, SHA256, SHA384, SHA512, SHA224
Compression: Uncompressed, ZIP, ZLIB, BZIP2
2017-02-14T23:34:48.773005 ▶ [DEBU keybase log.go:30] 0ac | running Gpg: /usr/local/bin/gpg2 --no-tty --armor --export 1fbf7b37653768b12532a4cb0994094621dbefd4
2017-02-14T23:34:48.773422 ▶ [DEBU keybase log.go:30] 0ad | setting GPG_TTY=/dev/ttys001
2017-02-14T23:34:48.854519 ▶ [DEBU keybase log.go:30] 0ae SecretUI:GetPassphrase, sessionID = 0
2017-02-14T23:35:04.589684 ▶ [DEBU keybase log.go:30] 0af SecretUI:GetPassphrase, sessionID = 0

At this point, I have a dialog asking for the passphrase, but that doesn't work: it tells me I have not provided the valid passphrase.

Maybe relevant: the private key is on a Gemalto smartcard.

Maybe relevant:

pub  4096R/0x0994094621DBEFD4  created: 2009-06-26  expires: 2018-02-14  usage: SC
                               trust: ultimate      validity: ultimate
sub  4096R/0xE9821730F3198A94  created: 2009-06-26  expires: never       usage: E
sub  4096R/0x89B6FE7DB6633197  created: 2014-03-22  expires: 2018-02-14  usage: S

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

Start by reproducing keybase pgp select with the reported GnuPG 2.0.30 setup and Gemalto smartcard, then trace the PGP key export and passphrase flow indicated by the logs. Compare handling of the primary key and its signing and encryption subkeys. Done means the valid smartcard-backed key can be selected, or the command reports a clear actionable error.

Written by the indexing model from the issue text.

Assessment

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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.