Skip to content
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

How to disable keychain data recovery from iCloud backup #153

Open
0x1306a94 opened this issue Jun 23, 2022 · 2 comments
Open

How to disable keychain data recovery from iCloud backup #153

0x1306a94 opened this issue Jun 23, 2022 · 2 comments

Comments

@0x1306a94
Copy link

  • Device A creates a token write through the following options
kSecAttrAccessible = kSecAttrAccessibleAlwaysThisDeviceOnly
kSecAttrSynchronizable = kSecAttrSynchronizableAny
  • Device A creates an iCloud backup
  • Device B erases or reflashes the firmware
  • Device B selects the iCloud backup created by Device A to restore
  • After the recovery of Device B is completed, the application can read the token written by Device A
  • I want to disable the ability to read tokens created by other devices after restoring from the iCloud backup of other devices, what should I do?
@matthiastz
Copy link

Hey, did you try to just disable the iOS cloud sync for your local on Device A via KeychainSwift?

let keychain = KeychainSwift()
keychain.synchronizable = false

https://github.com/evgenyneu/keychain-swift#synchronizing-keychain-items-with-other-devices

@0x1306a94
Copy link
Author

0x1306a94 commented Jul 6, 2022

Hey, did you try to just disable the iOS cloud sync for your local on Device A via KeychainSwift?

let keychain = KeychainSwift()
keychain.synchronizable = false

https://github.com/evgenyneu/keychain-swift#synchronizing-keychain-items-with-other-devices

@matthiastz

  • still the same
  • From the actual results, synchronization should not be equal to backup recovery

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants
@0x1306a94 @matthiastz and others