SSH Reference Manual

Considerations

• The value must be set consistent with the value of parameter IPMODE

• If a host name is resolved to multiple IP addresses, then only those IP addresses are used that occur in the

subnet configuration of the configured TCP/IP processes (parameter SUBNET

• If the any address (0.0.0.0 or 0::0) is listed in INTERFACEOUT, then the ANY address is used as bind address

only for those IP processes that aren’t configured with any of the other listed non-ANY addresses.

• If parameter is set via PARAM and a comma separated list is defined, then the list must be enclosed in double

quotes.

Example

INTERFACEOUT 10.0.0.197

See also

DNSMODE, INTERFACE, IPMODE, SUBNET

INTERVALLIVEPRIVATEUSERKEY

This parameter is related to a user private key’s life-cycle (configuration of database entity KEY). It determines the

length of the interval a user private key stays in state ‘LIVE’.

Parameter Syntax

INTERVALLIVEPRIVATEUSERKEY number-of-days

Arguments

number-of-days

The number of days a newly generated user private key will be in state ‘LIVE’ after leaving state ’PENDING’

and before reaching state ‘EXPIRED’.

Default

The default value for this parameter is 730, i.e. 2 years.

Example

INTERVALLIVEPRIVATEUSERKEY 1460

Considerations

• The life-cycle configuration of existing user private keys will not be modified due to this parameter. If existing

keys need to participate in life-cycle control, then they must be configured via ALTER KEY command

specifying the LIVE-DATE and EXPIRE-DATE command options.

• Parameter value is ignored if life-cycle for user private keys is disabled (i.e. if

LIFECYCLEPOLICYPRIVATEUSERKEY

is set to DISABLED).

• Parameter value is ignored if KEY attributes LIVE-DATE and EXPIRE-DATE are specified in GENERATE

KEY and IMPORT KEY commands (if a user is allowed to specify these attributes according to the key life-

cycle policy).