基于java的仿QQ即时聊天程序的设计与实现外文翻译资料

Rivest Shamir Adleman (RSA)

Authentication and key exchange

512 and larger

Rivest Cipher 4 (RC4)

Bulk encryption

128
128 (40 effective)

Data Encryption Standard (DES)

Bulk encryption

64 (56 effective)
64 (40 effective)

Triple DES (3DES)

Bulk encryption

192 (112 effective)

Advanced Encryption Standard (AES)

Bulk encryption

256 ^{武汉理工大学}

^英文翻译

^{专业班级： 信计1202}

^{指导教师： 陆济湘}

^Introduction

^{Data that travels across a network can easily be accessed by someone who is not the intended recipient. When the data includes private information, such as passwords and credit card numbers, steps must be taken to make the data unintelligible to unauthorized parties. It is also important to ensure that the data has not been modified, either intentionally or unintentionally, during transport. The Secure Sockets Layer (SSL) and Transport Layer Security (TLS) protocols were designed to help protect the privacy and integrity of data while it is being transferred across a network.}

^{The Java Secure Socket Extension (JSSE) enables secure Internet communications. It provides a framework and an implementation for a Java version of the SSL and TLS protocols and includes functionality for data encryption, server authentication, message integrity, and optional client authentication. Using JSSE, developers can provide for the secure passage of data between a client and a server running any application protocol (such as HTTP, Telnet, or FTP) over TCP/IP. For an introduction to SSL, see Secure Sockets Layer (SSL) Protocol Overview.}

^{By abstracting the complex underlying security algorithms and handshaking mechanisms, JSSE minimizes the risk of creating subtle but dangerous security vulnerabilities. Furthermore, it simplifies application development by serving as a building block that developers can integrate directly into their applications.}

^{JSSE provides both an application programming interface (API) framework and an implementation of that API. The JSSE API supplements the core network and cryptographic services defined by the java.security and java.net packages by providing extended networking socket classes, trust managers, key managers, SSL contexts, and a socket factory framework for encapsulating socket creation behavior. Because the SSLSocket class is based on a blocking I/O model, the Java Development Kit (JDK) includes a nonblocking SSLEngine class to enable implementations to choose their own I/O methods.}

^{The JSSE API is capable of supporting SSL versions 2.0 and 3.0 and TLS version 1.0. These security protocols encapsulate a normal bidirectional stream socket, and the JSSE API adds transparent support for authentication, encryption, and integrity protection. The JSSE implementation shipped with the JDK supports SSL 3.0 and TLS 1.0. It does not implement SSL 2.0.}

^{JSSE is a security component of the Java SE platform, and is based on the same design principles found elsewhere in the Java Cryptography Architecture (JCA) framework. This framework for cryptography-related security components allows them to have implementation independence and, whenever possible, algorithm independence. JSSE uses the cryptographic service providers defined by the JCA framework.}

^{The JSSE API was designed to allow other SSL/TLS protocol and Public Key Infrastructure (PKI) implementations to be plugged in seamlessly. Developers can also provide alternative logic to determine if remote hosts should be trusted or what authentication key material should be sent to a remote host.}

^{Features and Benefits}

^{JSSE includes the following important features:}

• ^{Included as a standard component of the JDK}
• ^{Extensible, provider-based architecture}
• ^{Implemented in 100% pure Java}
• ^{Provides API support for SSL versions 2.0 and 3.0, TLS 1.0 and later, and an implementation of SSL 3.0 and TLS 1.0}
• ^{Includes classes that can be instantiated to create secure channels (SSLSocket, SSLServerSocket, and SSLEngine)}
• ^{Provides support for cipher suite negotiation, which is part of the SSL handshaking used to initiate or verify secure communications}
• ^{Provides support for client and server authentication, which is part of the normal SSL handshaking}
• ^{Provides support for HTTP encapsulated in the SSL protocol, which allows access to data such as web pages using HTTPS}
• ^{Provides server session management APIs to manage memory-resident SSL sessions}
• ^{Provides support for several cryptographic algorithms commonly used in cipher suites, including those listed in Table 1.}