If the command that launched the daemon proccess is start with --tor-mode strict, the daemon runs all commands with --tor-mode strict
Open
- Dominant language
- Go
- Stars
- 9.2k
- Forks
- 1.3k
- Avg merge
- 12h 58m
- Merged PRs (30d)
- 56
Description
Steps to reproduce
1. kill the daemon process
2. run "keybase --tor-mode strict status"
3. run "keybase --tor-mode leaky login" This will fail because the daemon process will apply tor-mode strict to all future commands.
Contributor guide
No contributing guide indexed for this repository
Research direction
Reproduce the issue with the two `keybase --tor-mode ...` commands, then trace the command entry point and daemon handling for how tor mode is retained between commands. Done means a strict status command no longer forces a later leaky login command to fail.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- cli
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100