重用证书签名请求对苹果推送服务 [英] Reusing Certificate Signing Request for Apple Push Service

问题描述

企业社会责任的建立将促使
  同时钥匙串访问
  生成公钥和私钥
  对。您的私人密钥存储在
  您的Mac在日......

The creation of a CSR will prompt Keychain Access to simultaneously generate a public and private key pair. Your private key is stored on your Mac in th....

所以每次iOS应用可以有两种环境设置推送通知，开发和生产。

So every iOS app can have two environments set up for push notifications, development and production.

什么是重用为开发和督促环境相同的CSR（因此相同的私钥？）危害？这甚至可能？

What is the harm in reusing the same CSR (and thus the same private key?) for both dev and prod environments? Is this even possible?

在一个类似的效果，这将是在不同的应用程序使用同一个企业社会责任的伤害。

In a similar effect what would be the harm of using the same CSR across the different apps.

基本上我想，当我安装将处理推在我结束通知的服务器上的所需的元素来管理一个单一的私有密钥。

Basically I want to manage a single private key when I install the required elements on the server that will handle push notifications on my end.

感谢

推荐答案

我用我所有证书相同的公钥/私钥。我曾经结束有不同的私人/公共密钥的唯一情况是当客户要我来管理他们的整个苹果账号和证书生成。

I use the same private/public key for all my certificates. The only time I ever end up having different private/public keys is when a client wants me to manage their whole Apple account and certificate generation.

这篇关于重用证书签名请求对苹果推送服务的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！