Document revision date: 24 June 2002
[Compaq] [Go to the documentation home page] [How to order documentation] [Help on this site] [How to contact us]
[OpenVMS documentation]
Open Source Security for OpenVMS Alpha
Volume 2: Compaq SSL (Secure Sockets Layer) for OpenVMS Alpha
AA-RSCVA-TE
This is a new manual.
Compaq SSL Version 1.0 for OpenVMS Alpha (based on OpenSSL 0.9.6B)
OpenVMS Alpha Version 7.3-1
June 2002
Compaq Computer Corporation
Houston Texas 
© 2002 Compaq Information Technologies Group, L.P.
This manual contains installation instructions, release notes, example programs, information about programming your Compaq SSL for OpenVMS Alpha application, and reference information for the OpenSSL APIs.
Compaq, the Compaq logo, Alpha, OpenVMS, Tru64, VAX, VMS, and the DIGITAL logo are trademarks of Compaq Information Technologies Group, L.P. in the U.S. and/or other countries.
Microsoft, MS-DOS, Visual C++, Windows, and Windows NT are trademarks of Microsoft Corporation in the U.S. and/or other countries.
Intel, Intel Inside, and Pentium are trademarks of Intel Corporation in the U.S. and/or other countries.
Motif, OSF/1, and UNIX are trademarks of The Open Group in the U.S. and/or other countries.
Java and all Java-based marks are trademarks or registered trademarks of Sun Microsystems, Inc., in the U.S. and other countries.
All other product names mentioned herein may be trademarks of their respective companies.
Confidential computer software. Valid license from Compaq required for possession, use, or copying. Consistent with FAR 12.211 and 12.212, Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor’s standard commercial license.
Compaq shall not be liable for technical or editorial errors or omissions contained herein. The information in this document is provided "as is" without warranty of any kind and is subject to change without notice. The warranties for Compaq products are set forth in the express limited warranty statements accompanying such products. Nothing herein should be construed as constituting an additional warranty.
ZK6661
The Compaq OpenVMS documentation set is available on CD-ROM.
Contents
Open Source Security for OpenVMS Alpha
Volume 2: Compaq SSL (Secure Sockets Layer) for OpenVMS Alpha
Preface
Intended Audience
Document Structure
Related Documents
Reader’s Comments
How to Order Additional Documentation
Conventions
OpenSSL Open Source License
Chapter 1 Installation and Release Notes
1.1 Installation Requirements and Prerequisites
 

 

 

1.2 OpenSSL Documentation from The Open Group
1.3 Installing Compaq SSL for OpenVMS Alpha
1.4 Postinstallation Tasks
1.5 SSL Directory Structure
1.6 Building an SSL Application
 

 

1.7 Release Notes
 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

Chapter 2 Overview of SSL
2.1 The SSL Protocol
2.2 The SSL Handshake
2.3 Public Key Encryption
2.4 Certificates
2.5 Cipher Suite
2.6 Digital Signatures
Chapter 3 Using the Certificate Tool
3.1 Starting the Certificate Tool
3.2 Viewing a Certificate
3.3 View a Certificate Request File
3.4 Create a Certificate Signing Request
 

3.5 Create a Self-Signed Certificate
3.6 Create a Certificate Authority
3.7 Create a Certificate Chain
 

 

 

3.8 Sign a Certificate Signing Request
3.9 Hash Certificates
3.10 Hash Certificate Revocations
Chapter 4 SSL Programming Concepts
4.1 SSL Data Structures
 

 

 

 

 

 

4.2 Certificates for SSL Applications
 

 

4.3 SSL Programming Tutorial
 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

Chapter 5 OpenSSL Command Line Interface
5.1 Command-Line Help
5.2 Standard Commands
5.3 Message Digest Commands
5.4 Encoding and Cipher Commands
5.5 Password Arguments
5.6 Creating a DH Parameter (Key) File and a DSA Certificate and Key
Chapter 6 Example Programs
6.1 Programs Included in Compaq SSL Kit
6.2 Simple SSL Client Program
6.3 Simple SSL Server Program
6.4 Creating Certificates and Keys for the Example Programs
Application Programming Interface (API) Reference
asn1parse
bio
BIO_ctrl
BIO_ctrl_get_read_request
BIO_ctrl_pending
BIO_f_base64
BIO_f_buffer
BIO_f_cipher
BIO_f_md
BIO_f_null
BIO_f_ssl
BIO_find_type
BIO_new
BIO_new_bio_pair
BIO_push
BIO_read
BIO_s_accept
BIO_s_bio
BIO_s_connect
BIO_s_fd
BIO_s_file
BIO_s_mem
BIO_s_null
BIO_s_socket
BIO_set_callback
BIO_should_retry
blowfish
bn
BN_add
BN_add_word
BN_bn2bin
BN_cmp
BN_copy
BN_CTX_new
BN_CTX_start
BN_generate_prime
bn_internal
BN_mod_inverse
BN_mod_mul_montgomery
BN_mod_mul_reciprocal
BN_new
BN_num_bytes
BN_rand
BN_set_bit
BN_zero
buffer
CA.pl
ca
ciphers
crl
crl2pkcs7
crypto
CRYPTO_set_ex_data
d2i_DHparams
d2i_RSAPublicKey
d2i_SSL_SESSION
des
des_modes
dgst
dh
DH_generate_key
DH_generate_parameters
DH_get_ex_new_index
DH_new
DH_set_method
DH_size
dsa
DSA_do_sign
DSA_dup_DH
DSA_generate_key
DSA_generate_parameters
DSA_get_ex_new_index
DSA_new
DSA_set_default_openssl_method
DSA_SIG_new
DSA_sign
DSA_size
dsaparam
enc
err
ERR_clear_error
ERR_error_string
ERR_get_error
ERR_GET_LIB
ERR_load_crypto_strings
ERR_load_SSL_strings
ERR_load_strings
ERR_print_errors
ERR_put_error
ERR_remove_state
evp
EVP_DigestInit
EVP_EncryptInit
EVP_OpenInit
EVP_SealInit
EVP_SignInit
EVP_VerifyInit
gendsa
genrsa
HMAC
lh_stats
lhash
md5
MDC2
nseq
openssl
OpenSSL_add_all_algorithms
OPENSSL_VERSION_NUMBER
passwd
pem
pkcs12
pkcs7
pkcs8
rand
RAND_add
RAND_bytes
RAND_cleanup
RAND_egd
RAND_load_file
RAND_set_rand_method
rand_ssl
rc4
req
RIPEMD160
rsa
RSA_blinding_on
RSA_check_key
RSA_generate_key
RSA_get_ex_new_index
RSA_new
RSA_padding_add_PKCS1_type_1
RSA_print
RSA_private_encrypt
RSA_public_encrypt
RSA_set_method
RSA_sign
RSA_sign_ASN1_OCTET_STRING
RSA_size
rsautl
s_client
s_server
sess_id
SHA
smime
speed
spkac
ssl
SSL_accept
SSL_alert_desc_string
SSL_alert_type_string
SSL_callback_ctrl
SSL_check_private_key
SSL_CIPHER_get_name
SSL_clear
SSL_COMP_add_compression_method
SSL_connect
SSL_copy_session_id
SSL_ctrl
SSL_CTX_add_extra_chain_cert
SSL_CTX_add_session
SSL_CTX_ctrl
SSL_CTX_flush_sessions
SSL_CTX_free
SSL_CTX_get_cert_store
SSL_CTX_get_ex_new_index
SSL_CTX_get_quiet_shutdown
SSL_CTX_get_verify_mode
SSL_CTX_load_verify_locations
SSL_CTX_new
SSL_CTX_sess_number
SSL_CTX_sess_set_cache_size
SSL_CTX_sess_set_get_cb
SSL_CTX_sessions
SSL_CTX_set_cert_store
SSL_CTX_set_cert_verify_cb
SSL_CTX_set_cipher_list
SSL_CTX_set_client_CA_list
SSL_CTX_set_def_verify_paths
SSL_CTX_set_default_passwd_cb
SSL_CTX_set_info_callback
SSL_CTX_set_mode
SSL_CTX_set_options
SSL_CTX_set_purpose
SSL_CTX_set_quiet_shutdown
SSL_CTX_set_session_cache_mode
SSL_CTX_set_session_id_context
SSL_CTX_set_ssl_version
SSL_CTX_set_timeout
SSL_CTX_set_tmp_dh_callback
SSL_CTX_set_tmp_rsa_callback
SSL_CTX_set_trust
SSL_CTX_set_verify
SSL_CTX_use_certificate
SSL_do_handshake
SSL_dup
SSL_dup_CA_list
SSL_free
SSL_get_certificate
SSL_get_ciphers
SSL_get_client_CA_list
SSL_get_current_cipher
SSL_get_default_timeout
SSL_get_error
SSL_get_ex_data_X509_STORE_CTX_idx
SSL_get_ex_new_index
SSL_get_fd
SSL_get_finished
SSL_get_info_callback
SSL_get_peer_cert_chain
SSL_get_peer_certificate
SSL_get_peer_finished
SSL_get_privatekey
SSL_get_quiet_shutdown
SSL_get_rbio
SSL_get_read_ahead
SSL_get_session
SSL_get_shared_ciphers
SSL_get_SSL_CTX
SSL_get_verify_result
SSL_get_version
SSL_library_init
SSL_load_client_CA_file
SSL_new
SSL_peek
SSL_pending
SSL_read
SSL_renegotiate
SSL_rstate_string
SSL_SESSION_cmp
SSL_SESSION_free
SSL_SESSION_get_ex_new_index
SSL_SESSION_get_time
SSL_SESSION_hash
SSL_SESSION_new
SSL_SESSION_print SSL_SESSION_print_fp
SSL_session_reused
SSL_set_bio
SSL_set_connect_state
SSL_set_fd
SSL_set_info_callback
SSL_set_purpose
SSL_set_quiet_shutdown
SSL_set_read_ahead
SSL_set_session
SSL_set_shutdown
SSL_set_trust
SSL_set_verify_result
SSL_shutdown
SSL_state
SSL_state_string
SSL_version
SSL_want
SSL_write
threads
verify
version
x509
Appendix A Data Structures and Header Files















Preface

Intended Audience

This document is for application developers who want to protect communication links to OpenVMS applications. The OpenSSL APIs establish private, authenticated and reliable communications link between applications.

Document Structure

This manual consists of the following chapters:
Chapter 1 contains installation instructions and release notes.
Chapter 2 provides an overview of SSL.
Chapter 3 includes information about the Certificate Tool.
Chapter 4 is a programming tutorial about how to use the OpenSSL APIs in your application program.
Chapter 5 describes the OpenSSL command line utility.
Chapter 6 lists the example programs included in the Compaq SSL kit.
Chapter 7 is a reference section that includes documentation from The Open Group about the OpenSSL application programming interfaces (APIs).
Appendix A lists the header files and the data structures included in Compaq SSL for OpenVMS Alpha.

Related Documents

The following documents are recommended for further information:
• Open Source Security for OpenVMS Alpha Volume 1: CDSA (Common Data Security Architecture)
• OpenSSL documentation from The Open Group is available at the following URL:
http://www.openssl.org
For additional information about Compaq OpenVMS products and services, see the Compaq web site at thefollowing URL:
http://www.openvms.compaq.com
For additional information about OpenSSL, see the OpenSSL web site at the following URL:
http://www.openssl.org

Reader’s Comments

Compaq welcomes your comments on this manual. Please send comments to either of the following addresses:
Internet
openvmsdoc@compaq.com
Mail
Compaq Computer Corporation
OSSG Documentation Group, ZKO3-4/U08
110 Spit Brook Rd.
Nashua, NH 03062-2698

How to Order Additional Documentation

Visit the following World Wide Web address for information about how to order additional documentation:
http://www.openvms.compaq.com

Conventions

Writers: Delete those conventions not applicable in your book.
The following conventions are used in this manual:
Ctrl/ x
Indicates that you must hold down the key labeled Ctrl while you press another key or a pointing device button.
PF1x
A sequence such as PF1x indicates that you must first press and release the key labeled PF1 and then press and release another key or a pointing device button.
[Return]
In an example, a key name enclosed in a box indicates that you press that key.
A horizontal ellipsis in examples indicates one of the following possibilities:
• Additional optional arguments in a statement have been omitted.
• The preceding item or items can be repeated one or more times.
• Additional parameters, values, or other information can be entered.
A vertical ellipsis indicates the omission of items from a code example or command format; the items are omitted\par because they are not important to the topic being discussed.
( )
In command format descriptions, parentheses indicate that you must enclose choices in parentheses if you specify more than one.
[ ]
In command format descriptions, brackets indicate optional choices. You can choose one or more items or no items. Do not type the brackets on the command line. However, you must include the brackets in the syntax for OpenVMS directory specifications and for a substring specification in an assignment statement.
|
In command format descriptions, vertical bars separate choices within brackets or braces. Within brackets, the choices are optional; within braces, at least one choice is required. Do not type the vertical bars on the command line.
{ }
In command format descriptions, braces indicate required choices; you must choose at least one of the items listed. Do not type the braces on the command line.
Type
This typeface represents the introduction of a new. It also represents the name of argument an attribute, or a reason.
italics
Italic text indicates important information, complete titles of manuals, or variables. Variables include information that varies in system output (Internal error number), in command lines (/PRODUCER=name), and in command parameters in text (where (dd) represents the predefined par code for the device type.
UPPERCASE TEXT
Uppercase text indicates a command, the name of a routine, the name of a file, or the abbreviation for a system privilege.
Monospace text
Monospace type indicates code examples and interactive screen displays.
In the C programming language, monospace type in text identifies the following elements: keywords, the names of independently compiled externalfunctions and files, syntax summaries, and references to variables or identifiers introduced in an example.
A hyphen at the end of a command format description, command line, or code line indicates that the command or statement continues on the following line.
numbers
All numbers in text are assumed to be decimal unless otherwise noted. Nondecimal radixes---binary, octal, or hexadecimal---are explicitly indicated.

OpenSSL Open Source License

  OpenSSL License
  ---------------
 ====================================================================
 * Copyright (c) 1998-2002 The OpenSSL Project.  All rights reserved.
 *
 * Redistribution and use in source and binary forms, with or without
 * modification, are permitted provided that the following conditions
 * are met:
 * 1. Redistributions of source code must retain the above copyright
 *    notice, this list of conditions and the following disclaimer. 
 * 2. Redistributions in binary form must reproduce the above copyright
 *    notice, this list of conditions and the following disclaimer in
 *    the documentation and/or other materials provided with the
 *    distribution.
 * 3. All advertising materials mentioning features or use of this
 *    software must display the following acknowledgment:
 *    "This product includes software developed by the OpenSSL Project
 *    for use in the OpenSSL Toolkit. (http://www.openssl.org/)"
 * 4. The names "OpenSSL Toolkit" and "OpenSSL Project" must not be used to
 *    endorse or promote products derived from this software without
 *    prior written permission. For written permission, please contact
 *    openssl-core@openssl.org.
 * 5. Products derived from this software may not be called "OpenSSL"
 *    nor may "OpenSSL" appear in their names without prior written
 *    permission of the OpenSSL Project.
 * 6. Redistributions of any form whatsoever must retain the following
 *    acknowledgment:
 *    "This product includes software developed by the OpenSSL Project
 *    for use in the OpenSSL Toolkit (http://www.openssl.org/)"
 * THIS SOFTWARE IS PROVIDED BY THE OpenSSL PROJECT ‘‘AS IS’’ AND ANY
 * EXPRESSED OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
 * IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR
 * PURPOSE ARE DISCLAIMED.  IN NO EVENT SHALL THE OpenSSL PROJECT OR
 * ITS CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
 * SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT
 * NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES;
 * LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
 * HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
 * STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE)
 * ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED
 * OF THE POSSIBILITY OF SUCH DAMAGE.
 * ====================================================================
 *
 * This product includes cryptographic software written by Eric Young
 * (eay@cryptsoft.com).  This product includes software written by Tim
 * Hudson (tjh@cryptsoft.com).
 *
 */ Original SSLeay License
    -----------------------

 /* Copyright (C) 1995-1998 Eric Young (eay@cryptsoft.com)
 * All rights reserved.
 *
 * This package is an SSL implementation written
 * by Eric Young (eay@cryptsoft.com).
 * The implementation was written so as to conform with Netscapes SSL.
 * 
 * This library is free for commercial and non-commercial use as long as
 * the following conditions are aheared to.  The following conditions
 * apply to all code found in this distribution, be it the RC4, RSA,
 * lhash, DES, etc., code; not just the SSL code.  The SSL documentation
 * included with this distribution is covered by the same copyright terms
 * except that the holder is Tim Hudson (tjh@cryptsoft.com).
 *
 * Copyright remains Eric Young’s, and as such any Copyright notices in
 * the code are not to be removed.
 * If this package is used in a product, Eric Young should be given attribution
 * as the author of the parts of the library used.
 * This can be in the form of a textual message at program startup or
 * in documentation (online or textual) provided with the package.
 * 
 * Redistribution and use in source and binary forms, with or without
 * modification, are permitted provided that the following conditions
 * are met:
 * 1. Redistributions of source code must retain the copyright
 *    notice, this list of conditions and the following disclaimer.
 * 2. Redistributions in binary form must reproduce the above copyright
 *    notice, this list of conditions and the following disclaimer in the
 *    documentation and/or other materials provided with the distribution.
 * 3. All advertising materials mentioning features or use of this software
 *    must display the following acknowledgement:
 *    "This product includes cryptographic software written by
 *     Eric Young (eay@cryptsoft.com)"
 *    The word ’cryptographic’ can be left out if the rouines from the library
 *    being used are not cryptographic related :-).
 * 4. If you include any Windows specific code (or a derivative thereof) from 
 *    the apps directory (application code) you must include an acknowledgement:
 *    "This product includes software written by Tim Hudson (tjh@cryptsoft.com)"
 * 
 * THIS SOFTWARE IS PROVIDED BY ERIC YOUNG ‘‘AS IS’’ AND
 * ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
 * IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
 * ARE DISCLAIMED.  IN NO EVENT SHALL THE AUTHOR OR CONTRIBUTORS BE LIABLE
 * FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
 * DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
 * OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
 * HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
 * LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
 * OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
 * SUCH DAMAGE.
 * 
 * The licence and distribution terms for any publically available version or
 * derivative of this code cannot be changed.  i.e. this code cannot simply be
 * copied and put under another distribution licence
 * [including the GNU Public Licence.]
 */

1    Installation and Release Notes

This chapter contains hardware and software prerequisites, installation instructions, postinstallation tasks, instructions for building your application, the SSL directory structure, and release notes for Compaq SSL V1.0 for OpenVMS Alpha. For an overview of SSL, see Chapter 2, Overview of SSL.

1.1  Installation Requirements and Prerequisites

The following sections list hardware and disk space requirements, and software prerequisites.

1.1.1  Hardware Prerequisites

Compaq SSL is available only on the Alpha platform. You can install Compaq SSL on any AlphaServer system or on any Alpha workstation running OpenVMS Version 7.2-2 or higher.

Disk Space Requirements

The Compaq SSL for OpenVMS Alpha kit requires approximately 45,000 blocks of working disk space to install. Once installed, the software occupies approximately 40,000 blocks of disk space.

1.1.2  Software Prerequisites

Compaq SSL for OpenVMS Alpha requires the following software:
• OpenVMS Alpha Version 7.2-2 or higher
• Compaq TCP/IP Services for OpenVMS Version 5.0A or higher
Compaq SSL for OpenVMS Alpha has been tested and verified using Compaq TCP/IP Services for OpenVMS. There are no known problems running Compaq SSL for OpenVMS Alpha with other TCP/IP network products. This includes the following TCP/IP network products from Process Software Corporation, but Compaq has not formally tested and verified these other products:
• TCPware Version 5.5
• MultiNet Version 4.3

1.1.3  Account Quotas and System Parameters

There are no specific requirements for account quotas and system parameters for installing or using Compaq SSL for OpenVMS Alpha.

1.2  OpenSSL Documentation from The Open Group

Documentation about the OpenSSL project and The Open Group is available at the following URL:
http://www.openssl.org
The OpenSSL documentation was written for UNIX users. When reading UNIX-style OpenSSL documentation, note the following differences between UNIX and OpenVMS:
• File specification format
The OpenSSL documentation shows example file specifications in UNIX format. For example, the UNIX file specification /dka100/foo/bar/file.dat is equivalent to DKA100:[FOO.BAR]FILE.DAT on OpenVMS.
• Directory format
Directories (pathnames) that begin with a period (.) on UNIX begin with an underscore (_) on OpenVMS. In addition, on UNIX, the tilde (~) is an abbreviation for SYS$LOGIN. For example, the UNIX pathname ~/.openssl/profile/prefs.js is equivalent to the OpenVMS directory [._OPENSSL.PROFILE]PREFS.JS.

1.3  Installing Compaq SSL for OpenVMS Alpha

Compaq SSL for OpenVMS Alpha is shipped with OpenVMS Alpha Version 7.3-1 on the Layered Products CD-ROM. You must install Compaq SSL before you can use it. Use the following procedure to install Compaq SSL for OpenVMS Alpha.
To install the SSL for OpenVMS Alpha kit, enter the following command:
$ PRODUCT INSTALL SSL/SOURCE=ddcu:[dir]
By default, SSL for OpenVMS Alpha is installed into SYS$SYSDEVICE:[VMS$COMMON]. You can specify a different installation location by using the PRODUCT INSTALL command line qualifier /DESTINATION.
For a description of the features you can request with the PRODUCT INSTALL command when starting an installation, such as running the IVP, purging files, and configuring the installation, refer to the POLYCENTER Software Installation Utility User’s Guide.
As the installation procedure progresses, the system displays information similar to the following:
$ product install ssl/source=dka300:[kits]

   1 - CPQ AXPVMS SSL V1.0                 Layered Product
   2 - CPQ AXPVMS SSL T1.0                 Layered Product
   3 - All products listed above
   4 - Exit

Choose one or more items from the menu separated by commas: 1

The following product has been selected:
    CPQ AXPVMS SSL V1.0                    Layered Product

Do you want to continue? [YES]

Configuration phase starting ...

You will be asked to choose options, if any, for each selected product
and for any products that may be installed to satisfy software 
dependency requirements.

CPQ AXPVMS SSL V1.0: SSL for OpenVMS Alpha V1.0 (Based on OpenSSL 0.9.6B).

    (c) Compaq Computer Corporation 2002. All rights reserved.

Do you want the defaults for all options? [YES]

Do you want to review the options? [NO]

Execution phase starting ...

The following product will be installed to destination:
    CPQ AXPVMS SSL V1.0                    DISK$DWLLNG_A_V73:[VMS$COMMON.]
The following product will be removed from destination:
    CPQ AXPVMS SSL T1.0                    DISK$DWLLNG_A_V73:[VMS$COMMON.]

Portion done: 0%...10%...20%...30%...40%...50%...60%...70%...80%...90%...100%

The following product has been installed:
    CPQ AXPVMS SSL V1.0                    Layered Product
The following product has been removed:
    CPQ AXPVMS SSL T1.0                    Layered Product

%PCSI-I-IVPEXECUTE, executing test procedure for CPQ AXPVMS SSL V1.0 ... 
%PCSI-I-IVPSUCCESS, test procedure completed successfully

CPQ AXPVMS SSL V1.0: SSL for OpenVMS Alpha V1.0 (Based on OpenSSL 0.9.6B).

    Insert the following lines in SYS$MANAGER:SYSTARTUP_VMS.COM:
        @sys$startup:ssl$startup.com
    Insert the following lines in SYS$MANAGER:SYSHUTDWN.COM:
        @sys$startup:ssl$shutdown.com

    There are post installation activities that need to be performed.

    This includes things like defining logical names and running SSL$UTILS.COM
    to define some foreign symbols, and running the IVP if it was not done
    as part of the installation.  Refer to the Release Notes for more
    information about activities that should be performed once the installation
    has finished.

    SSL has created the following directory structure in
    PCSI$DESTINATION, which defaults to SYS$SYSDEVICE:[VMS$COMMON]:

     [SSL] -                Top-level SSL directory
     [SSL.ALPHA_EXE] -      Contains the images for the Alpha platform.
     [SSL.COM] -            Directory to hold the various command procedures.
     [SSL.DEMOCA] -         Directory structure to demo SSL’s CA features
     [SSL.DEMOCA.CERTS] -   Directory to hold the certificates and keys
     [SSL.DEMOCA.CONF] -    Contains the configuration files.
     [SSL.DEMOCA.CRL] -     Contains revoked certificates and CRLs
     [SSL.DEMOCA.PRIVATE] - Directory for private keys and random data.
     [SSL.INCLUDE] -        Contains the C Header (.H) files.
     [SSL.TEST] -           Contains the files used during the IVP.


    Refer to SYS$HELP:SSL010.RELEASE_NOTES for more information.

    @SYS$STARTUP:SSL$STARTUP.COM should be run at system startup.
$

Stopping and Restarting the Installation

Use the following procedure to stop and restart the installation:
1. To stop the procedure at any time, press Ctrl/Y.
2. Enter the DCL command PRODUCT REMOVE to reverse any changes to the system that occurred during the partial installation. This deletes all files created up to that point and causes the installation procedure to exit.
3. To restart the installation, go back to the beginning of the installation procedure.

1.4  Postinstallation Tasks

After the installation is complete, perform the following steps:
1. Add the following line to the system startup file,
SYS$STARTUP:SYSTARTUP_VMS.COM, to set up the SSL symbols and logical names:
$ @SYS$STARTUP:SSL$STARTUP
2. At the DCL command prompt, execute the command that you entered into the system startup file so that you can use SSL immediately:
$ @SYS$STARTUP:SSL$STARTUP
3. Define the foreign commands that use the OpenSSL utility OPENSSL.EXE, such as openssl, ca, enc, req, and X509, by entering the following command:
$ @SSL$COM:SSL$UTILS
4. Optionally, start the Certificate Tool by entering the following command:
$ @SSL$COM:SSL$CERT_TOOL
This menu-driven tool allows you to create