2017-01-17 2 views
-1

Je me demande en préparant pour un Keychain item, quand convertiriez-vous NSString en NSData?iOS Keychain: NSDate vs NSString

Par exemple: Dans le code fourni par ce tutoriel http://hayageek.com/ios-keychain-tutorial/

Il déclare ce qui suit:

[dict setObject:encodedKey forKey:(__bridge id)kSecAttrAccount]; 

Cependant, dans le livre "Application Security iOS" par David Thiel utilisé comme suit:

[dict setObject:@"dthiel" forKey:(__bridge id)kSecAttrAccount]; 

donc, je suis tout à fait confus, quand dois-je convertir NSString à NSData et comment puis-je le dire?

Merci.

Répondre

0

Vous DEVEZ coder la valeur en tant que NSData.

Par exemple:

#define KeychainIdentifier @"keychain.access.identifier" 

- (void)setKeyValue:(NSString *)key value:(NSString *)value { 
    //The keychain identifier must be encoded as `NSData`. 
    NSData *keychainItemID = [KeychainIdentifier dataUsingEncoding:NSUTF8StringEncoding]; 


    //Build the query. We need to QUERY the keychain and check if the item exists. 
    //If it does, we will NOT be adding the item in the keychain. Note: You can "overwrite" the data if you want but for this example, I'm going to keep it simple and NOT do that. 
    //For this example, the item stored is a "GenericPassword". 
    //We will query for the existence of "one" item. 
    //This query will only return attributes because we are not FETCHING from the keychain. Just "checking/querying". 
    //Finally, the item is accessible when the device is unlocked. 
    NSMutableDictionary *query = [@{ 
            (id)kSecClass    : (id)kSecClassGenericPassword, 
            (id)kSecAttrGeneric  : keychainItemID, 
            (id)kSecMatchLimit  : (id)kSecMatchLimitOne, 
            (id)kSecReturnAttributes : (id)kCFBooleanTrue, 
            (id)kSecAttrAccessible : (id)kSecAttrAccessibleWhenUnlocked, 
            (id)kSecAttrAccount  : key 
            } mutableCopy]; 


    //Query the keychain and get all the item's attributes. 
    CFMutableDictionaryRef result = nil; 
    OSStatus error = SecItemCopyMatching((__bridge CFMutableDictionaryRef)query, (CFTypeRef *)&result); 

    if (error == errSecItemNotFound) { 
     //Item does not exist, add it to the keychain. 
     //To do that, we turn our query into an "INSERT". 
     //That means we need to remove the "return" key because we are no longer fetching/querying and returning attributes. We also have to remove the match limit. 
     //We also remove the match limit. 
     [query removeObjectForKey:(id)kSecMatchLimit]; 
     [query removeObjectForKey:(id)kSecReturnAttributes]; 

     //Now we encode the data to be stored in the keychain and then we submit our "INSERT" to the keychain. This will add the item in the keychain. 
     [query setObject:[value dataUsingEncoding:NSUTF8StringEncoding] forKey:(id)kSecValueData]; 

     error = SecItemAdd((__bridge CFMutableDictionaryRef)query, nil); 

     if (error == noErr) { 
      //Success. 
     } 
     else { 
      //Something went wrong. 
     } 
    } 
    else { 
     //Item already exists. 
    } 
} 
+0

Nous vous remercions de votre échantillon. Je me demandais, est-il nécessaire d'avoir ** kSecAttrGeneric **? Parce que je me rappelle que ** kSecClassGenericPassword ** n'a besoin que de ** kSecClass **, ** kSecAttrAccount ** et ** kSecAttrServer ** pour l'identification, est-ce correct? –

+0

@KwokPingLau; Ce n'est pas nécessaire. C'est optionnel. Comme vous pouvez le voir ici: http://stackoverflow.com/questions/11614047/what-makes-a-keychain-item-unique-in-ios La clé primaire de '' kSecClassGenericPassword'' est 'kSecAttrAccount et kSecAttrService' – Brandon