It’s generally better to migrate or restore from a backup or copy, which isn’t an easy choice either. Manually reconstructing a keychain or building a fresh one, for instance after resetting the login keychain and wiping its contents, is lengthy and tedious. In the past, Keychain Access has also provided a First Aid feature to check and repair faulty or damaged keychains, but it no longer does. It can normally be rectified by changing the password for the login keychain to the same as the user login password. This results in login requiring you to enter two passwords instead of one. However, sometimes the two passwords become different, usually because you changed the password on the login keychain separately. When you change your user password, that should automatically change the password for the login keychain as well, ensuring that unlocking still works automatically. Even when you set a custom keychain to be kept unlocked, before you can access it the first time after each login, you’ll be required to enter its password, as it can’t be unlocked automatically in the way that the login keychain is.īy default, your user login and login keychain passwords are identical, enabling macOS to automatically unlock your login keychain whenever you log in as that user. If you have custom keychains that are being accessed repeatedly and resulting in repeated password requests, try copying the items being accessed from those to your login keychain, which should eliminate the need to keep opening that custom keychain. You can then increase the time before that keychain is locked automatically, or disable locking altogether. To change locking behaviour of a keychain, select that keychain in the sidebar of Keychain Access and use the Edit / Change Settings for Keychain menu command to show that keychain’s settings. Locking of keychains is simple to observe in the sidebar of Keychain Access, or in Mints’ Keychain tool. Your Mac’s security system will then decide whether to give that app lasting access, so saving further requests. If you’re happy that app should be given access to that keychain, instead of pressing Return to Allow that access, click on Always Allow. There are two normal reasons for repeated requests for authentication to unlock keychains: either the app making the request isn’t trusted to access that keychain or item within it, or the keychain is being locked again after use, something that shouldn’t normally happen for the login keychain. However, this can sometimes occur genuinely when an app has just been updated, for instance. If you start seeing requests from Safari to open your login keychain to give access to passwords that it should already have, suspect that the app has been changed, forcing reset of its access rights, or that the requests are bogus either way you should suspect a security problem. For example, Safari is normally given full access to your web and Internet access passwords, so it doesn’t prompt you for individual access. You should also be wary of apps suddenly requesting access that they should already have. If any request for access to a keychain or its password doesn’t meet all the above, then don’t enter any text into it, and deny the request immediately: it’s likely to be malicious. The exact layout of these items has changed a little over the years.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |