OpenSSL supports a set of SSL options and defect workarounds. You can enable these workarounds and options as settings of an individual client-side or server-side SSL profile. The default value for the Options setting is Options List. Retaining the default value enables one option, which is Don’t insert empty fragments. You can then enable other options that appear in the Available Options list.

Note that when configuring protocol versions, you must ensure that the protocol versions configured for the BIG-IP system match those of the system’s peer. That is, protocol versions specified in the client-side SSL profile must match those of the client, and protocol versions specified in the server-side SSL profile must match those of the server. Thus, for both client-side and server-side SSL connections, you can specify the protocol versions that you do not want the BIG-IP system to allow.

You can enable or disable ModSSL method emulation. You enable ModSSL method emulation when the OpenSSL methods are inadequate. When you enable this setting, you can then write an iRule, using the HTTP::header insert_modssl_fields command, which inserts some of the ModSSL options as headers into HTTP requests.

You can configure timeout and size values for the SSL session cache. Because each profile maintains a separate SSL session cache, you can configure the values on a per-profile basis.

You can specify the duration in seconds that the BIG-IP^® system waits while trying to close an SSL connection, before the connection is reset. The default timeout value for this setting is 10 seconds.

You can specify the amount of time in seconds that the BIG-IP^® system spends attempting to perform an SSL handshake. The default timeout value for this setting is 10 seconds.

Long-lived connections are susceptible to man-in-the-middle attacks. To prevent such attacks, you can force the BIG-IP^® system to renegotiate SSL sessions, based on either time period or application size. You can also force the BIG-IP system to terminate an SSL session after receiving a specified number of records.

More specifically, you can control, on a per-connection basis, the way that the system responds to mid-stream SSL reconnection requests. When you enable renegotiation, the system processes mid-stream SSL renegotiation requests. When you disable renegogiation, the system either terminates the connection or ignores the request, depending on the system configuration. By default, renegotiation is enabled.

The Server Name setting in an SSL profile specifies the name of the specific domain from which the client requests a certificate. This setting supports a feature known as TLS Server Name Indication (TLS SNI), used when a single virtual IP server needs to host multiple domains.

For example, suppose that the BIG-IP^® system needs to host the two domains domain1.com and domain2.com, on the same HTTP virtual server. Each domain has its own server certificate to use, such as domain1.crt and domain2.crt, and each has different security requirements.

To ensure that the BIG-IP system presents the correct certificate to the browser, you enable SNI, which sends the name of a domain as part of the TLS negotiation. This, in turn, enables the BIG-IP system to select this domain rather than waiting to read the domain name in the request header.

To enable SNI, you configure the Server Name and other TLS-related settings on an SSL profile, and then assign the profile to a virtual server.

Note that the wildcard character (*) is supported within any domain name that you specify.

When you enable the Default SSL Profile for SNI setting on an SSL profile, you are specifying that this is the default SSL profile to use when the client provides either no Server Name Indication (SNI) extension, or provides a non-matching SNI extension.

When assigning multiple SSL profiles to a single virtual server, you can enable this setting on one Client SSL profile only and one Server SSL profile only.

If you enable the Require Peer SNI Support setting on an SSL profile, the domain name of the peer must match the domain name that you specify in the Default SSL Profile for SNI field.

In an unclean shutdown, underlying TCP connections are closed without exchanging the required SSL shutdown alerts. However, you can disable unclean shutdowns and thus force the SSL profile to perform a clean shutdown of all SSL connections by configuring this setting.

This feature is especially useful with respect to the Internet Explorer browser. Different versions of the browser, and even different builds within the same version of the browser, handle shutdown alerts differently. Some versions or builds require shutdown alerts from the server, while others do not, and the SSL profile cannot always detect this requirement or lack of it. In the case where the browser expects a shutdown alert but the SSL profile has not exchanged one (the default setting), the browser displays an error message.

By default, this setting is enabled, which means that Local Traffic Manager™ performs unclean shutdowns of all SSL connections.

You can configure Local Traffic Manager™ to discontinue an SSL session after an unclean shutdown. By default, this setting is disabled, which causes Local Traffic Manager (LTM^®) to resume SSL sessions after an unclean shutdown. If you enable this setting, LTM does not resume SSL sessions after an unclean shutdown.

To enhance system performance, you can enable the use of session tickets, a TLS extension defined in RFC 5077. The use of session tickets is an alternative to the standard session caching mechanism that systems such as the BIG-IP system typically use to resume sessions.

When you enable this feature, the BIG-IP system, acting as a server to terminate SSL connections, sends a special message to the client as part of the SSL handshake. This message includes a session ticket, which contains complete session state information. Sending the session state information to the client removes the need for the BIG-IP system to maintain a server-side cache for storing session information. With session tickets, the entire session state is remembered by the client.

The session state information in the ticket includes the master secret negotiated between the client and the BIG-IP system, as well as the cipher suite used.

For security reasons, when sending an SSL alert message, the BIG-IP^® system sends a generic handshake failure message with an alert code of 40, with no detailed information. This is the default behavior.

If you want SSL alert messages to include the specific reason for the failure, you can disable the Generic Alerts setting. In this case, when an SSL failure occurs, the system sends an alert message with a specific numeric code. For example, an alert message due to a certificate revocation would show a specific code of 48 instead of the generic code of 40.

You can configure Local Traffic Manager™ to accept connections that are not SSL connections. In this case, connections pass through the BIG-IP^® system in clear-text format. By default, this setting is disabled.

For a Client SSL profile, this setting specifies the hash algorithm that the Client SSL profile uses to sign Server Key Exchange messages and advertises in a Certificate Request message when requesting a client certificate.

For a Server SSL profile, this setting specifies the certificate signature hash algorithm or algorithms that the Server SSL profile advertises in the ClientHello signature_algorithms extension and uses in the Certificate Verify handshake message when using a client certificate.

A reboot or reset action can sometimes produce an excessive number of SSL handshakes, which can impact normal BIG-IP^® system operation. To prevent this from happening, you can use the Max Active Handshakes setting on a Client SSL or Server SSL profile to limit the number of concurrent handshakes.

When the number of active SSL handshakes pertaining to an SSL profile reaches the specified limit, the system terminates the most recent SSL handshake, and the BIG-IP system displays a message that the specified handshake limit has been reached. The system also sends an alert message to other members of the device group.

The default setting is Indefinite, which means that there is no limit on the number of active SSL handshakes that the system allows.

Dynamic record sizing is a TLS performance enhancement, designed to improve application response by preventing bottlenecks caused by the buffering of TLS record fragments. Without dynamic record sizing, a record that spans multiple TCP packets can cause buffering, forcing the TCP receiver to wait for all of the TCP packets to arrive before constructing the original-sized record (typically 16 KB). Other causes of buffering can include packet loss, packet reordering, or throttling. The result is that the browser is left to deal with significant bottlenecks that affect performance.

With dynamic record sizing, the system dynamically adjusts the size of TLS records based on the state of the connection. For example, if a connection is idle for awhile, it might make sense for the system to ensure a single TLS record per packet, where the size of the TLS record is the TCP maximum segment size (MSS). For connections in another state, such as large application streams, it might still make sense for a TLS record to span multiple packets.

To specify dynamic record sizing, you log in to the BIG-IP ^®Configuration utility screen, and locate the screen for creating a Client SSL profile. Then enable the Allow Dynamic Record Sizing check box.

The Maximum Record Size setting on a Client SSL profile defines the maximum size possible for a TLS record. If you enable dynamic record sizing (for performance enhancement), then the maximum record size you set is the largest size that the system can use for a TLS record when that size is needed. If dynamic record sizing is disabled (the default value), then all record size is static, and the size can be up to the maximum record size you specify.

To set the maximum record size, you log in to the BIG-IP ^®Configuration utility screen and locate the screen for creating a Client SSL profile. Then type a value for the Maximum Record Size setting. The default value in kilobytes (KB) is 16384.