Error code 1009: SIG_BAD_CLOCK in method keybase.1.login.login
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 9.2k
- Forks
- 1.3k
- Avg merge
- 12h 58m
- Merged PRs (30d)
- 56
Description
[write something useful and descriptive here]
my log id: a9175cebc6b25bffc8d4db1c
I have a Mac-mini M1 Apple chip: bad signature: your computer's clock is wrong: signature is dated 10791 seconds in the future => Error code 1009: SIG_BAD_CLOCK in method keybase.1.login.login
More feedback (or press when done):
▶ INFO Not sending up a UID for logged in user; none found
Success! Your log ID is: a9175cebc6b25bffc8d4db1c
Here's a URL to submit new bug reports containing this ID:
https://github.com/keybase/client/issues/new?body=[write%20something%20useful%20and%20descriptive%20here]%0A%0Amy%20log%20id:%20a9175cebc6b25bffc8d4db1c
Thanks!
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.1.login.login entry point and the supplied log ID a9175...d1c, then reproduce the SIG_BAD_CLOCK / error 1009 report on the Mac mini M1 context. Trace how the 10,791-second clock difference is detected and verify that the login path handles the reported condition correctly.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, macos
- Domain
- authentication
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100