keychain

Until Xcode 8/iOS 10, I was able to access the Keychain from within the unit tests of a static library. After upgrading, I get an error, see stack trace: failed: caught "NSInternalInconsistencyException", "Couldn't add the Keychain Item." ( 0 CoreFoundation 0x000000010b2a734b __exceptionPreprocess + 171 1 libobjc.A.dylib 0x000000010ad0821e objc_exception_throw + 48 2 CoreFoundation 0x000000010b2ab442 +[NSException raise:format:arguments:] + 98 3 Foundation 0x000000010a89eedd -[NSAssertionHandler handleFailureInMethod:object:file:lineNumber:description:] + 195 4 MyLibTests 0x0000000117366dea -

So the OS X Keychain has three pieces of information: ServiceName (the name of my app) Username Password I obviously always know the ServiceName. Is there a way to find any saved Username(s) for that ServiceName? (Finding the password is easy once you know the Username.) I would much prefer to use a nice Cocoa wrapper such as EMKeychain to do this. But EMKeychain requires the UserName to get any keychain item! + (EMGenericKeychainItem *)genericKeychainItemForService:(NSString *)serviceNameString withUsername:(NSString *)usernameString; How are you expected to fully utilize saving credentials

I'm trying to sign some data using SecKeyRawSign but I keep getting a -4 errSecUnimplemented. That seems strange since the documentation states that it is available in iPhone OS2.0 and later. Has anyone been able to use this function? If so, are there any tricks involved? ~Nate If you're having this problem, most likely it is because the private key you generated isn't actually being saved into the keychain. I figured this out when stopping and restarting the application and signing the message wasn't working. So here are my methods to make this work. This one generates the key pair - (void

Calls to the the Keychain Services fail with errSecNotAvailable when executing a target using the command line tools and the iphone simulator is set to Hardware version 6.0 (10A403). If I change the simulator version to other previous version (4.3, 5.0, 5.1) and re-execute using the same command line script the calls succeed. I'm running latest XCode 4.5 and the command line tools were downloaded from within XCode. To reproduce this error just do the following: Setup an ios library project with a OCUnit target Set Base SDK to 6.0 Set iOS Deployment Target to 4.3 Copy and paste the code st the

We're using a multi platform application which should run on both Windows and Mac. Our application is based on OpenSSL as the SSL and related stuff supplier. It uses Client Certificate to establish secure connections and to identify the end user. We want to use Windows and Mac native certificate storages to ensure maximum security. Openssl has an engine to interact with Windows' Certificate Store (CAPI engine). However, we didn't manage to find such a solution for Mac's Keychain. Is there an integration between OpenSSL and Apple's Keychain? If not, what are your suggestion ? In addition to

The KeychainItemWrapper class in the Apple GenericKeychain sample use kSecValueData key to store password. But the reference http://developer.apple.com/library/ios/#documentation/Security/Reference/keychainservices/Reference/reference.html#//apple_ref/doc/uid/TP30000898 says kSecValueData is used in the results dictionary for SecItemCopyMatching or SecItemAdd, indicating the type of values returned. which key should I use when I call SecItemAdd to create a keychain item? You should use kSecValue data as the key to store the password (in NSData or CFDataRef format). The reference is a bit

I've been digging around Apple forums and SO for this issue to no avail. Using Apple's KeychainItemWrapper (ARCified), trying to set the kSecAttrAccessible attribute to anything except the default ( kSecAttrAccessibleWhenUnlocked ) results in an assertion failure from SecItemUpdate returning an error. KeychainItemWrapper *wrapper = [[KeyChainItemWrapper alloc] initWithIdentifier:kMyIdentifier accessGroup:nil]; [wrapper setObject:kMyServiceName forKey:(__bridge NSString*)kSecAttrService]; [wrapper setObject:kMyAccountToken forKey:(__bridge NSString*)kSecAttrAccount]; [wrapper setObject:(_

I am trying to switch on a certain keychain, and close another one. I need this because our enterprise & appstore identities are called the same. Right now, I do a "security unlock-keychain" followed by a "security default-keychain" to open the correct keychain and do a "security lock-keychain" on the keychain I wish not to use. But xcodebuild still sees the entries in both keychains and gives up. iPhone Distribution: Company name.: ambiguous (matches "iPhone Distribution: Company name." in /Users/user/Library/Keychains/login.keychain and "iPhone Distribution: Company name" in /Users/user