Fail decryption if any part of the cipher fails to decrypt #425
+50
−50
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
🎟️ Tracking
📔 Objective
While testing SDK integration on https://bitwarden.atlassian.net/browse/PM-24745, I found that failures to decrypt were being swallowed - values were being coerced into empty-string /
None
if that value failed to decrypt, and therefore were reported as successful decryptions from the SDK.I specifically noticed it and fixed it for
Login
ciphers, and then I ran a find/replace to update all instances where errors fromdecrypt
were being coerced into anOption
with.ok()
-- I replaced all of these with the?
operator, using the below regex, and verified that the crates still build locally. Since these are all called from functions that already return aResult
of the appropriate type, it's assumed (read: untested) that these errors are appropriately handled upstream.Regex used:
sed/(decrypt\([^)]*\))\.ok\(\)((\.unwrap_or_default\(\))|(\.flatten\(\)))?/\1?/g
⏰ Reminders before review
team
🦮 Reviewer guidelines
:+1:
) or similar for great changes:memo:
) or ℹ️ (:information_source:
) for notes or general info:question:
) for questions:thinking:
) or 💭 (:thought_balloon:
) for more open inquiry that's not quite a confirmedissue and could potentially benefit from discussion
:art:
) for suggestions / improvements:x:
) or:warning:
) for more significant problems or concerns needing attention:seedling:
) or ♻️ (:recycle:
) for future improvements or indications of technical debt:pick:
) for minor or nitpick changes