You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Oct 28, 2024. It is now read-only.
Correct me if I'm wrong, but reset_keychain() simply resets default keychain to login, but does not lock previously unlocked keychain in $KEYCHAIN_PATH.
The text was updated successfully, but these errors were encountered:
ivany4
changed the title
reset_keychain is hardcoded to login.keychain
Unlocked keychain is never locked
Jul 2, 2015
Yep you're actually right. But now that I think about it, I don't know if locking the keychain makes sense. Probably from a security standpoint it does and we could check the state of the key chain prior to unlocking, save it, and then after building the app lock the keychain if it was locked prior to launching.
What I don't like much about this is that given parallel builds (which we can do if the simulator isn't being used), this would probably fail as one process would lock the keychain in the middle of the other processes work, causing the build to fail.
This whole file-state based approach is really meh. I wish Apple had implemented this feature through some kind of session mechanism, where you would unlock the keychain with a per-process session.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Correct me if I'm wrong, but reset_keychain() simply resets default keychain to login, but does not lock previously unlocked keychain in $KEYCHAIN_PATH.
The text was updated successfully, but these errors were encountered: