 |
» |
|
|
|
|
|
|
|
To expand the HPE SSL1 source kit self-extracting file, enter one of
the following commands, depending on the platform on which you downloaded the kit:
$ RUN HPE_VMS_SSL1_SOURCES_V10-2H.AXPEXE ! for OpenVMS Alpha
$ RUN HPE_VMS_SSL1_SOURCES_V10-2H.I64EXE ! for OpenVMS Integrity servers
The system expands the file and names the decompressed file:
HPE_VMS_ALPHA_SSL1_SOURCES_V10-2H.BCK
or
HPE_VMS_I64_SSL1_SOURCES_V10-2H.BCK
To expand the HPE SSL source kit self-extracting file, enter one of the following commands, depending on the platform on which you downloaded the kit:
$RUN HPE_VMS_SSL_SOURCES_V14-503.AXPEXE ! for OpenVMS Alpha
$ RUN HPE_VMS_SSL_SOURCES_V14-503.I64EXE ! for OpenVMS Integrity servers
The system expands the file and names the decompressed file:
HPE_VMS_ALPHA_SSL_SOURCES_V14-503.BCK
or
HP_VMS_I64_SSL_SOURCES_V14-503.BCK
|
|
|
|
|
|
Important: If you are restoring the sources on a system where you
installed HP SSL for OpenVMS or HP Secure Web Server
for OpenVMS,
HPE recommends that you unpack the SSL sources into
a directory tree separate from your SSL1 or Secure Web Server installation.
For example, if you installed the HPE SSL1 PCSI kit in SYS$COMMON,
do not unpack the SSL1 sources in SYS$COMMON:[000000...].
If you previously installed a source code kit for an earlier version of HPE SSL1, remove the previous version source directory tree or create a new directory tree for the Version 1.0 source code kit.
To restore the HPE SSL1 sources backup saveset, enter the following commands:
$ CREATE/DIR disk:[directory]
$ BACKUP HPE_VMS_I64_SSL1_SOURCES_V10-2H.BCK/SAVE disk:[directory...]*.*
Where disk:[directory] is the location where you want to restore the sources.
This will create a directory tree under disk:[directory].
HPE SSL1 creates a subdirectory named [.HPE_VMS_SSL1_SOURCES_V10-2H…].
For example, if you specify DKA0:[SSL1_SOURCES...] on the BACKUP command line,
the resultant directory tree is DKA0:[SSL1_SOURCES.HPE_VMS_SSL1_SOURCES_V10-2H…].
To restore the HPE SSL sources backup saveset, enter the following commands:
$ CREATE/DIR disk:[directory]
$ BACKUP HPE_VMS_ALPHA_SSL_SOURCES_V14-503.BCK/SAVE disk:[directory...]*.*
|
|
|
|
|
|
Instructions for building HPE SSL1/SSL from sources are as follows:
- Confirm or change settings in VMS_BUILD_INFO.COM
to build on Alpha (64 or 32 bits), Integrity server (64 or 32 bits), or VAX (32 bits).
Set your default directory to the top level directory for the build tree.
The file VMS_BUILD_INFO.COM contains build information
about the Version 1.0/1.4 source code kit. If you do not change any values in
VMS_BUILD_INFO.COM, building the source code results in an SSL Alpha 64-bit build.
To change the default Alpha 64-bit build to an Alpha 32-bit build, an Integrity
server 64-bit or 32-bit build, or a VAX build,
open VMS_BUILD_INFO.COM in a text editor.
The default build information you will see in VMS_BUILD_INFO.COM
is for the Alpha platform with 64-bit addressing,
as follows:
$ BUILD_PLATFORM == "ALPHA"
$ USER_CCFLAGS == "/POINTER_SIZE=64"
$ BUILD_BITS == "64"
To build on the Alpha platform with 32-bit addressing, edit VMS_BUILD_INFO.COM and change
the following lines as follows:
$ BUILD_PLATFORM == "ALPHA"
$ USER_CCFLAGS == "/POINTER_SIZE=32"
$ BUILD_BITS == "32"
To build on the Itanium platform with 64-bit addressing, edit VMS_BUILD_INFO.COM and change
the following lines as follows:
$ BUILD_PLATFORM == "IA64"
$ USER_CCFLAGS == "/POINTER_SIZE=64"
$ BUILD_BITS == "64"
To build on the Itanium platform with 32-bit addressing, edit VMS_BUILD_INFO.COM and change
the following lines as follows:
$ BUILD_PLATFORM == "IA64"
$ USER_CCFLAGS == "/POINTER_SIZE=32"
$ BUILD_BITS == "32"
To build on the VAX platform with 32-bit addressing, edit VMS_BUILD_INFO.COM and change
the following lines as follows:
$ BUILD_PLATFORM == "VAX"
$ USER_CCFLAGS == ""
$ BUILD_BITS == "32"
After you have made changes to the file, save the file and exit the editor.
- Execute MAKEVMS.COM.
Execute the command procedure MAKEVMS.COM from the appropriate platform (Alpha, Integrity server, or VAX) with the following parameters:
$ @MAKEVMS/OUTPUT=MAKEVMS.LOG ALL NORSAREF NODEBUG DECC NONE
You may see the following errors, which are to be expected. The MDC2, RC5 and IDEA symmetric ciphers have been disabled in HPE SSL1 because of licensing restrictions.
$ search makevms.log "-E-"
%CC-E-ERRORMESSAGE, #error MDC2 is disabled.
%CC-E-ERRORMESSAGE, #error MDC2 is disabled.
%CC-E-ERRORMESSAGE, #error IDEA is disabled.
%CC-E-ERRORMESSAGE, #error IDEA is disabled.
%CC-E-ERRORMESSAGE, #error IDEA is disabled.
%CC-E-ERRORMESSAGE, #error IDEA is disabled.
%CC-E-ERRORMESSAGE, #error IDEA is disabled.
You may see the following errors, which are to be expected. The RC5 and IDEA symmetric ciphers have been disabled in HPE SSL because of licensing restrictions.
%CC-E-ERRORMESSAGE, #error RC5 is disabled.
%CC-E-ERRORMESSAGE, #error RC5 is disabled.
%CC-E-ERRORMESSAGE, #error RC5 is disabled.
%CC-E-ERRORMESSAGE, #error RC5 is disabled.
%CC-E-ERRORMESSAGE, #error RC5 is disabled.
%CC-E-ERRORMESSAGE, #error IDEA is disabled.
%CC-E-ERRORMESSAGE, #error IDEA is disabled.
%CC-E-ERRORMESSAGE, #error IDEA is disabled.
%CC-E-ERRORMESSAGE, #error IDEA is disabled.
%CC-E-ERRORMESSAGE, #error IDEA is disabled.
- Execute regression tests.
Execute the following command procedure to run the OpenSSL regression tests.
$ @[.TEST]TESTS
- Execute INSTALL.COM.
After the regression tests are running smoothly, create a new
directory to hold the installed files and execute the following
command procedure located in the top level directory of the build
tree. INSTALL.COM copies the necessary files out of the build tree and
into the specified kit directory.
$ CREATE/DIR disk:[directory.KIT]
$ @INSTALL.COM disk:[directory.KIT]
For example, if you restored the HPE SSL1 sources using the command:
$ BACKUP HPE_VMS_I64_SSL1_SOURCES_V10-2H.BCK/SAVE disk:[SSL1_SOURCES...]
Then copy the OpenSSL build results with the following command:
$ @INSTALL.COM disk:[SSL1_SOURCES.HPE_VMS_SSL1_V10.KIT]
For example, if you restored the HPE SSL sources using the command:
$ BACKUP HPE_VMS_I64_SSL_SOURCES_V14-503.BCK/SAVE disk:[SSL_SOURCES...]
Then copy the OpenSSL build results with the following command:
$ @INSTALL.COM disk:[SSL_SOURCES.HPE_VMS_SSL_V14.KIT]
|
|
|
|
|
|
» Download HPE SSL1 Version 1.0-2G for OpenVMS Integrity servers Source Code Kit
(March, 2016)
» Download HPE SSL1 Version 1.0-2G for OpenVMS Alpha Source Code Kit
(March, 2016)
» Download HPE SSL1 Version 1.0-2C for OpenVMS Integrity servers Source Code Kit
(November, 2015))
» Download HPE SSL1 Version 1.0-2C for OpenVMS Alpha Source Code Kit
(November, 2015)
» Download HP SSL Version 1.4-502 for OpenVMS Integrity servers Source Code Kit
(February, 2015))
» Download HP SSL Version 1.4-502 for OpenVMS Alpha Source Code Kit
(February, 2015)
» Download HP SSL Version 1.4-495 for OpenVMS Integrity servers Source Code Kit
(December, 2014)
» Download HP SSL Version 1.4-495 for OpenVMS Alpha Source Code Kit
(December, 2014)
» Download HP SSL Version 1.4-493 for OpenVMS Alpha Source Code Kit
(August, 2014)
» Download HP SSL Version 1.4-493 for OpenVMS Alpha Source Code Kit
(August, 2014)
» Download
HP SSL Version 1.4-476 for OpenVMS Integrity servers Source Code Kit
(June, 2014)
» Download
HP SSL Version 1.4-476 for OpenVMS Alpha Source Code Kit
(June, 2014)
» Download
HP SSL Version 1.4-471 for OpenVMS Alpha Source Code Kit
(March, 2013)
» Download
HP SSL Version 1.4-471 for OpenVMS Integrity servers Source Code Kit
(March, 2013)
» Download
HP SSL Version 1.4-467 for OpenVMS Alpha Source Code Kit
(June, 2012)
» Download
HP SSL Version 1.4-467 for OpenVMS Integrity servers Source Code Kit
(June, 2012)
» Download
HP SSL Version 1.4-453 for OpenVMS Alpha Source Code Kit
(March, 2011)
» Download
HP SSL Version 1.4-453 for OpenVMS Integrity servers Source Code Kit
(March, 2011)
» Download
HP SSL Version 1.4 for OpenVMS Alpha Source Code Kit
(May, 2010)
» Download
HP SSL Version 1.4 for OpenVMS Integrity servers Source Code Kit
(May, 2010)
|
» Return to the HP SSL home page
|
