Encrypted Volume and File System v1.1.2 Release Notes
automatically retrieve stored passphrases and use the passphrases to execute EVFS
commands.
CAUTION: Stored passphrases provide convenience, but they are security risks.
1.2 New and Changed Features in this Release
HP-UX EVFS v1.1.2 includes the defect fixes listed in “Enhancements” (page 10) and “Defects
Fixed” (page 10).
1.3 Acquiring and Installing EVFS
You can acquire and install EVFS free of charge from Software Depot:
http://www.software.hp.com
Enter EVFS into the search box at the top of the page.
Installation Requirements
EVFS requires approximately 12 MB of disk space and has the following software requirements:
• HP-UX 11i version 2 Update 2 for HP 9000 servers and HP Integrity servers.
• If your system does not automatically reboot when migrating from EVFS v1.0, you must
manually reboot to load the DLKM module. You do not need to reboot if there is no previous
version of EVFS installed.
Patch Requirements
You can download patches from the HP IT Resource Center at:
http://www2.itrc.hp.com/service/patch/mainPage.do
NOTE: You do not need to install the superseding patches listed below if you have patches on
your system from a previous installation of EVFS.
• PHCO_38637
On systems with patch PHCO_32488 and VxFS (the EnableVxFS bundle), you must install
patch PHCO_38637.
• PHKL_37146
HP strongly recommends that you install patch PHKL_37146, which fixes a defect that can
cause the newfs or mkfs command for an EVFS volume to fail on systems with components
that call alloc_fake_device(), such as systems that are NFS clients. See “Possible Device
File Collision” (page 11) for more information.
1.4 Limitations
The EVFS product has the following limitations:
• EVFS operates with LVM, VxVM and physical volumes only. Each EVFS volume is mapped
to an underlying LVM, VxVM or physical volume.
• You can use an alternate link to specify an LVM or VxVM volume or an alternate device
path to specify a whole disk for the evfsadm map command. However, when creating
EVFS volumes, do not:
— Create multiple EVFS volumes that reference the same LVM or VxVM volume
— Create multiple EVFS volumes that reference the same physical disk when using whole
disk access
8 EVFS