重用开发 CSR 进行分发证书
因此，我为我的 iPhone 应用程序创建了一个开发证书，在此过程中，我使用 Keychain Access Certificate Assistant 将 CSR 作为 CertificateSigningRequest.certSigningRequest 文件保存在计算机硬盘上。在我看来，Apple 还要求生成一个完全相同的文件并将其保存到硬盘上以请求分发证书。我可以重复使用为开发而创建的请求文件来请求分发证书吗？我知道我将被允许使用该文件，但这会在以后以某种方式产生问题吗？
So, I've created a development certificate for my iPhone app, and in the process I saved a C.S.R as a CertificateSigningRequest.certSigningRequest file on the computer hard drive with Keychain Access Certificate Assistant. It seems to me that Apple asks for an exactly same file to be generated and saved onto the hard drive for requesting a distribution certificate as well. Can I reuse the request file I already created for development to request a distribution certificate? I know I'll be allowed to use the file, but will this create a problem later down the road somehow?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
简短回答
您可以，但是您的开发证书和分发证书都将绑定到相同的公钥/私钥对（在您创建证书请求时生成）。
详细信息
拥有与该证书关联的私钥的任何人都可以使用该证书对应用程序进行签名。
应用程序必须使用开发证书进行签名才能在设备上运行和调试。
应用程序必须使用分发证书进行签名才能提交到App Store。 （分发签名的应用程序也可以在设备上运行，但您无法将调试器附加到它们。）
在较大的组织中，每个开发人员都有自己的开发人员证书（带有自己的公钥/私钥对）。此外，还有一个分发证书（也有自己的公钥/私钥对）。
这使得组织能够：
如果您是一名个人开发者并且不打算发展工作室，那么这一切对您来说可能都不重要，因为您将既是开发者又是提交者。
Short Answer
You can, but then both your development and distribution certificates will be tied to the same public/private key pair (which is generated when you create the certificate request).
Details
Applications can be signed with a certificate by anyone who has the private key with which that certificate is associated.
Applications must be signed with a development certificate to run and debug on a device.
Applications must be signed with a distribution certificate to be submitted to the App Store. (Distribution-signed applications can also be run on a device, but you can't attach a debugger to them.)
In larger organizations, each developer has their own developer certificate (with their own public/private key pair). Additionally, there's one distribution certificate (also with its own public/private key pair).
This allows the organization to:
If you're an individual developer and not trying to grow a studio, probably none of this will matter much to you because you're going to be both the developer and submitter.