Loading Profile...
keychain access
I'm a huge fan of Delicious Library. The only thing that bugs me is this: why does it want access to my keychain? When I start it, I get a message: "Delicious Library 2 wants to use your confidential information store in "[user]" in your keychain." Thanks for any info.
I’m acting like a paranoid person
2
people have this question
I have this question, too!
Tell me when someone answers.
The more people who ask this question, the more it gets noticed.
The more people who ask this question, the more it gets noticed.
The company marked this question as answered.
The best answer from the company
-
Since .Mac is the only thing we use Keychain for, you should be able to get around this by deselecting .Mac in your publishing settings. Go into the publish settings and where it says Publish To: select something like Folder instead of dotMac. This *should* stop DL2 from asking about your keychain...
Sorry for the annoying keychain messages, but this should work! Let me know if it doesn't work and I'll try and get it resolved asap =)
The company says
this answers the question
-
Inappropriate?Don't worry, we aren't stealing all of your information =) There are a few passwordy services that we sync with for .Mac stuff for when you want to upload your library to the web.
-
Inappropriate?Thanks for the quick reply! I hadn't thought about the .Mac stuff. Is there a way I can get DM not to ask unless I'm actually uploading to .Mac? I don't do that at all right now.
-
Inappropriate?Thanks for the reply. Since I don't do anything with Delicious Library that requires my password, I don't think I should have to ever allow, much less "Always Allow." I don't have any reason to think that DM is doing anything malicious with my password, but allowing unnecessary access to my password seems like a bad idea on principle.
-
Inappropriate?I agree with that. A matter of principle. We should have the option to allow or disallow. -
Inappropriate?You do have the option to disallow... This is the way keychain works in Mac OSX, we don't have much control over it =\
1 Comment Add a comment
This answers the question
-
My library is not accepting either a scanned barcode or a typed in ISBN. Could this be because I have not allowed keychain access? -
Inappropriate?Hi,
I also have trouble with this. It may be that Mac OSX forces you to only offer users three options (Always Allow, Deny, or Allow).
However, Delicious Monster does NOT have to attempt to access the keychain until .Mac information is needed. That way, we don't have to "deny" keychain access every single time the program starts.
Simple task for the programmers?
Thanks!
I’m frustrated
-
Inappropriate?Since .Mac is the only thing we use Keychain for, you should be able to get around this by deselecting .Mac in your publishing settings. Go into the publish settings and where it says Publish To: select something like Folder instead of dotMac. This *should* stop DL2 from asking about your keychain...
Sorry for the annoying keychain messages, but this should work! Let me know if it doesn't work and I'll try and get it resolved asap =)
The company says
this answers the question
-
Inappropriate?Brilliant! Yes, I switched the "publish to" setting to "folder," quit the app, restarted the app, and now it doesn't ask for keychain access.
Thank you.
EMPLOYEE
