My mistake, it's only the SecKeychainAddGenericPassword routine that
returns 1. Furthermore, it seems that the problem exists goes away
once the tool is relaunched. However, even though these conditions are
more unique than I originally thought, I still need a way to work
around this...
On Nov 9, 2004, at 5:14 PM, Keith Malkin wrote:
It seems that several Keychain Services APIs (like
SecTrustedApplicationCreateFromPath, SecAccessCreate, and
SecKeychainAddGenericPassword) return 1 for the status error code when
called from a Foundation Tool on Jaguar. Does anyone know why this
is, or even better, have a work around?
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Apple-cdsa mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden
