将 PEM 导入 Java 密钥库
我正在尝试连接到需要我进行身份验证的 SSL 服务器。为了通过 Apache MINA 使用 SSL,我需要一个合适的 JKS 文件。但是,我只得到了一个 .PEM 文件。
我将如何从 PEM 文件创建 JKS 文件?
如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱,如果其他用户或者作者回复了您的评论,将不能在第一时间通知您!
我正在尝试连接到需要我进行身份验证的 SSL 服务器。为了通过 Apache MINA 使用 SSL,我需要一个合适的 JKS 文件。但是,我只得到了一个 .PEM 文件。
我将如何从 PEM 文件创建 JKS 文件?
由于您还没有绑定你的真实邮箱,如果其他用户或者作者回复了您的评论,将不能在第一时间通知您!
接受
或继续使用网站,即表示您同意使用 Cookies 和您的相关数据。
发布评论
评论(14)
首先,将您的证书转换为 DER 格式:
然后,将其导入密钥库:
First, convert your certificate in a DER format :
And after, import it in the keystore :
如果您只想将 PEM 格式的证书导入密钥库,keytool 将完成这项工作:
If you only want to import a certificate in PEM format into a keystore, keytool will do the job:
如果您需要一种简单的方法来在 Java 中加载 PEM 文件而无需处理外部工具(opensll、keytool),这里是我在生产中使用的代码:
玩得开心。
If you need an easy way to load PEM files in Java without having to deal with external tools (opensll, keytool), here is my code I use in production :
Have fun.
我开发了 https://github.com/alastairmccormack/keyutil 它将 PEM 证书直接导入到Java 密钥库。其主要目的是导入多部分 PEM 操作系统证书包,例如 ca-bundle.crt。这些通常包括 keytool 无法处理的标头。
I've developed https://github.com/alastairmccormack/keyutil which imports PEM certificates straight into a Java keystore. Its primary purpose is to import a multi-part PEM Operating System certificate bundles such as ca-bundle.crt. These often includes headers which keytool cannot handle.
就我而言,我有一个 pem 文件,其中包含两个证书和一个用于相互 SSL 身份验证的加密私钥。
所以我的 pem 文件看起来像这样:
这是我所做的
将文件拆分为三个单独的文件,以便每个文件只包含一个条目,
以
---BEGIN..
开始并以---END..
行结束。假设我们现在有三个文件:cert1.pem
、cert2.pem
和pkey.pem
。使用 openssl 和以下语法将
pkey.pem
转换为 DER 格式:请注意,如果私钥已加密,您需要提供密码(从原始 pem 文件的供应商处获取)转换为 DER 格式,
openssl
会要求您输入如下密码:“输入pkey.pem
的密码:”。如果转换成功,您将获得一个名为
pkey.der
的新文件。创建新的 java 密钥库并导入私钥和证书:(
可选)验证新密钥库的内容:
密钥库类型:JKS
密钥库提供程序:SUN
您的密钥库包含 3 个条目:
cn=...,ou=...,o=.., 2014 年 9 月 2 日,trustedCertEntry,
证书指纹 (SHA1):2C:B8: ...
importkey,2014 年 9 月 2 日,PrivateKeyEntry,
证书指纹 (SHA1):9C:B0: ...
cn=...,o=....,2014 年 9 月 2 日,trustedCertEntry,
证书指纹 (SHA1): 83:63: ...
(可选)针对 SSL 服务器测试新密钥存储中的证书和私钥:
(您可能希望将调试作为 VM 选项启用: -Djavax.net.debug=all )
最后,如果计划使用 HttpsURLConnection ,请使用它注册您的证书:
In my case I had a pem file which contained two certificates and an encrypted private key to be used in mutual SSL authentication.
So my pem file looked like this:
Here is what I did
Split the file into three separate files, so that each one contains just one entry,
starting with
---BEGIN..
and ending with---END..
lines. Lets assume we now have three files:cert1.pem
,cert2.pem
, andpkey.pem
.Convert
pkey.pem
into DER format using openssl and the following syntax:Note, that if the private key is encrypted you need to supply a password( obtain it from the supplier of the original pem file ) to convert to DER format,
openssl
will ask you for the password like this: "enter a passphrase forpkey.pem
: ".If conversion is successful, you will get a new file called
pkey.der
.Create a new java keystore and import the private key and the certificates:
(optional) Verify the content of your new key store:
Keystore type: JKS
Keystore provider: SUN
Your keystore contains 3 entries:
cn=...,ou=...,o=.., Sep 2, 2014, trustedCertEntry,
Certificate fingerprint (SHA1): 2C:B8: ...
importkey, Sep 2, 2014, PrivateKeyEntry,
Certificate fingerprint (SHA1): 9C:B0: ...
cn=...,o=...., Sep 2, 2014, trustedCertEntry,
Certificate fingerprint (SHA1): 83:63: ...
(optional) Test your certificates and private key from your new key store against your SSL server:
( You may want to enable debugging as an VM option: -Djavax.net.debug=all )
Finally register your certificates with HttpsURLConnection if plan to use it:
我使用 Keystore Explorer
I used Keystore Explorer
我总是忘记如何做到这一点,因为这是我偶尔做的事情,这是一种可能的解决方案,而且它确实有效:
执行以下两行代码:
如果在 Java SE 环境中执行,请添加以下选项:
或者将以下内容添加到 java 代码中:
步骤 2 的另一个选项是仅使用
keytool
命令。下面是一个带有证书链的示例:I'm always forgetting how to do this because it's something that I just do once in a while, this is one possible solution, and it just works:
Execute the two following lines of code:
If executing in Java SE environment add the following options:
Or add the following to the java code:
The other option for step 2 is to just using the
keytool
command. Bellow is an example with a chain of certificates:OpenJDK
keytool
现在可以本地处理 PEM 证书(并且已经有几个版本了,但我不确定从什么时候开始)。keytool
建议不要像任何其他密钥库一样指定 cacerts 文件路径,而是使用-cacerts
选项。因此,适用于 OpenJDK 18(可能还有许多早期版本)的命令行是:
OpenJDK
keytool
handles PEM certificates natively now (and has been for a few releases but I'm not sure since when).keytool
recommends against specifying the cacerts file path like any other keystore but using-cacerts
option instead.So the command line which works with OpenJDK 18 (and probably many earlier versions) is:
还有一个 GUI 工具,允许可视化 JKS 创建和证书导入。
http://portecle.sourceforge.net/
There is also a GUI tool that allows visual JKS creation and certificates importing.
http://portecle.sourceforge.net/
我从互联网上得到的。它对于包含多个条目的 pem 文件非常有效。
I got it from internet. It works pretty good for pem files that contains multiple entries.
尽管这个问题已经很老了并且已经有很多答案,但我认为提供一个替代方案是值得的。使用本机 java 类使得仅使用 pem 文件变得非常冗长,并且几乎迫使您想要将 pem 文件转换为 p12 或 jks 文件,因为使用 p12 或 jks 文件要容易得多。我想为任何想要替代已提供答案的人提供帮助。
GitHub - SSLContext Kickstart
我需要在这里提供一些免责声明,我是库维护者
Although this question is pretty old and it has already a-lot answers, I think it is worth to provide an alternative. Using native java classes makes it very verbose to just use pem files and almost forces you wanting to convert the pem files into p12 or jks files as using p12 or jks files are much easier. I want to give anyone who wants an alternative for the already provided answers.
GitHub - SSLContext Kickstart
I need to provide some disclaimer here, I am the library maintainer
如果您想在 Android 上执行此操作,可以将一些小的调整添加到 PEMImporter 类中>这个很好的答案。总结一下:
首先我使用 Android Studio 翻译成 Kotlin(这不是必需的,我只是更喜欢它)。原始类包含所有静态方法,因此这会产生一个命名对象。
javax.xml.bind.DatatypeConverter
已从版本 11 中的 java 核心中删除。尽管您仍然可以导入它(在 gradle 中:implementation("javax.xml.bind:jaxb-api:2.4.0-b180830.0359"
),这在Android上不起作用,使用java.util.Base64更简单
它执行的任务(即,将 base64 转换为字节)。输出是相同的(尽管您需要修剪原始 PEM 数据中的行结尾)。将
SunX509
和JKS
替换为PKIX
。仅在第一种情况下才有必要,而在第二种情况下可能无关紧要;如果您像此处所做的那样使用已初始化的PrivateKey
等对象填充KeyStore
,我认为它没有任何意义。事实上,我在createKeyStore
中使用了getDefaultAlgorithm()
代替了“JKS”,尽管当前默认值是“jks”,但密钥存储在中工作得很好。使用
。PKIX
作为算法创建的 KeyManagerFactory我还应该注意,我没有使用
createSSLFactory
方法,而是使用createKeyStore()
的输出来初始化KeyManagerFactory
并提取 < code>KeyManagers 用于初始化SSLContext
:这里的密码可能并不重要,因为
PEMImporter
使用已经未加密的密钥数据 -除非您想将PrivateKey
写回文件(我认为getEncoded()
是朝着这个方向迈出的一步,但我从来没有需要这样做)。它只需与上述两种用途相匹配即可。我还添加了 RSA PRIVATE KEYS 的捕获,事实证明,它是
与第一行没有“RSA”的 PEM 密钥不同;这是我以前没有意识到的微妙之处。前者是PKCS #1,后者是PKCS #8;您应该能够使用通常使用的任何工具来处理这些问题(例如,在使用
certtool
创建密钥时,使用--pkcs8
)。请注意,这并不意味着 PKCS #8 密钥可能不是基于 RSA 的,它只是与用于存储和提取密钥数据的协议有关。这是我在 Kotlin 中使用的
PEMImporter
Android 版本:If you want to do this on Android, there are a few minor tweaks that can be added to the
PEMImporter
class from this great answer. To summarize those:First I used Android Studio to translate into Kotlin (this is not necessary, I just prefer it). The original class contained all static methods, so this resulted in a named object instead.
javax.xml.bind.DatatypeConverter
was removed from the java core in version 11. Although you can still import it (in gradle:implementation("javax.xml.bind:jaxb-api:2.4.0-b180830.0359"
), this does not work on Android and it is simpler to usejava.util.Base64
for the tasks it performed (namely, translating base64 to bytes). The output is identical (although you need to trim line endings in the raw PEM data).Replace
SunX509
andJKS
withPKIX
. It is only necessary in the first case, and in the second case probably inconsequential; I do not think it has any significance if you are populating aKeyStore
with already initializedPrivateKey
etc. objects as is done here. I in fact usedgetDefaultAlgorithm()
in place of "JKS" increateKeyStore
, and although that default is currently "jks", the key store worked fine in aKeyManagerFactory
created withPKIX
as the algorithm.I should also note that I am not using the
createSSLFactory
method and am instead using the output ofcreateKeyStore()
to initialize aKeyManagerFactory
and extractKeyManagers
used to initialize anSSLContext
:It probably doesn't matter much what the password is here since the
PEMImporter
works with already unencrypted key data -- unless you want to write aPrivateKey
back to a file (I presumegetEncoded()
is a step in that direction but I've never had need to do this). It just has to match in the two uses above.I also added a catch for
RSA PRIVATE KEYS
, which, as it turns out, arenot the same as PEM keys with no "RSA" in the first line; a subtlety I was previously unaware of. The former are PKCS #1, the latter PKCS #8; you should be able to use whatever tool you normally use to deal with these (eg., when creating keys with
certtool
, use--pkcs8
). Note that doesn't mean PKCS #8 keys aren't potentially RSA based, it's just about the protocol used to store and extract the key data.Here's my Android version of
PEMImporter
in Kotlin:如果您有一个包含多个证书的 pem 文件,您可以使用脚本来提取它们并一次添加一个,如下所示:
If you have a pem file with multiple certificates you can use a script to extract them and add them one at a time something like:
这是动态构建商店的 Scala 代码下方。
它可以这样使用:
我正在使用通过 Let's Encrypt 为 Google 域获得的证书进行测试。
它运行良好,但不要忘记使用“fullchain.pem”作为证书文件,使用“privkey.pem”作为私钥。
谢谢大家。
This is below the Scala code to build a store on the fly.
It can be used this way:
I am testing with a certificate I got for a Google Domain via Let's Encrypt.
It works well, but do not forget to use the "fullchain.pem" for the certificates file, and the "privkey.pem" for the private key.
Thanks to everyone.