evfstab.4 (2010 09)

evfstab(4) evfstab(4)

(EVFS Software Required)

EXAMPLES

The following is a sample evfstab ﬁle:

v /dev/vg01/lvol1 /dev/evfs/vg01/lvol1

v /dev/vg01/lvol2 /dev/evfs/vg01/lvol2 root.root noauto

v /dev/dsk/c1t0d0 /dev/evfs/dsk/c1t0d0 root.admink boot_local

v /dev/vg01/lvol5 /dev/evfs/vg01/lvol5 root.admink boot_remote

f /dev/vg01/lvol9 /dev/evfs/vg01/lvol9

The ﬁle contains ﬁve entries for ﬁve different encrypted volumes - Four for volume encryption and one for

ﬁle encryption. Each entry minimally contains a mapping between an encrypted volume special ﬁle and

the original logical volume.

• The ﬁrst entry does not contain a key ID. The administrator will be prompted for a passphrase when

enabling or disabling the volume, and when executing

evfsvol operations on the volume that modify

Encryption Metadata (EMD), such as adding or deleting user keys.

• The second entry contains a key ID and the

noauto option. If a passphrase is stored for the key, the

administrator can execute

evfsvol commands on this volume in non-interactive mode, but the EVFS

volume will not be automatically enabled at system startup time.

• The third entry contains a key ID and the

boot_local option. A passphrase must be stored for the

key, and the EVFS will be automatically enabled at system startup time before networking is started.

The key ﬁles and stored passphrase must exist on the local root directory.

• The fourth entry contains a key ID and the

boot_remote option. A passphrase must be stored for

the key, and the EVFS will be automatically enabled at system startup time after networking is

started. The stored passphrase must exist on the local root directory, but the key ﬁles may be stored

on a remote directory.

• The ﬁfth entry is a volume used for ﬁle level encryption.

AUTHOR

evfstab was developed by Hewlett-Packard.

FILES

/etc/evfs/evfstab