login fails with ▶ ERROR Message wasn't signed
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 9.2k
- Forks
- 1.3k
- Avg merge
- 12h 58m
- Merged PRs (30d)
- 56
Description
I cannot login using the keybase client under Arch installed yaourt.
My log id is: 74bc3f3663eca6bd568fc31c. What I am seeing when I use my email address is:
$ keybase login
Your keybase username or email address: bengt.lueers@gmail.com
▶ WARNING Error running Bug 3964 repairman: lksec load: no device id set, thus can't fetch server half
▶ WARNING In Bug 3964 repair: lksec load: no device id set, thus can't fetch server half
▶ ERROR Message wasn't signed
$
When I use my keybase user name, I get a similar error (log ID b83799472162795c6aed1c1c):
$ keybase login
Your keybase username or email address: bengt
▶ ERROR Message wasn't signed
$
I can decrypt, sign and encrypt messages using gpg (version 2) and using keybase.io.
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
Start with the keybase login entry point and the provided log IDs 74bc3f3663eca6bd568fc31c and b83799472162795c6aed1c1c. Investigate the reported “Message wasn't signed” error alongside the Bug 3964 warnings and Arch installation details; done means login succeeds using either the email address or username.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- arch-linux, go
- Domain
- authentication, security
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100