Encrypt for current user/self while offline
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 9.2k
- Forks
- 1.3k
- Avg merge
- 12h 58m
- Merged PRs (30d)
- 56
Description
It ought to be possible - especially for a user not storing private keys in Keybase cloud - to encrypt for only 'self' while offline.
Unfortunately, keybase encrypt fails, requiring user[s] parameter. I'm keybase.io/ojford; so keybase encrypt would be a nice shortcut for keybase encrypt ojford.
However, even if I am logged in as ojford, keybase encrypt ojford will attempt to find ojford on keybase.io - which of course fails if I am offline.
I can of course fallback to using gpg instead, but it would be a nicer UX if Keybase supported:
$ ip link set $NETWORK_INTERFACE down
$ keybase encrypt # logged-in user implied
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 at the keybase encrypt CLI entry point and trace how the current user and recipient are resolved when offline. Verify the behavior with the network disabled as shown in the issue; done means keybase encrypt encrypts for the logged-in user without querying keybase.io.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- cli, cryptography
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100