keybase / keybase/client

Bad passphrase

Open
#4,666 3 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

useful and descriptive?

i don't know that this will be either, but, after installing keybase on a windows 10 machine and under Lubuntu on another box, i decided to put it on my Macbook running Sierra, and hilarity ensued.

Win10 Desktop -> Lubuntu Lappy -> Macbook
first i tried re-naming the Lubuntu box and the Macbook, when i found i couldn't do that i
revoked the Lubuntu, then re-added it with the correct name using the Macbook to provision it. then i revoked the Macbook and added it with the correct name, provisioning it with the Lubuntu box.

then both machines cried for paper keys to allow me access to my private files on the FS...
i used my paper key on the Lubuntu box, and then discovered i needed to leave off the first two words for that to work, for some reason....

then i tried a paper key on the Macbook, it wouldn't accept any variation of the original key, so i created a new one, tried that, minus the first two words, that didn't work, so i C/P'd the entire key and voila, it seemed to accept that, the app opened and i could choose private/public in the gui.... there were no files in either though.

i re-booted and was prompted to log in, now i'm getting "bad passphrase" hence sending the error log, i clicked "show typing" just to make sure my keys are in the correct place on the keyboard (they are) so, i have no clue what's up with this.

i understand this project is in Alpha and i hope whatever nonesense i've just shared furthers the cause!

my log id: 58e0fbd4c05bc8d577b6451c

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

Begin with the error log referenced by log id 58e0fbd4c05bc8d577b6451c and review the Windows 10, Lubuntu, and macOS Sierra provisioning and revocation sequence. Reproduce the post-reboot “bad passphrase” failure; done means identifying a reproducible cause and a verified resolution, but the report names no source file or test.

Written by the indexing model from the issue text.

Assessment

Domain
authentication, operating-systems
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.