-
Notifications
You must be signed in to change notification settings - Fork 24
[PM-29048] Validate pin protected user key envelope #628
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Conversation
|
Great job! No new security vulnerabilities introduced in this pull request |
🔍 SDK Breaking Change Detection ResultsSDK Version:
Breaking change detection completed. View SDK workflow |
Codecov Report❌ Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #628 +/- ##
=======================================
Coverage 78.84% 78.84%
=======================================
Files 283 283
Lines 29660 29723 +63
=======================================
+ Hits 23384 23434 +50
- Misses 6276 6289 +13 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
quexten
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Some nits on the commenting, but nothing blocking.

🎟️ Tracking
https://bitwarden.atlassian.net/browse/PM-29048
📔 Objective
Enables validation for a PIN for a pin protected key envelope, so that mobile can move off of
validatePinwhich only works with pin key protected userkeys.The original
validate_pinimplementation compared the decrypted user key from envelope with the client key stored user key. This implementation is much simpler, we simply validate if the envelope can be successfully unsealed with provided PIN.Tested against android.
🚨 Breaking Changes
None
⏰ 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