keychain

Can the user access the keychain on iOS?

强颜欢笑 提交于 2019-11-29 18:17:30
问题 We're looking at storing some information (think the equivalent of usernames, passwords, etc) in our app that we don't want the user to be able to meddle with. One (bad) way to do this would be to put them in an encrypted file somewhere in the app's folder, but if we did that the user would be able to take any iOS filesystem exploration tool and edit or replace that file, which we don't want. If we stored the details in the keychain, is there any way the user could read or write those details

Store an encryption key in Keychain while application installation process

谁说我不能喝 提交于 2019-11-29 15:47:42
问题 I need my application to use client's phone-number to generate unique ID for my web-service. Of course a phone-number is unique, but it must be secured. So it can be implemented with symmetric encryption (asymmetric will be later, because leak of resources), but I do not know where to store a encryption-key. 1. I do not know why, but seems bad to store a key as a static field in code. May be because it's too easy to read it from here even not running an application. 2. It seems better to

How can I get the username for a proxy host from KeyChain?

随声附和 提交于 2019-11-29 15:43:42
问题 I'm writing an utility on the Mac and need to auto-determine proxy information. I've managed to get the proxy host and port (from an automatic proxy configuration file), however how do I obtain the username from the keychain from this? I know you can use SecKeychainAddInternetPassword to get the proxy password, but I don't know the username either. Is there a way to get the username AND the password? 回答1: I found it a little complicated. First, you have to ask the system configuration whether

Changing manually $(AppIdentifierPrefix) property?

不打扰是莪最后的温柔 提交于 2019-11-29 14:45:10
I had application uploaded on apple store. Now I am developing update version. But instead on working on existing project, i created new project with different name. When i finished i changed name and bundle identifier to match existing app. I tried uploading app to test flight but i got error "Invalid IPA: The keychain-access-group in the embedded.mobileprovision and your binary don't match." So I started browsing net for answers... What I have come up is to enable entitlements. I did, but to no avail... Then i edited entitlements, changing from this: $(AppIdentifierPrefix)com.xxxx to this:

Subversion on Mac - refuses to get password from keychain

给你一囗甜甜゛ 提交于 2019-11-29 14:27:51
问题 On Mac OS X Leopard - when I try and access a remote repository from Terminal it always asks for: 1. Password 2. Username 3. Password (again) with the message: "Authentication realm: http://svn.myserver.com:80 Subversion" I've checked and my credentials are being stored in Keychain and SVN has access to them. Why won't it use them? 回答1: I got this solved by recursively changing the owner of the subversion authentication directory: sudo chown -R myuser:staff ~/.subversion/auth/ (previous user

This certificate has an invalid issuer keychain

ぃ、小莉子 提交于 2019-11-29 14:26:05
问题 I do have private key(my_ca.key) and public key(my_cert.crt) which is signed by DigiCert. Now I want to generate the SSL certificate (version 3) and sign it by my private key . Here is the way I tried to do that. But when I export into keychain (Mac OS X). I have been getting error like this " This certificate has an invalid issuer keychain ". No idea how to solve this. Here my_cert.crt is extended from DigiCert High Assurance CA-3 and that one extended from DigiCert High Assurance EV Root CA

Share between an iOS extension and it's containing app with the keychain?

感情迁移 提交于 2019-11-29 12:35:07
问题 I understand I can share data between my share extension and its containing app by enabling app groups and using NSUserDefaults (see Sharing data between an iOS 8 share extension and main app). However, the data I am storing is sensitive, so I hoped to use the keychain. So the user would enter account information in the containing app, and then the share extension would read that data to perform the intended sharing action. Does anyone know if this is possible? My first crack at it suggests

iOS Keychain SecItemAdd returns -25243

情到浓时终转凉″ 提交于 2019-11-29 12:18:59
问题 I'm working on updating an iPhone application with a minor change in its default configuration. It's been awhile since I've built it last, though, and so I've upgraded Xcode to 4.2 and included iOS 5 support in the latest builds. When I go to test on the device, I get the following assertion error: 2011-11-02 20:57:18.869 RoseBandwidth[903:707] Tried to add item, got result: -25243 2011-11-02 20:57:18.870 RoseBandwidth[903:707] *** Assertion failure in -[KeychainItemWrapper writeToKeychain],

Storing email in keychain impossible (KeychainItemWrapper)

非 Y 不嫁゛ 提交于 2019-11-29 09:11:11
I'm using the ARCified version of KeychainItemWrapper available at github , and I can't get it to store both email and password. KeychainItemWrapper *keychainItem = [[KeychainItemWrapper alloc] initWithIdentifier:@"myApp" accessGroup:@"MY_APP.com.yourcompany.GenericKeychainSuite"]; [keychainItem setObject:[self.email dataUsingEncoding:NSUTF8StringEncoding] forKey:(__bridge id)kSecAttrAccount]; [keychainItem setObject:self.password forKey:(__bridge id)kSecValueData]; I works perfectly as long as I store an email... that don't have an at sign (@) it. Otherwise, I get the error *** Assertion

Why does git freeze on git-credential-osxkeychain sometimes?

一个人想着一个人 提交于 2019-11-29 08:01:14
When I do cd some-repo; git push origin master in my bash terminal, it doesn't ask me for username/password because I guess git has already saved that (it was so long ago that I don't remember the details of how that went down). I'm pushing to a GitHub repo as the remote origin. So I have a C++ program that does a fork and execl("/bin/bash", "/bin/bash", "-c", "cd some-repo; git push origin master", (char *)0); Then waits for the child bash process to finish. Sometimes it works just fine, but other times (seemingly randomly) it will freeze up. Looking at the running process hierarchy, I see: