适用于多种操作系统的 BlackBerry 代码签名
我想做几件事，想知道它们是否可能，如果可以，该怎么做。
我打算制作一个虚拟机来运行代码签名。这样，如果我的计算机死机，我可以通过简单地在新系统中运行虚拟机来最大程度地减少停机时间。我知道代码密钥与运行它们的机器相关联。如果有人在虚拟机中进行了代码签名并将虚拟机切换到另一台物理机，请告诉我密钥是否继续有效。
我还想在虚拟机中运行多个 JDE 来为不同操作系统签名代码。据我了解，代码签名使用位于每个 JDE 目录中的代码签名应用程序。是否可以在同一系统上运行多个 JDE，并能够为特定操作系统签署代码（我计划在代码签名虚拟机上使用 JDE 4.2.1、4.5、4.6.1、4.7，最终为 5.0） ）。如果是这样，我是否需要多个密钥（每个 JDE 版本一个）或者是否有某种方法可以为不同版本使用相同的密钥？
感谢您回答这个问题的任何帮助。
I wanted to do a couple of things and am wondering if they're possible, and if so, how to do them.
I was going to make a Virtual Machine to run code-signing in. That way if my computer dies I can hopefully minimize downtime by simply running the VM in a new system. I know the code keys are tied to the machine they're run on. If anyone has done code signing in a VM and switched the VM to another physical machine please let me know if the keys continued to work or not.
I also wanted to run more than one JDE in the VM to sign code for different OSes. From what I understand the code signing uses a code signing app located in each JDE's directory. Is it possible to run multiple JDE's on the same system and be able to sign code for a specific OS (I'm planning on having JDE 4.2.1, 4.5, 4.6.1, 4.7, and eventually 5.0 on the code-signing VM). If so, do I need multiple keys - one for each JDE version - or is there some way to use the same keys for the different versions?
Thanks for any help in answering this.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（2）
当然可以在机器之间迁移密钥 - 我们有一组已在 Windows XP、Mac OS X 和 Linux 机器上使用的密钥。
如果您在手动使用签名工具后查看
BlackBerry JDE Component Package XYZ\bin目录之一，您将看到以下文件：需要。只需将它们复制到备用 JDE 树中的等效位置，您就可以将它们用于“多个目标”。我没有在 4.7.0 上这样做过，但在 4.6.0、4.5.0、4.3.0 和 4.2.1 上这样做过。 运行签名者
我们使用我不确定其他方法是否有效来
。迁移到类似 UNIX 的构建机器会带来一些麻烦，这就是为什么我认为 RIM 说密钥不可移植 - SignatureTool 应用程序似乎无法检测操作系统特定的目录路径分隔符。结果是，它会在这些位置查找关键文件，甚至在 UNIX 计算机上（注意反斜杠）：
例如，当您认为它会查找
bin/sigtool.csk时。解决方案就是使用这些指向实际文件的名称创建软链接。在组件包顶级目录中，我们执行以下操作：我仅登录了一个虚拟机 - Windows XP 映像。效果很好。
It's certainly possible to migrate the keys between machines - We have a set of keys that have been used on Windows XP, Mac OS X and Linux machines.
If you look in one of your
BlackBerry JDE Component Package X.Y.Z\bindirectories after you've used the signing tool manually you'll see these files:These are the files you need. Simply copy them to the equivalent location in the alternate JDE trees and you will be able to use them for 'multiple targets'. I've not done this with 4.7.0, but have with 4.6.0, 4.5.0, 4.3.0, and 4.2.1. We're run the signer using
I'm not sure whether other methods would work.
Migrating to UNIX-like build machines introduces a twist, and this is why I think RIM say the keys are not portable - the SignatureTool application seems to not detect the operating system-specific directory path separator character. The upshot is that it looks for the key files in these locations, even on a UNIX machine (note the backslashes):
when you'd think it would look for
bin/sigtool.cskfor example. A solution for this is simply to create soft links with these names that point to the actual files. In the component package top-level directory we do this:I've only signed in one VM - a Windows XP image. It worked fine.
另一个解决方案是使用 SignatureTool 修复问题（仅供参考，RAPC 也有类似问题），如本博客所述：
http://www.slashdev.ca/2008/03/16/using-sigtool-in-linux/
Another solution is to just fix the problem with SignatureTool (FYI, RAPC has similar issues), as this blog describes:
http://www.slashdev.ca/2008/03/16/using-sigtool-in-linux/