-
Notifications
You must be signed in to change notification settings - Fork 48
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
Accessibility Issue #3
Comments
I'm afraid something has changed with recent macOS updates. If you inspect a keychain item (select it in Keychain.app, then File > Get Info > Access Control), it is likely that “Confirm before allowing access” is selected, but “Ask for a keychain password” is not. Despite that, it seems that now the system asks for a password anyway. I'll see whether a fix is possible, but I can't promise anything. |
Same issue here. Let me known if there is any workaround. |
@ErinAmalie @lifepillar @MrSparklle Managed to export following information found at Original Source Export Script You can verify this is the original source as linked in README.md It was still fiddly, especially as it was initially asking for the 'destination' keychain password, then the source keychain password. I basically started the copy, provided the first 'destination' keychain password, then started the script. |
Thanks for link! I’ll take a look later. |
This commit addresses #3 by implementing the fix suggested here: https://gist.github.com/rmondello/b933231b1fcc83a7db0b#gistcomment-2272755
Please try the current master, which implements the fix suggested by @dmblack. It works for me in macOS 10.13.5, although it is a bit of a nuisance if you type the wrong password (the script goes into a loop by repeatedly entering the wrong password into a SecurityAgent dialog: it that happens, try to stop the script in Script Editor). Also, review the Readme. Thanks @dmblack! |
I've tried to run the script twice but I am being asked for my password every time. I followed the provided directions and gave script editor full access before running the script. Any advice?
The text was updated successfully, but these errors were encountered: