keychain

Has anyone used Buzz Andersen's Simple iPhone Keychain code?

不想你离开。 提交于 2019-12-06 05:34:30
You can find it here. I'm trying to understand his sample code in order to write a simple program with that stores passwords into the keychain and retrieves them for login. Has anyone done this before? It would be most appreciated if I can see any examples you may have. There's really no code to demonstrate, he lists both calls there. Heres's an example, for what it is worth: NSError *error; [SFHFKeychainUtils storeUsername:@"fred" andPassword:@"mypassword123" forServiceName:@"myService" updateExisting:YES error:&error]; NSString *storedPassword = [SFHFKeychainUtils getPasswordForUsername:@

Get the Username(s) stored in Keychain, using only the ServiceName? OR: Where are you supposed to store the Username?

社会主义新天地 提交于 2019-12-06 05:00:26
问题 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 *

Unable to Publish from Github Desktop Application to github.com

情到浓时终转凉″ 提交于 2019-12-06 04:13:01
While trying to publish from Github desktop app to github.com am getting the following error. GitHub Desktop was unable to store the account token in the keychain. Please check you have unlocked access to the 'login' keychain. relogin didnt help. Updating Github desktop didn't help. Deleted all the entries regarding github in Keychain tool This seems to be caused by the Keychain being in an invalid state, affecting applications that try to use the keychain to store or retrieve credentials. Seems to be specific to macOS High Sierra and Mojave. Workaround: Open Keychain Access.app Right-click on

Using SecKeyRawSign on the iPhone

為{幸葍}努か 提交于 2019-12-06 03:23:04
问题 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 回答1: 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

How to save CFUUID in keychain

橙三吉。 提交于 2019-12-06 02:26:04
问题 I'm developing an iPhone application. The application access some web service that aboug other things should recognize the device ID. Since UDID is deprecated, I need to call CFUUIDCreate to generate my own UUID for this purpose. The ID is security-sensitive: all my network communication is encrypted, and I don't want nobody but my certificate-authenticated server to know that UUID. Besides, I want this identifier to survive re-install. Using the keychain to store that UUID seems like an

OpenSSL and Apple Keychain integration

℡╲_俬逩灬. 提交于 2019-12-06 01:55:34
问题 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

How to securely share data between two or more applications in android?

徘徊边缘 提交于 2019-12-05 22:58:31
问题 I am making an application framework for the enterprise environment which involves data sharing between two or more applications from the device memory . This data needs to be stored on the device and accessible to only a few applications (which can be identified by the certificates used to install them) . Also, it needs to be stored in a secure way so as to be not accessible to other third party applications . Which is the best way to implement this functionality ? I have read up about

Google plus sign-in for xcode share extension

让人想犯罪 __ 提交于 2019-12-05 21:46:30
I’m writing an iOS app to share web page links by email, and as part of it I want users to be able to sign in to google plus. I’ve got the containing app working fine using the instructions from here: https://developers.google.com/+/mobile/ios/sign-in and now I’m trying to add a share extension that can also access the user’s google+ profile. I started off by trying to add the sign in button in to the share extension, but I don’t think that’s going to work because after clicking the button you’re taken out of the app to the browser to accept permissions, and then there’s no way to redirect

Storing a .p12 certificate in keychain to use later

穿精又带淫゛_ 提交于 2019-12-05 21:15:07
I am trying to follow the apple docs for dealing with client p12 certificates here: https://developer.apple.com/library/ios/documentation/Security/Conceptual/CertKeyTrustProgGuide/iPhone_Tasks/iPhone_Tasks.html#//apple_ref/doc/uid/TP40001358-CH208-SW13 I have successfully loaded a .p12 cert from the file system: - (SecIdentityRef)getClientCertificate:(NSString *) certificatePath { SecIdentityRef identity = nil; NSData *PKCS12Data = [NSData dataWithContentsOfFile:certificatePath]; CFDataRef inPKCS12Data = (__bridge CFDataRef)PKCS12Data; CFStringRef password = CFSTR("password"); const void *keys

How to store your github https password on Linux in a terminal keychain?

不羁的心 提交于 2019-12-05 18:36:22
问题 This is becoming even more important now with the new 2-factor authentication, as one has to create a new token each time a password is required on the terminal. Basically, I'm looking for an equvalent to the osxkeychain available in OS X that I could use on Linux desktops and servers: git config --global credential.helper osxkeychain I searched through the possible solutions, but so far I don't like any of them: ssh instead of https - not recommended and links not easily accessible on GitHub