keybase / keybase/keybase-issues
Should decrypt really fail?
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 899
- Forks
- 40
- PR merge metrics
- No merged PRs in 30d
Description
Hi,
I'm using Keybase almost every day in combination with pass as a password manager. See pass-keybase
Anyway. Before some days I revoked one of my devices, which I used to encrypt my passwords. Now, if I'm using another device to decrypt my passwords I get the error
Authored by mbauhardt, however the key that authenticated this message has been revoked (key ID: 01200cec64dad851a5ea3a4c4982b57e492e4f06e7c41444b7b52f9c052b911d5e340a).
Use --force to decrypt anyway.
▶ ERROR Decryption error: For user "mbauhardt": sender key revoked
I mean sure, when I use the option --force I'm able to decrypt.
The question I have is about: Is It really convenient to not decrypt a message if the sender's key is revoked, or could be a warning message enough?
Thx
Marko
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
The issue names no files, tests, or entry points. Start by locating the decryption handling for revoked sender keys and the existing --force behavior, then determine whether the desired outcome is a hard failure or warning. Done means the behavior is decided and covered by an appropriate test.
Written by the indexing model from the issue text.
Assessment
- Domain
- cryptography, security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100