For this article, I used IBM JRE 1.3.1 and JSSE 1.0.3.
针对本文，我使用了IBMJRE1.3.1和JSSE1.0.3。
First, we need to obtain a JSSE provider (see Resources).
首先我们需要获得JSSE提供程序(请参阅参考资料)。
All this is done transparently for you by the JSSE runtime.
这一切通过JSSE运行时对您都是透明的。
IBM makes no claim of interoperability with other JSSE providers.
IBM没有声明与其它JSSE提供方的互操作性。
Configuring and installing the IBM JSSE: do I need to do anything?
配置及安装IBMJSSE：我需要做什么吗？
The J2SE 1.4 SDK comes with JSSE already installed and configured.
J2SE 1.4SDK提供了已安装和配置的JSSE。
In the main content pane, click the New JSSE repertoire button (Figure 3).
在主内容窗格中，单击newJSSErepertoire按钮(图3)。
We'll leave this parameter null, allowing JSSE to use the default — and secure!
我们让该参数为null，这样允许JSSE使用缺省的—并且安全的！
By specifying "SSL" we allow JSSE to default to the highest level it can support.
通过指定“SSL ”，我们允许jsse缺省至它能支持的最高级别。
By constructing a customized socket factory we can customize the behavior of JSSE.
通过构造一个定制的套接字工厂，我们可以定制JSSE的行为。
The JSSE prototypes pointed to a more complex API than we'd originally anticipated.
JSSE原型指出JSSE是一个比我们最初预期的更加复杂的API。
The SSLCIPHERSUITE value is a valid CipherSuite implemented by the JSSE implementation.
SSLCIPHERSUITE值是由JSSE实现实现的有效的密码套件。
Support for custom JSSE trust and key managers enables more control of the SSL handshake.
支持自定义JSSE信任和密钥管理器，从而允许对SSL握手进行更多的控制。
If you're using J2SE 1.2 or 1.3 you will need to obtain a JSSE implementation and install it.
如果您正在使用J2SE 1.2或1.3，则需要获取一个JSSE实现并安装它。
The JSSE runtime will ensure that, but it doesn't guarantee that the server is the right server.
JSSE运行时将会确保这一点，但它无法保证服务器是正确的服务器。
If you are curious, there are a number of providers here, most of which are not related to JSSE.
如果您很好奇，那么此处存在大量的提供方，大多数都与JSSE无关。
We still let JSSE use its default SecureRandom, however, by passing null as the third parameter.
但是，我们仍然让JSSE通过传递null作为第三个参数来使用它缺省的SecureRandom。
In my installation, it always seems to pick Bob's certificate, but your JSSE may behave differently.
在我的安装中，似乎始终选取bob的证书，但是您的JSSE的行为可能有所不同。
This article will demonstrate how to use the JSSE interface to tailor the properties of an SSL connection.
本文将演示如何使用JSSE接口定制SSL连接的属性。
While JSSE does start the handshake automatically, it only does so when data is first sent across the socket.
尽管JSSE确实会自动启动握手，但是仅当数据首次通过套接字发送时它才这样做。
Because this article focuses on more advanced topics, it is assumed that you have prior experience with JSSE.
由于本文着重讲述更高级的主题，因此假定您已经具备了JSSE的使用经验。
JSSE 1.0.3 includes installation instructions for adding the package to the JRE, which I will not repeat here.
JSSE1.0.3包括用于将包添加到JRE的安装说明，在此我就不重复了。
The JSSE API only became a standard with J2SE 1.4, and slight variations exist between earlier JSSE implementations.
JSSEAPI只是J2SE 1.4的一项标准，并且早期的JSSE实现之间存在略有不同的变体。
By the same token, the server must have its private key locally protected and make it accessible to the JSSE runtime.
出于同样的机制，服务器必须本地保护它的私有密钥并且使其能够访问JSSE运行时。
Again, the tutorial "Using JSSE for secure socket communication" can provide more detail on these individual options.
同样，教程“Using JSSE forsecuresocketcommunication”可以提供这些单个选项的更多细节。
No further install is required on your part; in fact, replacing JSSE or JCE implementations from other sources is forbidden.
您的部分中无需进一步的安装；事实上，禁止替换其他来源的JSSE或JCE实现。
Wherever necessary, I'll highlight the changes needed to make the examples work with Sun's JSSE implementation for J2SE 1.2 and 1.3.
必要的时候，我会强调使示例与J2SE 1.2和 1.3 的SunJSSE实现协同工作所必需的更改。
Regardless of how you choose to implement the advanced JSSE customizations demonstrated here, none of them should be approached carelessly.
不管您如何选择实现本文演示的高级JSSE定制，任何一个都不是随便就可以实现的。
Javax.net.ssl is the most important of the three statements; it contains most of the core JSSE classes and we need it to do any work with SSL.
ssl是三条语句中最重要的；它包含大多数核心jsse类，我们要用它处理任何和ssl有关的工作。
When using JSSE for SSL communication, one needs to maintain the set of trusted signer certificates in a local store, hence the name truststore.
当将JSSE用于SSL通信时，需要在本地存储中维护一套信任的签名者的证书，由此得名信任库。
应用推荐