keybase appears to be extremely broken
- Dominant language
- Go
- Stars
- 9.2k
- Forks
- 1.3k
- Avg merge
- 12h 58m
- Merged PRs (30d)
- 56
Description
folders in `/keybase/private/joshuaacasey` are inaccessible
folders in `/keybase/team` are inaccessible
```
joshua@homeserver:~$ cd /keybase/team
joshua@homeserver:/keybase/team$ ls
ls: cannot access 'fffusa': Input/output error
ls: cannot access 'joshuaacasey_': Input/output error
ls: cannot access 'joshuaacasey_.ssh.staging': Input/output error
ls: cannot access 'joshuaacasey_.ssh.production': Input/output error
ls: cannot access 'joshuaacasey_.ssh.root_everywhere': Input/output error
ls: cannot access 'commandline': Input/output error
ls: cannot access 'sysadmins_unite': Input/output error
ls: cannot access 'lewdful': Input/output error
ls: cannot access 'devrelopers.io': Input/output error
ls: cannot access 'keybasefriends': Input/output error
ls: cannot access 'stellar.public': Input/output error
ls: cannot access 'joshuaacasey_.ssh': Input/output error
```
(my log id: 54e97357172f995c55b0251c)
The devices tab of the android app is showing 0 devices (which is wrong because I haven't removed them). Out of curiosity I logged out of the Windows app to log back in and it fails with `server rejected session; is your device revoked?
Error code 202: BAD_SESSION in method keybase.1.login.login` Please fix!
Contributor guide
No contributing guide indexed for this repository
Research direction
Start with the supplied log ID 54e97357172f995c55b0251c and reproduce the failures under /keybase/private and /keybase/team, then compare the Android devices view and Windows login error. Done means the listed folders are accessible, the expected devices appear, and Windows login no longer returns BAD_SESSION.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100