Using OAEP cipher mode to encrypt unique id #2656
Open
+14
−6
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
NB: Falling back on PKCS1 at decryption time to successfully decode unique id encoded with MSDK 12 or older At this point PKCS1 is only used in fall back scenarios - to decrypt payloads encrypted for older version of MSDK: - to decrypt encrypted push notifications, if server generated key was created with PKCS1 cipher mode - to decrypt unique id, if it was encrypted with PKCS1 cipher mode
brandonpage
approved these changes
Jan 24, 2025
Tests results for SalesforceReactGenerated by 🚫 Danger |
Tests results for MobileSyncGenerated by 🚫 Danger |
Tests results for SalesforceHybridGenerated by 🚫 Danger |
Tests results for SmartStoreGenerated by 🚫 Danger |
…PKCS1 cipher mode
|
NB: manually tested upgrade - login to app that uses old generateUniqueIdIfNoneStored and then relaunching app with the new generateUniqueIdIfNoneStored and making sure uniqueId was read and written back using new cipher mode. |
Tests results for SalesforceSDKGenerated by 🚫 Danger |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
NB: Falling back on PKCS1 at decryption time to successfully decode unique id encoded with MSDK 12 or older
At this point PKCS1 is only used in fall back scenarios - to decrypt payloads encrypted for older version of MSDK: