HP OpenVMS Systems

The HP SSL Version 1.4 source code kits can be built on OpenVMS Alpha Version 8.3 or higher and OpenVMS Integrity server Version 8.3 or higher (refer SSL support matrix). See the Instructions for Building HP SSL on OpenVMS for more information.

Download the appropriate source code kit. The compressed file contains approximately 14,000 blocks.

» 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)
» Download HP SSL V1.3 for OpenVMS Alpha Source Code Kit (September 12, 2006)
» Download HP SSL V1.3 for OpenVMS Integrity servers Source Code Kit (September 12, 2006)

To expand the HP SSL source kit self-extracting file, enter one of the following commands, depending on the platform on which you downloaded the kit:

$ RUN HP_VMS_SSL_SOURCES_V14-476.AXPEXE  !  for OpenVMS Alpha
$ RUN HP_VMS_SSL_SOURCES_V14-476.I64EXE    !  for OpenVMS Integrity servers

The system expands the file and names the decompressed file:
HP_VMS_ALPHA_SSL_SOURCES_V14-476.BCK
or
HP_VMS_I64_SSL_SOURCES_V14-476.BCK.

If you previously installed a source code kit for an earlier version of HP SSL, remove the previous version source directory tree or create a new directory tree for the Version 1.4 source code kit.

To restore the HP SSL sources backup saveset, enter the following commands:

$ CREATE/DIR disk:[directory]
$ BACKUP HP_VMS_SSL_SOURCES_V14.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]. HP SSL creates a subdirectory named [.HP_VMS_SSL_V14...].

For example, if you specify DKA0:[SSL_SOURCES...] on the BACKUP command line, the resultant directory tree is DKA0:[SSL_SOURCES.HP_VMS_SSL_V 14...].

1. 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.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.

2. 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 RC5 and IDEA symmetric ciphers have been disabled because of licensing restrictions.

       $ search makevms.log "-E-"
       %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.
       $
       $ search makevms.log "-W-"
       %CC-W-EMPTYFILE, Source file does not contain any declarations.
       %LIBRAR-W-COMCOD, compilation warnings in module E_IDEA file
       DKA500:[COMPAQ_SSL.HP_VMS_SSL_V14.ALPHA.OBJ.CRYPTO]E_IDEA.OBJ;1
       %CC-W-EMPTYFILE, Source file does not contain any declarations.
       %LIBRAR-W-COMCOD, compilation warnings in module E_RC5 file
       DKA500:[COMPAQ_SSL.HP_VMS_SSL_V14.ALPHA.OBJ.CRYPTO]E_RC5.OBJ;1
       $
   

3. Execute regression tests.

   Execute the following command procedure to run the OpenSSL regression tests.

   $ @[.TEST]TESTS
   

4. 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 HP SSL sources using the command:

   $ BACKUP HP_VMS_SSL_SOURCES_V14.EXE/SAVE disk:[SSL_SOURCES...]
   

   Then copy the OpenSSL build results with the following command:

   $ @INSTALL.COM disk:[SSL_SOURCES.HP_VMS_SSL_V14.KIT]
   
   
   

» Return to the HP SSL home page