JavaScript is required to for searching.
Skip Navigation Links
Exit Print View
Oracle Solaris 10 1/13 Installation Guide: Network-Based Installations     Oracle Solaris 10 1/13 Information Library
search filter icon
search icon

Document Information

Preface

Part I Planning to Install Over the Network

1.  Where to Find Oracle Solaris Installation Planning Information

2.  Preconfiguring System Configuration Information (Tasks)

3.  Preconfiguring With a Naming Service or DHCP

Part II Installing Over a Local Area Network

4.  Installing From the Network (Overview)

5.  Installing From the Network With DVD Media (Tasks)

6.  Installing From the Network With CD Media (Tasks)

7.  Patching the Miniroot Image (Tasks)

8.  Installing Over the Network (Examples)

9.  Installing From the Network (Command Reference)

Part III Installing Over a Wide Area Network

10.  WAN Boot (Overview)

What Is WAN Boot?

When to Use WAN Boot

How WAN Boot Works (Overview)

Sequence of Events in a WAN Boot Installation

Protecting Data During a WAN Boot Installation

Checking the Integrity of Data With a Hashing Key

Encrypting Data With Encryption Keys

Protecting Data by Using HTTPS

Security Configurations Supported by WAN Boot (Overview)

Secure WAN Boot Installation Configuration

Insecure WAN Boot Installation Configuration

11.  Preparing to Install With WAN Boot (Planning)

12.  Installing With WAN Boot (Tasks)

13.  SPARC: Installing With WAN Boot (Tasks)

14.  SPARC: Installing With WAN Boot (Examples)

15.  WAN Boot (Reference)

Part IV Appendixes

A.  Troubleshooting (Tasks)

B.  Installing or Upgrading Remotely (Tasks)

Glossary

Index

Security Configurations Supported by WAN Boot (Overview)

WAN boot supports varying levels of security. You can use a combination of the security features that are supported in WAN boot to meet the needs of your network. A more secure configuration requires more administration, but also protects your system data to a greater extent. For more critical systems or systems you want to install over a public network, you might choose the configuration in Secure WAN Boot Installation Configuration. For less critical systems, or systems on semi-private networks, consider the configuration that is described in Insecure WAN Boot Installation Configuration.

This section briefly describes the different configurations you can use to set the level of security for your WAN boot installation. The section also describes the security mechanisms that are required by these configurations.

Secure WAN Boot Installation Configuration

This configuration protects the integrity of the data exchanged between the server and client, and helps keep the contents of the exchange confidential. This configuration uses an HTTPS connection, and uses either the 3DES or AES algorithm to encrypt the client configuration files. This configuration also requires the server to authenticate itself to the client during the installation. A secure WAN boot installation requires the following security features:

If you want to also require client authentication during the installation, you must also use the following security features:

For a list of the tasks that are required to install with this configuration, see Table 12-1.

Insecure WAN Boot Installation Configuration

This security configuration requires the least administration effort but provides the least secure transfer of data from the web server to the client. You do not need to create a hashing key, encryption key, or digital certificates. You do not need to configure your web server to use HTTPS. However, this configuration transfers the installation data and files over an HTTP connection, which leaves your installation vulnerable to interception over the network.

If you want the client to check the integrity of the data that is transmitted, you can use an HMAC SHA1 hashing key with this configuration. However, the flash archive is not protected by the hashing key. The archive is transferred insecurely between the server and the client during the installation.

For a list of the tasks that are required to install with this configuration, see Table 12-1.