docs(crypto): clarify encryptable contract - #1286
Conversation
🔍 SDK Breaking Change DetectionSDK Version:
Breaking change detection uses the build of the SDK from this branch, including any incompatibities pre-existing on or merged into this branch. Check the workflow logs to confirm. |
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #1286 +/- ##
=======================================
Coverage 85.74% 85.74%
=======================================
Files 483 483
Lines 68364 68364
=======================================
Hits 58622 58622
Misses 9742 9742 ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
7238134 to
5d8de7a
Compare
🤖 Bitwarden Claude Code ReviewOverall Assessment: APPROVE This is a documentation-only change to Code Review DetailsNo blocking findings. Minor note (not blocking): |
…rify encryptable contract (bitwarden/sdk-internal#1286)
Encryptables currently have mis-usages, which lead to easy bugs. For example, encrypt(decrypt(encrypt(K1), K1), K2) may lead to an item partially being encrypted by K1, and partially by K2. The next decrypt will fail. This is entirely unexpceted and a footgun. This PR adds clarification on the intent (contract) of the traits, and tags usages that are violating the contract.