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

Suggestion: It would be better to support all kSecAttrAccessible values #12

Open
AlvaroBro opened this issue Nov 21, 2017 · 1 comment

Comments

@AlvaroBro
Copy link

For example, you may want to store a secret but prevent it to be carried to another device via encrypted backup. This would be a reasonable thing to want for example if you are encrypting you database with a passphrase stored in the KeyChain, and you want that database to be readable only in the device where it was created. Regards!

@reidmain
Copy link
Owner

Makes complete sense to me. I really just wanted to steer people away from using the "Always" option but it does feel like I should support everything EXCEPT for "Always".

Repository owner deleted a comment from CASABECI Aug 3, 2024
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

2 participants