Manually moving an entry from the SSL grey list to the white list on a SteelHead enables trust between which hosts?

Question

Options

• AClient-side SteelHead and server-side SteelHead
• BClient PC and server-side SteelHead
• CClient-side SteelHead and server
• DServer-side SteelHead and server

• A
  83% (38)
• B
  4% (2)
• C
  2% (1)
• D
  11% (5)

Explanation

The Riverbed SSL solution optimizes data transfers that are encrypted using SSL, provided that SteelHeads are deployed locally to both the client-side and server-side of the network. Note: Secure Peering Using the Self-Signed Peer White, Gray, and Black Lists You can use peering lists to configure peer certificates on SteelHeads running RiOS 5.0 or later. When SSL optimization is enabled, and an optimizable SSL connection is attempted across the SteelHeads, the remote peer is detected and its peering certificate is automatically populated into the self- signed peer gray list. The connection remains unoptimized because the remote peer is listed in the self-signed peer gray list. You can examine the peer certificate for authenticity and move any peer from the gray list to either the white list or the black list. If you trust the remote peer, move it into the self-signed peer white list to begin optimizing the SSL connection. If you do not trust the remote peer, move it into the self-signed peer black list to prevent the SSL connection from being optimized.

No community discussion yet for this question.