【问题标题】:Unable to identify iOS OSStatus Code无法识别 iOS OSStatus 代码
【发布时间】:2014-01-16 00:11:22
【问题描述】:

我在 iOS 应用程序中有一个非常奇怪的行为。 我从 iOS 6 切换到 iOS 7。在 iOS 6 中一切正常。

- (NSMutableDictionary *)newSearchDictionary:(NSString *)identifier {
    NSMutableDictionary *searchDictionary = [[NSMutableDictionary alloc] init];

    [searchDictionary setObject:(__bridge id)kSecClassGenericPassword forKey:(__bridge id)kSecClass];

    NSData *encodedIdentifier = [identifier dataUsingEncoding:NSUTF8StringEncoding];
    [searchDictionary setObject:encodedIdentifier forKey:(__bridge id)kSecAttrGeneric];
    [searchDictionary setObject:encodedIdentifier forKey:(__bridge id)kSecAttrAccount];
    [searchDictionary setObject:serviceName forKey:(__bridge id)kSecAttrService];

    return searchDictionary;
}

- (NSData *)searchKeychainCopyMatching:(NSString *)identifier {
    NSMutableDictionary *searchDictionary = [self newSearchDictionary:identifier];

    [searchDictionary setObject:(__bridge id)kSecMatchLimitOne forKey:(__bridge id)kSecMatchLimit];
    [searchDictionary setObject:(id)kCFBooleanTrue forKey:(__bridge id)kSecReturnData];

    CFDataRef dataRef;
    OSStatus status = SecItemCopyMatching((__bridge CFDictionaryRef)searchDictionary,
                                      (CFTypeRef *)&dataRef);

    if (status != errSecSuccess) {
#ifdef DEBUG
        NSLog(@"%s - No OSStatus errSecSuccess. Caused by SecItemCopyMatching", __PRETTY_FUNCTION__);
#endif
        return nil;
    }
    NSData *result = (__bridge_transfer NSData *)dataRef;
    return result;
}

当应用启动时,- (NSData *)searchKeychainCopyMatching:(NSString *)identifier 函数会从钥匙串中加载值。一切正常一段时间。但是在大约 15 次成功的值请求之后,我得到了一个错误。

操作系统状态码 -34018

SecItemCopyMatching 函数返回该错误代码。文档说

@result 结果代码。请参阅“安全错误代码”(SecBase.h)。

但在 SecBase.h 中只指定了这些 OSStatus 代码。

enum
{
    errSecSuccess                               = 0,       /* No error. */
    errSecUnimplemented                         = -4,      /* Function or operation not implemented. */
    errSecIO                                    = -36,     /*I/O error (bummers)*/
    errSecOpWr                                  = -49,     /*file already open with with write permission*/
    errSecParam                                 = -50,     /* One or more parameters passed to a function where not valid. */
    errSecAllocate                              = -108,    /* Failed to allocate memory. */
    errSecUserCanceled                          = -128,    /* User canceled the operation. */
    errSecBadReq                                = -909,    /* Bad parameter or invalid state for operation. */
    errSecInternalComponent                     = -2070,
    errSecNotAvailable                          = -25291,  /* No keychain is available. You may need to restart your computer. */
    errSecDuplicateItem                         = -25299,  /* The specified item already exists in the keychain. */
    errSecItemNotFound                          = -25300,  /* The specified item could not be found in the keychain. */
    errSecInteractionNotAllowed                 = -25308,  /* User interaction is not allowed. */
    errSecDecode                                = -26275,  /* Unable to decode the provided data. */
    errSecAuthFailed                            = -25293,  /* The user name or passphrase you entered is not correct. */
};

这些值不会被覆盖,已经检查过。

最后但并非最不重要的是搜索字典:

编辑 - 新信息

我调试了一整天,发现了一些消息。我正在下载一个包含可执行包的 Zip 文件。这是一个内部应用程序,因此无需担心审查指南中的第 2.7 点和第 2.8 点。成功加载捆绑包后,出现权利错误。

NSBundle *bundle = nil;
NSError *error = nil;
bundle = [[NSBundle alloc] initWithPath:bundlePath];
if (!bundle) {
    return nil;
}

// Here i can access the keychain as usually
[bundle loadAndReturnError:&error];
// Well here it suddenly doesn't work anymore
// error is also nil

嗯,里面的捆绑代码不使用钥匙串。可能这是某种安全逻辑?有什么线索吗?

【问题讨论】:

标签: ios iphone security


【解决方案1】:

此错误表明您的应用权利存在问题。找到this:原因通常是应用的entitlements中的App Identifier Prefix与provisioning profile中的App Identifier Prefix不匹配。

要进行验证,请使用协同设计工具查看您应用的权利:

codesign -d --entitlements - MyApp.app/

然后,将 App Identifier Prefix 与配置文件中的进行比较:

cat MyApp.app/embedded.mobileprovision

【讨论】:

  • 还是一样的行为。刚开始可以,但经过几次尝试,它失败了
  • 或许these guys可以帮到你
  • 我将创建一个产生该行为的示例项目并将其上传。
猜你喜欢
  • 2017-11-19
  • 1970-01-01
  • 2022-10-22
  • 2020-10-13
  • 2012-03-06
  • 2014-09-21
  • 2015-07-12
  • 1970-01-01
  • 1970-01-01
相关资源
最近更新 更多