In message <CMM.0.91.0.1038677515.jaltman@watsun> on Sat, 30 Nov 2002 12:31:55 EST,
Jeffrey Altman <[EMAIL PROTECTED]> said:
jaltman> The only thing I have not done yet for VMS is provide default
jaltman> locations for the System-wide and User-specific locations for the
jaltman> storing of CERTS/KEYS and CRLs.
jaltman>
jaltman> Could some post a description of what is considered standard practice?
Standard practice under VMS is to install with the command procedure
install.com with a directory as argument. It creates a directory
structure reminding of the one built under /usr/local/ssl on Unix,
with a subdirectory [.VMS] that contains startup scripts,
openssl_startup.com and openssl_utils.com. openssl_startup.com builds
logical names (like SSLROOT, which points at the top of the created
directory structure), and is basically meant to be run at system
startup. openssl_utils.com defines command symbols, and is meant to
be run as part of the system-wide login procedure, or any procedure
you want that need those command symbols defined.
Did that answer your question?
--
Richard Levitte \ Spannv�gen 38, II \ [EMAIL PROTECTED]
Redakteur@Stacken \ S-168 35 BROMMA \ T: +46-8-26 52 47
\ SWEDEN \ or +46-708-26 53 44
Procurator Odiosus Ex Infernis -- [EMAIL PROTECTED]
Member of the OpenSSL development team: http://www.openssl.org/
Unsolicited commercial email is subject to an archival fee of $400.
See <http://www.stacken.kth.se/~levitte/mail/> for more info.
______________________________________________________________________
OpenSSL Project http://www.openssl.org
Development Mailing List [EMAIL PROTECTED]
Automated List Manager [EMAIL PROTECTED]
