Luna SA 4.4.3 - Secure Support - SafeNet

Hardware revisions and part numbers
SafeNet may occasionally make minor changes to the hardware components used to manufacture the appliance for cost
or availability reasons. For example, if the supply of one the original components used to manufacture the appliance
becomes limited, the original component may be replaced with an equivalent, but more widely available component.
Although these minor hardware changes do not affect how the appliance behaves or operates, any hardware change
triggers a change in the product revision. A product may go through several hardware revisions during its lifecycle. Note,
however, that for any given part number, all revisions of that part number are functionally equivalent. For example, there is
no operational difference between revisions B and D of part number 808-000043-001.
In general, the following rules apply:
If the hardware change does not affect how the product behaves or operates, the part number remains the same.
Only the revision is changed.
If the hardware change affects how the appliance behaves or operates, the hardware is assigned a new part number.
Notes about this release
Utilities and sample code
The utilities and the code samples that are included with the SDK are provided for illustrative purposes only. They are
intended as a starting point to assist you in developing your own applications. They are not intended for use in a
production environment.
[The following notes are unchanged from the CRN for versions 4.4.0 and 4.4.1.]
New SafenetKSP.dll available
A new SafenetKSP.dll file is available (part number 630-010150-001) as a patch that fixes a compatibility issue when
used with Windows 2008 R2. Contact SafeNet Customer Support if you need it. (This note retained from Luna SA 4.4.1
CRN.)
AIX and HP-UX client version number mismatch
During installation of the update to Luna SA 4.4.1 Client, the software reports version 4.4.0. Similarly, if you queried the
system after installation, the installed software reports 4.4.0. This occurs only in AIX and HP-UX systems. If the
installation proceeds smoothly (no stops for error messages), then version 4.4.1 is actually installed. Ignore any reference
to 4.4.0. (This note retained from Luna SA 4.4.1 CRN – this is an appliance patch and doesn't affect the Client software,
which remains at version 4.4.1.)
Luna SA with Luna SX with remote PED
Luna SA provides a command-line administrative interface (lunash) via SSH or direct serial link. Luna SX provides a GUI
overlay for common setup and administrative tasks.
Luna SX was developed before Remote PED support was added to Luna SA.
Luna SX has been tested with Luna SA that uses Remote PED, and the combination is supported.
However, Luna SX has no awareness of Remote PED, and no specific functions supporting that feature. Therefore:
All appliance-side (PEDclient) setup for Remote PED must be accomplished via Luna SA command line - use an SSH
session or a direct-connect serial session, or use the command-line panel within Luna SX.
When Luna SX indicates that a PED operation is needed, you must keep track of where that PED is located (local or
remote).
Luna SA with 100+ clients
To register a large number of clients simultaneously with one Luna SA appliance, register by IP address. (This note
retained from Luna SA 4.4.1 CRN.)
No Apache/OpenSSL support in Suse Linux Enterprise Server
Porting to Novell‟s SUSE Linux Enterprise Server (SLES) 10 for PPC does not include Apache/OpenSSL. (This note
retained from Luna SA 4.4.1 CRN.)
Luna SA 4.4.3 Customer Release Notes 007-011327-001 Revision E Copyright 2009-2012 SafeNet Inc. 3