"Login failed after passphrase verified" in macOS client
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 9.2k
- Forks
- 1.3k
- Avg merge
- 12h 58m
- Merged PRs (30d)
- 56
Description
Logging into the mac client, I get the error "Login failed after passphrase verified". This is a distinctly different error than the error I get if typing in an incorrect passphrase.
I can log into the web client with the same passphrase with no errors. My PGP key is stored with keybase, and using the web client, I can successfully encrypt and decrypt messages with other users.
I tried, to no avail:
- Changing my password through the keybase web client. This successfully changed my password, but the new password has the same error.
- Uninstalling keybase by first running "keybase uninstall", then deleting the keybase app, then re-installing.
I have not tried logging out of my other device and attempting to log in again just in case I'm locked out of both devices and can't easily access my chats again. Looking up this error on google, both people who had this issue previously have had success with deleting all their keys and starting over, but I'd like not to do that if possible.
my log id, by just running "keybase log send": 564177cfa2822ea3c2d2a91c
my log id, by running "keybase log send" immediately after attempting to log in: 361ccee1fa4171128a338d1c
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue names no source file or test. Start by reviewing the two submitted log IDs and reproducing the macOS login failure described; done means resolving the post-passphrase login error without requiring key deletion, then verifying that login succeeds.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- authentication, desktop
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100