Rogue Wave banner
No previous fileTop of DocumentContentsNo linkNo next file
Secure Communication Module User's Guide
Rogue Wave web site:  Home Page  |  Main Documentation Page

Topic Index

Click on one of the letters below to jump immediately to that section of the index.

A | B | C | D | E | F | G | H | I | K | M | O | P | Q | R | S | T | U | W

A

accessing
   underlying data structures [in 5.8 Mixing Calls to the Secure Sockets Package with Calls to the Cryptographic Library]
agents
   architecture [in 7.1.1 Using RWHttpAgent to Retrieve a Document Securely]
architecture
   Secure Sockets package [in 2.2 The Secure Sockets Package]
attributes
   secure socket [in 5.11.1 Working with Secure Socket Attributes]

B

bibliography [in B.1 Introduction]

C

callbacks
   stop using [in 8.1.2 Switching to the Default Callback]
   switching to the default [in 8.1.2 Switching to the Default Callback]
   using [in 8.1.1 Writing a Callback]
   using with HTTPS [in 7.4 Using the Security Callbacks]
   using with secure sockets [in 5.5 Using the Secure Sockets Callbacks]
   writing [in 8.1.1 Writing a Callback]
certificate name check callback (HTTPS) [in 7.4.1 Certificate Name Check Callback]
certificate name mismatch callback (HTTPS) [in 7.4.2 Certificate Name Mismatch Callback]
certificate verification callback (secure sockets) [in 5.5.2 Certificate Verification Callback]
certificates
   definition [in 2.4 Concepts]
   hard-coded [in 4.3.3 Using Hard-Coded Keys and Certificates]
   in the example programs [in 4.1.5 About the Keys and Certificates in the Example Programs]
   obtaining [in 4.3 Obtaining Certificates]
   obtaining to identify an entity [in 4.3.2 Obtaining Certificates to Identify a Specific Entity]
   obtaining to verify other certificates [in 4.3.1 Obtaining Trusted Certificates to Verify Other Certificates]
client and server authentication
   definition [in 2.4 Concepts]
   examples [in 5.7 Implementing Both Client and Server Authentication]
   initializing [in 4.5.2 Initializing the Context to Perform Both Client and Server Authentication]
client certificate callback (secure sockets) [in 5.5.4 Client Certificate Callback]
client program
   example [in 4.1.1 Writing a Client Program That Uses RWSecureSocket]
      [in 4.1.2 Writing a Client Program That Uses RWSecureSocketPortal]
clients
   architecture [in 7.1.2 Using RWHttpsSecureSocketClient to Retrieve a Document]
CloseNotify [in 5.13 Security Issues]
Communication Adapter Layer
   definition [in 2.4 Concepts]
Communication Services Layer
   definition [in 2.4 Concepts]
   using [in 5.1 Using RWPortalIStream and RWPortalOstream]
connecting
   through a firewall [in 8.2 Using the HTTP CONNECT Method with the HTTPS Package]
   through a proxy [in 8.2 Using the HTTP CONNECT Method with the HTTPS Package]
connections
   reusing [in 5.6 Reusing Sessions]
constructing
   global objects [in 4.4.2 Global Objects and the Secure Sockets Package Initialization]
context
   creating [in 4.5 Creating the Secure Socket Context]
creating
   secure socket context [in 4.5 Creating the Secure Socket Context]
   tunnels [in 8.2 Using the HTTP CONNECT Method with the HTTPS Package]
cryptographic data structures
   accessing [in 5.8 Mixing Calls to the Secure Sockets Package with Calls to the Cryptographic Library]
cryptographic library
   errors [in 5.10 Handling Errors from the Cryptographic Library]
   initialization [in 4.4 Initializing the Secure Sockets Package]
   mixing calls with the Secure Sockets package [in 5.8 Mixing Calls to the Secure Sockets Package with Calls to the Cryptographic Library]

D

dependencies [in 1.3 Module-Specific Software Requirements]
developing
   secure applications [in 4.2 Developing Secure Applications]

E

encrypted keys
   using [in 5.3 sing Encrypted Keys]
errors
   cryptographic library [in 5.10 Handling Errors from the Cryptographic Library]
exceptions
   handling [in 5.4 Handling Exceptions]
   RWHttpsCertificateNameMismatch [in 7.4.2 Certificate Name Mismatch Callback]
      [in 7.4 Using the Security Callbacks]

F

firewalls
   connecting through [in 8.2 Using the HTTP CONNECT Method with the HTTPS Package]

G

global objects
   when to construct [in 4.4.2 Global Objects and the Secure Sockets Package Initialization]

H

handle-body idiom [in 5.12 Multithreading, the Handle-Body Idiom, and the Secure Sockets Package]
handling
   errors from the cryptographic library [in 5.10 Handling Errors from the Cryptographic Library]
   exceptions [in 5.4 Handling Exceptions]
handshake information callback (secure sockets) [in 5.5.3 Handshake Information Callback]
header files
   for HTTPS package [in 6.1.2 Header Files]
   for Secure Sockets package [in 3.1.2 Header Files]
hierarchy
   HTTPS package [in 6.2 HTTPS Package Class Hierarchy]
   Secure Sockets package [in 3.2 Secure Sockets Package Class Hierarchy]
HTTP CONNECT
   using with HTTPS [in 8.2 Using the HTTP CONNECT Method with the HTTPS Package]
HTTPS package
   introducing [in 6.1 Introduction]
HTTPS protocol [in 6.1 Introduction]

I

initializing
   client and server authentication [in 4.5.2 Initializing the Context to Perform Both Client and Server Authentication]
   cryptographic library [in 4.4 Initializing the Secure Sockets Package]
   Secure Sockets package [in 4.4 Initializing the Secure Sockets Package]
   server authentication [in 4.5.1 Initializing the Context to Perform Server Authentication Only]

K

keys
   hard-coded [in 4.3.3 Using Hard-Coded Keys and Certificates]
   in the example programs [in 4.1.5 About the Keys and Certificates in the Example Programs]

M

mixing
   cryptographic library and Secure Sockets package calls [in 5.8 Mixing Calls to the Secure Sockets Package with Calls to the Cryptographic Library]
multiplexing [in 5.11 Secure Socket Multiplexing]
multithread levels
   definition [in 2.4 Concepts]
multithreading [in 5.12 Multithreading, the Handle-Body Idiom, and the Secure Sockets Package]

O

obtaining
   certificates [in 4.3 Obtaining Certificates]
   certificates to identify specific entities [in 4.3.2 Obtaining Certificates to Identify a Specific Entity]
   certificates to verify other certificates [in 4.3.1 Obtaining Trusted Certificates to Verify Other Certificates]

P

password callback (secure sockets) [in 5.3 sing Encrypted Keys]
   [in 5.5.1 Password Callback]
Portal Layer
   definition [in 2.4 Concepts]
portals
   definition [in 2.4 Concepts]
porting
   existing applications [in 4.2.2 Porting Existing Networking Package Applications to the Secure Sockets Package]
private and public keys
   definition [in 2.4 Concepts]
PRNG
   definition [in 2.4 Concepts]
protocols
   HTTPS [in 6.1 Introduction]
   SSL [in 3.1 Introduction]
   SSL/TLS [in 6.1 Introduction]
      [in 3.1 Introduction]
   TLS [in 3.1 Introduction]
proxy machines
   connecting through [in 8.2 Using the HTTP CONNECT Method with the HTTPS Package]
pseudo-random number generator
   definition [in 2.4 Concepts]

Q

quiet shutdown
   using [in 5.13 Security Issues]

R

random number generator
   definition [in 2.4 Concepts]
   seeding [in 4.4.1 Seeding the Random Number Generator]
retrieving
   documents with HTTPS using a client [in 7.1.2 Using RWHttpsSecureSocketClient to Retrieve a Document]
   documents with HTTPS using an agent [in 7.1.1 Using RWHttpAgent to Retrieve a Document Securely]
reusing
   connections [in 5.6 Reusing Sessions]
   server refuses to reuse session [in 5.6 Reusing Sessions]
   sessions [in 5.6 Reusing Sessions]
RNG
   definition [in 2.4 Concepts]
RW_SECSOCK_RNG_NEEDS_SEEDING [in 4.4.1 Seeding the Random Number Generator]
RWAsymmetricKey
   about [in 5.2 Using RWAsymmetricKey]
   password callback [in 5.3 sing Encrypted Keys]
RWHttpsCertificateNameMismatch [in 7.4.2 Certificate Name Mismatch Callback]
   [in 7.4 Using the Security Callbacks]
RWHttpsSecureSocketClient [in 7.2 Developing HTTPS Applications]
   [in 8.2 Using the HTTP CONNECT Method with the HTTPS Package]
   [in 8.2 Using the HTTP CONNECT Method with the HTTPS Package]
   [in 6.1.1 Classes in the HTTPS package]
RWHttpsSecurityManager [in 6.1.1 Classes in the HTTPS package]
RWInetAddr [in 4.2.1 Writing New Secure Sockets Applications]
RWPortalIStream [in 5.1 Using RWPortalIStream and RWPortalOstream]
RWPortalOstream [in 5.1 Using RWPortalIStream and RWPortalOstream]
RWPrivateKey [in 5.2 Using RWAsymmetricKey]
RWPublicKey [in 5.2 Using RWAsymmetricKey]
RWSecureSocket [in 4.1.1 Writing a Client Program That Uses RWSecureSocket]
   [in 4.1.3 Writing a Server Program That Uses RWSecureSocket]
   [in 4.8 Using RWSecureSocket, RWSecureSocketPortal, and RWSecureSocketListener]
   [in 4.3.2 Obtaining Certificates to Identify a Specific Entity]
   [in 4.8 Using RWSecureSocket, RWSecureSocketPortal, and RWSecureSocketListener]
   [in 4.2.1 Writing New Secure Sockets Applications]
   [in 4.2.2 Porting Existing Networking Package Applications to the Secure Sockets Package]
   [in 4.1 Getting Started with Secure Sockets]
RWSecureSocketAttribute [in 5.11.2 Using RWSecureSocketAttribute]
RWSecureSocketContext [in 4.2.2 Porting Existing Networking Package Applications to the Secure Sockets Package]
   [in 4.5 Creating the Secure Socket Context]
   [in 4.3.2 Obtaining Certificates to Identify a Specific Entity]
   [in 7.2 Developing HTTPS Applications]
   [in 4.2.1 Writing New Secure Sockets Applications]
   [in 4.2.2 Porting Existing Networking Package Applications to the Secure Sockets Package]
   loadVerifyLocations() [in 4.3.1 Obtaining Trusted Certificates to Verify Other Certificates]
   prepareToAuthenticate() [in 4.5.2 Initializing the Context to Perform Both Client and Server Authentication]
      [in 4.5.1 Initializing the Context to Perform Server Authentication Only]
      [in 4.3.1 Obtaining Trusted Certificates to Verify Other Certificates]
   setIdentity() [in 4.5.1 Initializing the Context to Perform Server Authentication Only]
      [in 4.5.2 Initializing the Context to Perform Both Client and Server Authentication]
RWSecureSocketListener [in 4.2.2 Porting Existing Networking Package Applications to the Secure Sockets Package]
   [in 4.8 Using RWSecureSocket, RWSecureSocketPortal, and RWSecureSocketListener]
   [in 4.8 Using RWSecureSocket, RWSecureSocketPortal, and RWSecureSocketListener]
   [in 4.2.1 Writing New Secure Sockets Applications]
RWSecureSocketPackageInit [in 4.4.1 Seeding the Random Number Generator]
   [in 4.1.3 Writing a Server Program That Uses RWSecureSocket]
   [in 4.4 Initializing the Secure Sockets Package]
   [in 4.1.2 Writing a Client Program That Uses RWSecureSocketPortal]
   [in 4.4.2 Global Objects and the Secure Sockets Package Initialization]
   [in 4.1.1 Writing a Client Program That Uses RWSecureSocket]
RWSecureSocketPortal [in 4.2.1 Writing New Secure Sockets Applications]
   [in 4.1.2 Writing a Client Program That Uses RWSecureSocketPortal]
   [in 4.1.4 Writing a Server Program That Uses RWSecureSocketPortal]
   [in 4.8 Using RWSecureSocket, RWSecureSocketPortal, and RWSecureSocketListener]
   [in 4.2.2 Porting Existing Networking Package Applications to the Secure Sockets Package]
   [in 4.1 Getting Started with Secure Sockets]
   [in 4.8 Using RWSecureSocket, RWSecureSocketPortal, and RWSecureSocketListener]
rwSecureSocketSelect [in 5.11.3 Using rwSecureSocketSelect]
RWWinSockInfo [in 4.2.1 Writing New Secure Sockets Applications]
   [in 7.2 Developing HTTPS Applications]
   [in 4.1.2 Writing a Client Program That Uses RWSecureSocketPortal]
   [in 4.1.1 Writing a Client Program That Uses RWSecureSocket]
   [in 4.1.1 Writing a Client Program That Uses RWSecureSocket]
   [in 4.1.3 Writing a Server Program That Uses RWSecureSocket]
   [in 4.1.3 Writing a Server Program That Uses RWSecureSocket]
RWX509Certificate [in 4.6 Constructing a Certificate]
   [in 4.3.2 Obtaining Certificates to Identify a Specific Entity]

S

Secure Sockets package
   architecture [in 2.2 The Secure Sockets Package]
   initialization [in 4.4 Initializing the Secure Sockets Package]
   introducing [in 3.1 Introduction]
   using [in 4.2.1 Writing New Secure Sockets Applications]
secure sockets
   using more than one [in 5.11 Secure Socket Multiplexing]
security [in 5.13 Security Issues]
seeding
   random number generator [in 4.4.1 Seeding the Random Number Generator]
server authentication
   definition [in 2.4 Concepts]
   initializing [in 4.5.1 Initializing the Context to Perform Server Authentication Only]
server program
   example [in 4.1.3 Writing a Server Program That Uses RWSecureSocket]
      [in 4.1.4 Writing a Server Program That Uses RWSecureSocketPortal]
sessions
   reusing [in 5.6 Reusing Sessions]
   server refuses reuse [in 5.6 Reusing Sessions]
software dependencies [in 1.3 Module-Specific Software Requirements]
SSL protocol [in 3.1 Introduction]
SSL/TLS protocol [in 3.1 Introduction]
   [in 6.1 Introduction]

T

TLS protocol [in 3.1 Introduction]
tunnels
   creating [in 8.2 Using the HTTP CONNECT Method with the HTTPS Package]

U

using
   callbacks [in 8.1.1 Writing a Callback]
   callbacks with HTTPS [in 7.4 Using the Security Callbacks]
   callbacks with secure sockets [in 5.5 Using the Secure Sockets Callbacks]
   certificate name check callback (HTTPS) [in 7.4.1 Certificate Name Check Callback]
   certificate name mismatch callback (HTTPS) [in 7.4.2 Certificate Name Mismatch Callback]
   certificate verification callbacks (secure sockets) [in 5.5.2 Certificate Verification Callback]
   client certificate callback (secure sockets) [in 5.5.4 Client Certificate Callback]
   encrypted keys [in 5.3 sing Encrypted Keys]
   handshake information callbacks (secure sockets) [in 5.5.3 Handshake Information Callback]
   HTTP CONNECT with HTTPS [in 8.2 Using the HTTP CONNECT Method with the HTTPS Package]
   more than one secure socket [in 5.11 Secure Socket Multiplexing]
   password callbacks (secure sockets) [in 5.5.1 Password Callback]
   quiet shutdown [in 5.13 Security Issues]
   secure agents [in 7.1.1 Using RWHttpAgent to Retrieve a Document Securely]
   secure clients [in 7.1.2 Using RWHttpsSecureSocketClient to Retrieve a Document]
   secure socket attributes [in 5.11.1 Working with Secure Socket Attributes]

W

writing
   callbacks [in 8.1.1 Writing a Callback]
   new HTTPS applications [in 7.2 Developing HTTPS Applications]
   new secure sockets applications [in 4.2.1 Writing New Secure Sockets Applications]


No previous fileTop of DocumentContentsNo linkNo next file

Copyright © Rogue Wave Software, Inc. All Rights Reserved.

The Rogue Wave name and logo, and SourcePro, are registered trademarks of Rogue Wave Software. All other trademarks are the property of their respective owners.
Provide feedback to Rogue Wave about its documentation.