HP UX IPSec Software nocommit Argument, Dynamic Configuration Updates

Configuring HP-UX IPSec

Using ipsec_config

Multihomed Nodes with Private Interfaces If the local system is multihomed with one public IP interface and one or more private IP interfaces, you may want to secure only the one public IP interface. In this case, you can set the default source parameter value to the address of the public IP interface in the HostPolicy-Defaults,GWPolicy-Defaults, and TunnelPolicy-Defaults sections of the profile file.

Dynamic Configuration Updates

The ipsec_config utility dynamically updates the configuration database. If HP-UX IPSec is running, ipsec_config also updates the runtime IPSec policy database, and runtime IKE configuration data (IKE policies and authentication records).

Dynamic Deletions

If you delete an object while HP-UX IPSec is running, HP-UX IPSec deletes it from its runtime database. If you delete an IPSec policy, HP-UX IPSec deletes any associated IPSec/QM SAs. If you delete an IKE policy, HP-UX deletes any associated ISAKMP/MM SAs. IPSec/QM SAs negotiated using the ISAKMP/MM SAs may continue to operate, but IKE peers will be unable to send control messages for the affected IPSec/QM SAs.

nocommit Argument

The nocommit argument validates entries but does not update the configuration and runtime databases. The nocommit argument is illegal inside batch files (you cannot specify the nocommit argument as part of a statement inside a batch file). You can specify the nocommit argument as part of the ipsec_config batch command line and ipsec_config will apply it to all entries in the batch file. Refer to the ipsec_config (1M) manpage for more information.

Chapter 3 65