[Feature request] Make encrypted contents of /keybase/private openly accessible
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 9.2k
- Forks
- 1.3k
- Avg merge
- 12h 58m
- Merged PRs (30d)
- 56
Description
It would be nice to be able to access the files in /keybase/private/jyn514 from a computer where I'm not logged in but do have my PGP key. It would also help reassure me the server isn't keeping any plaintext, right now the software says it's encrypted but all the implementation details are hidden so I can't really know.
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/private/jyn514 path and the described distinction between being logged in and possessing the PGP key. Establish the security and access requirements for exposing encrypted contents without plaintext access, then define how the behavior would be validated; the issue identifies no files or tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- cryptography, security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100