HP (Hewlett-Packard) Version 8.4 Server User Manual


 
Programming Release Notes
5.16 Calling Standard and Rotating Registers (Integrity servers Only)
Previously, the supplemental access routines LIB$I64_GET_FR, LIB$I64_SET_
FR, LIB$I64_GET_GR and LIB$I64_SET_GR (see Section 4.8.4 in the HP
OpenVMS Calling Standard) improperly interpreted their register number
parameters without applying an adjustment for the effects of the register rename
base and rotating size registers. This error is corrected.
5.17 Common Data Security Architecture (CDSA) Considerations
The following notes pertain to CDSA.
5.17.1 Secure Delivery
V8.4
From Version 8.4 onwards, all OpenVMS kits including PCSI and VMSINSTAL
based kits will be signed using HP Code Signing Service (HPCSS). The signing
and validation do not use the CDSA infrastructure. A new companion le,
<full kit name>_HPC is created and is provided along with the kit. The kit is
then validated using this companion le.
A new validator, "HPBinarychecker" is installed on all OpenVMS systems to
validate the kits signed using HP Code Signing Service. For more information,
see HP OpenVMS Version 8.4 New Features and Documentation Overview.
Note that the kits that are signed prior to Version 8.4 can be validated using
CDSA on OpenVMS Version 8.4.
V8.3
Downloading of les over the Internet is becoming a requirement of OpenVMS
customers who want to use this easy and convenient method to acquire software
updates, but are wary of the security vulnerabilities. Secure Delivery makes
use of public key and digital signature technology to implement a system that
provides OpenVMS users with the ability to authenticate and validate the les
they download from OpenVMS.
Secure Delivery is fully functional with OpenVMS Version 8.3. For more
information, refer to the HP OpenVMS Version 8.3 New Features and
Documentation Overview.
5.17.2 Installation and Initialization Considerations
V8.4
Installation of CDSA is done automatically when you install the operating system.
When a new version of CDSA is installed separately from an Operating
System upgrade, you must run the CDSA upgrade procedure:
$ @SYS$STARTUP:CDSA$UPGRADE
You should shut down any CDSA application before you run the upgrade
procedure.
It is not necessary to rerun the upgrade procedure when the system is
rebooted. You also do not need to add the upgrade procedure to the OpenVMS
startup procedures.
Do not attempt to remove CDSA from your system. Use of the PCSI command
PRODUCT REMOVE is not supported for CDSA, even though there is an
apparent option to remove CDSA. (This option is due to the use of PCSI in
the installation.) CDSA is installed together with the operating system and is
tightly bound with it. An attempt to remove it from OpenVMS will not work
5–14 Programming Release Notes