Timeline for Updating Keychain entry manually prevents next access from GUI tools afterwards: Always asks for permission
Current License: CC BY-SA 3.0
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Aug 10, 2018 at 8:02 | vote | accept | NextThursday | ||
| Mar 2, 2017 at 15:09 | answer | added | Niklas | timeline score: 1 | |
| Sep 26, 2016 at 17:08 | comment | added | tubedogg | Multiple applications can access a single keychain item. In your case you happen to be modifying the item and trying to use it again in the same application, but again you're modifying it outside the purview of the application you previously authorized to use it. Therefore it makes perfect sense that OS X wants to confirm you are intending to allow access to the updated credentials that are stored, just as it would if an application tried to access a keychain item that it hadn't created. | |
| Sep 26, 2016 at 14:13 | comment | added | NextThursday | With "Allow Always" it remembers until the password is changed (again). However I doubt that it makes sense, that this is not configurable. You need elevated user privileges (twice) in order to change the entry, why should you be informed again upon first access. I understand that some "integrity check" might be useful, but it is not a catchable warning, it is a GUI popup as soon as you try to access the keychain (if I understand the Tunnelblick source code correctly). | |
| Sep 23, 2016 at 18:45 | comment | added | tubedogg | If you edit a Keychain entry outside of the application, it makes sense to me that OS X would prompt you to confirm you want the app to be able to access it. When you click Allow Always, does it not remember that setting? | |
| Sep 23, 2016 at 14:45 | history | asked | NextThursday | CC BY-SA 3.0 |