博客内容讲述了在使用KeychainAccess时，由于其用户界面（UX）的缺陷，导致搜索证书时匹配到的是与私钥关联的证书而非期望的证书，从而持续导出错误的证书。作者在识别并修正这个问题后，解决了导入问题和签名身份丢失私钥的提示。
We identified in our case that we were exporting the WRONG certificate, because Keychain Access has a UX deficiency in that when you use the search box, you don't see certificates with a name matching what you searched for, you see certificates tied to PRIVATE KEYS with a name that matches what you searched for.
Because of this confusing UX of Keychain access, we were continually exporting the wrong certificate (but had convinced ourselves it was right because the name matched). Once we identified it as the right certificate, our import problem & signing identity missing private keys messages went away
扫一扫
被折叠的 条评论
为什么被折叠?
到【灌水乐园】发言
