![]() ![]() However, most organizations use a single identity for a given platform and purpose. Also, you typically have different identities for iOS and macOS apps. You can use more than one signing identity, each for its own purpose, such as one for beta seeds and one for final, released products. The simple act of code signing does not require a certificate authority’s signature on your certificate, but your signature is much more useful this way because anyone encountering your signature can be confident of its origin. The certificate is not secret, and is itself generally signed by a certificate authority, which effectively vouches for your identity. The digital certificate has a usage extension that enables it to be used for signing, and it contains the public key that complements your private key. The private key is an encryption key that only you have, making it impossible for anyone to forge your signature, as long as you keep the key secure. You sign code using a code signing identity, which consists of a private key plus a digital certificate. Read this chapter to gain a better understanding of what Xcode does on your behalf, or to handle special cases where you need to intervene in the code signing process. Letting Xcode handle code signing is generally the simplest and safest choice, because Xcode is designed with best practices built in. Typically, Xcode handles most code signing tasks for you, helping you manage your code signing identity, and applying your code signature to apps that you build and distribute.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |