Ask Different is a question and answer site for power users of Apple hardware and software. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I'm getting really tired of seeing this: “ubd wants to use the “elliottcable” keychain.”

As I understand it, ubd (the Ubiquity daemon) is responsible for the “Documents and Data” portion of iCloud's syncing. However, all of my iCloud-related data are in a separate, non-locking keychain.

How can I tell which keychain entries a particular process is trying to access? Failing that general case, does anybody know which keys specifically ubd needs access to?

share|improve this question
That's odd; I guess I'd expect a checkbox on this dialog window that would be something like "Always allow ubd to access the keychain". I don't know how to answer your question though. – bneely Dec 18 '11 at 2:30

First with any Keychain question/problem, run Keychain First Aid, found under the Keychain Access menu.

It is to be hoped you also check the option to Show Keychain Access in menubar, for quick access to all.

share|improve this answer

What you could do (but will take some time) is to check each keychain item and see which ones have allowed "ubd" to have access to (on the Access Control tab, while viewing a Keychain item).

Also make sure that "Confirm before allowing access" is selected. After that, you can just unlock the keychain and you will get a "ubd" wants to access the entry ... in your keychain.

share|improve this answer

This is just a first level warning that the process UBD wishes a look inside keychain for something. At that point you have to go inside that keychain and check that all of the items do not let that process automatically or always access the contents(one by one for each item in the keychain). The tool for this looking is Keychain Access.

What you verified the things in the keychain are set properly you can go ahead and allow the opening of the keychain and it will then be able to just examine what is inside that keychain file by name.

In this case everything seems "on the up and up" because the ubiquity demon would quite reasonably want to look inside that keychain file just to see if you could be storing an iCloud account credentials. It doesn't mean it would get to read the password or anything encrypted about that iCloud account, it's just checking to see if an iCloud account could be stored in there.

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.