Can't login after updating expired key
Open
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 9.2k
- Forks
- 1.3k
- Avg merge
- 12h 58m
- Merged PRs (30d)
- 56
Description
Howdy!
My subkey expired. So I added a new one, updated on the website, and tried to login, but...
$ keybase login mikeboers
▶ WARNING Checking status of key 0101744632bd95760eb6a205d689393290ded64bfa566bc17d3a844a2c9edecae5b40a
with respect to time [Tue Feb 7 08:34:25 -0500 EST 2017],
found it had expired at [Mon Aug 8 01:34:36 -0400 EDT 2016].
▶ ERROR Key expired: The key '0101744632bd95760eb6a205d689393290ded64bfa566bc17d3a844a2c9edecae5b40a' expired at 2016-08-08 01:34:36 -0400 EDT
This at least is a different message from my login attempt before adding a new subkey. Hopefully the log (IDed below) will help.
Cheers,
Mike
my log id: fe9a6c7a00ccae1725b7211c
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 by reproducing keybase login mikeboers with the updated subkey and inspect log ID fe9a6c7a00ccae1725b7211c. Trace how login checks key expiration after a website key update; done means the current subkey is accepted and login no longer reports the expired key.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- authentication, security
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100