keybase / keybase/keybase-issues
Some command line operations do not perform consistency checks on options/arguments
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 899
- Forks
- 40
- PR merge metrics
- No merged PRs in 30d
Description
Certain commands can be used with conflicting options, resulting in confusing errors.
Example:
$ keybase encrypt -m "Hello" pkirkovsky -o crypted.asc
$ keybase decrypt -m crypted.asc
warn: gpg: no valid OpenPGP data found.
warn: [GNUPG:] NODATA 1
warn: [GNUPG:] NODATA 2
warn: gpg: decrypt_message failed: Unknown system error
error: `gpg` exited with code 2
In this case, the -m option should be discarded since a file has been specified or the user should receive feedback about conflicting options.
Strangely, keybase does seem to perform this check in a different scenario:
$ cat crypted.asc | pbcopy
$ pbpaste | keybase decrypt -m
keybase decrypt: error: argument "-m/--message": Expected one argument. null
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 the conflicting-option examples with the keybase encrypt and keybase decrypt commands, then trace their command-line option handling. Done means conflicting options are discarded or produce clear feedback instead of being passed on to gpg and causing confusing errors.
Written by the indexing model from the issue text.
Assessment
- Domain
- cli
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100