Using your own self-signed certificates.
使用自己的自签名证书。
In these examples, you'll use a self-signed certificate.
在这些例子中，我们将使用自己签名的证书。
The self-signed certificated is saved in the indicated location.
自签名证书将保存到指定位置。
Figure 10 also shows the details of the ca's self-signed certificate.
图10还显示了CA的自签名证书的详细信息。
Use environment-specific tools to generate a self-signed certificate.
使用特定于环境的工具生成一张自签署的证书。
Select Personal certificates and click Create a self-signed certificate.
选择personalcertificates并单击Createa self - signed certificate。
Create a self-signed certificate using the administrative console as follows.
使用管理控制台创建自签名证书，具体操作如下。
Implementing SSL with self-signed certificates requires the administrator to.
实现带有自签名证书的SSL需要管理员执行以下操作。
Signature Algorithm: Algorithm to be used to sign the self-signed certificate.
SignatureAlgorithm：签署自签名证书所使用的算法。
By default, Community Edition Certification Authority USES a self-signed certificate.
缺省情况下，CommunityEdition证书颁发机构使用一个自签名证书。
For testing or internal use, you can instead generate your own self-signed certificates.
如果用于测试或内部用途，可以生成您自己的自签名证书。
The trust store entry for a self-signed certificate matches one and only one certificate.
自签名证书的信任存储区项与一个且仅与一个证书匹配。
For WebSphere Application Server, we will use a self-signed certificate, called jmsclient.
对于WebSphereApplicationServer，我们则使用一个自签署证书，名为jmsclient。
For these reasons, I prefer self-signed certificates and these are what will be discussed here.
基于上述原因，我倾向于使用自签名证书，这也是本文将讨论的证书。
With the information in Figure 11, we know the self-signed certificate's validity is 02-13-2009.
根据图11中提供的信息，我们知道自我签名证书的有效期是 02-13-2009。
Repeat the steps for CommandQmgr and CoordinationQmgr to create all three self-signed certificates.
对Command Qmgr和Coordination Qm gr重复以上步骤，创建所有的三个自签名证书。
This means you can verify exactly one certificate — the self-signed certificate created for the peer.
这意味着您可以准确地检验一个证书——为对方创建的自签署证书。
For this example configuration in this article, we are using the self-signed certificate in TXSeries.
对于本文中的示例配置，我们使用了TXSeries中的自签名证书。
Now walk through creating a self-signed certificate for distribution to a server using iKeyman V7.0.3.28.
下面使用iKeymanV7.0.3.28 来逐步地创建一个自签名的证书以便分发到服务器。
The quickest way to set up a keystore is to create your own certificate, called a self-signed certificate.
设置密钥存储库的最快方法是创建您自己的证书，称为自签名证书。
You need to create the trust store into which the extracted self-signed server certificate will be imported.
需要创建一个信任存储，用于导入已提取的自签名服务器证书。
It USES a default signature algorithm, SHA1 with DSA, to create a self-signed certificate valid for 180 days.
它使用默认的签名算法(SHA1和DSA)创建一个带有自我签名的证书，有效期为180天。
Since this example USES a serial number '0' for the ca's self-signed certificate, this field shows a value of 0.
由于本例中对CA的自签名证书使用序列号“0”，因此此字段显示的值为0。
For the demonstration, we will use self-signed certificate for transferring the key from the server to the client.
为了演示我们将使用自签名证书将密匙从服务器传输到客户端。
The example code for this article USES two such self-signed certificates, one for the client and one for the server.
本文的示例代码使用了两个这种自签名证书，一个用于客户机，一个用于服务器。
Since this application is not going to be deployed to a wide user base, we'll create a self-signed test certificate.
因为我们不准备将该应用程序部署给广大的用户，所以创建了一个自签名的测试证书。
I should mention at this point that self-signed certificates work in exactly the same way as ca signed certificates.
这里必须指出的是，自签名证书与CA签名证书的工作方式完全相同。
This means that each can be used to verify exactly one certificate -- the self-signed certificate created for the peer.
这意味着只能使用它们检验一个证书 ——为对方创建的自签名证书。
If the key database contains only self-signed certificates, there is no chance of matching multiple unintended certificates.
如果该密钥数据库仅包含自签名证书，就不可能匹配多个非预期证书。
Note that while both tools allow the user to generate self-signed certificates, neither tool allows the user to sign a certificate.
请注意，虽然两个工具都允许用户生成自签署的证书，但是它们都不允许用户签署证书。
应用推荐