1个Keystore签署所有应用程序或每个应用程序1个？ [英] 1 Keystore to sign all apps or 1 per app?

问题描述

我想知道哪个更受欢迎，有1个keystore签署你发布的所有应用程序，并将该keystore复制到云端和本地以保证安全，或为每个提交的新应用程序生成一个新的密钥存储库，以及保存它们的所有副本？

似乎更容易拥有1个密钥存储区，但是尽管重复了它，但我担心它会被损坏并且无法访问所有。

这种情况最好的办法是什么？

如果您使用相同的密钥库，那么使您的应用程序一起工作会更容易。通过让他们使用相同的密钥签名，您可以使用共享的UID（不是真正推荐的），也可以使用基于签名的权限。这将使得导出某些数据或功能成为可能，并且仅限于访问您自己的应用程序（使用ContentProvider或远程服务）。缺点是，如果你失去了密钥，你将不得不重新发布所有的应用程序。

如果您使用单独的密钥存储库，将应用程序转移给其他人更容易（给他们密钥库和密码）。此外，如果您丢失/损坏密钥库，则只需重新发布一个应用。

接下来选择，但我会说：使用相同的密钥存储并进行大量备份。我也会在不同的位置使用物理媒体（CD等），而不是云，但这也是您的选择。

I am wondering which is the more popular option, Having 1 keystore to sign all the apps you publish, and duplicating that keystore into the cloud and locally to keep it safe, or generating a new keystore for every new app submitted, and keeping copies of all of them?

It seems easier to have 1 keystore for everything, but despite duplicating it, im afraid of it getting corrupted and loosing access to all of the apps.

Whats the best approach for this situation?

解决方案

If you use the same keystore, it will be easier to make your apps work together. By having them signed with the same key, you can use a shared UID (not really recommended), or use signature based permissions. That would make it possible to export certain data or functionality and restrict access to your own apps only (using a ContentProvider or a remote service). The downside is, that if you loose the key, you'll have to republish all apps.

If you use separate keystores, it's easier to transfer an app to someone else (give them keystore and password). Additionally, you need to re-publish only one app if you lose/corrupt the keystore.

Take you pick, but I'd say: use the same keystore and make lots of backups. I would also use physical media (CD, etc) in separate locations, rather then the 'cloud', but that's your choice too.

这篇关于1个Keystore签署所有应用程序或每个应用程序1个？的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！