You Are Visitor: [Image] [Previous] [Next] [Table of Contents] ------------------------------------------------------------------------ 4.1 Building OSU HTTPD SSL_TASK Support. This assumes that you have done the following. * Built the SSLeay library as outlined in Compiling SSLeay for OpenVMS * Installed the completed SSLeay library and executed the SSLEAY_STARTUP.COM file as outlined in... Installing SSLeay for OpenVMS You will also need the following if you don't have it already. * You have a copy of the OSU HTTPD server either already installed or are about to install it. The OSU HTTPD server can be found at http://kcgl1.eng.ohio-state.edu/www/doc/serverinfo.html * The updated replacement TSERVER_TCPSHR_INSTALL.COM file. [Image] * Updated/upgraded WWWSSL.COM file. [Image] * Either DEC's MMS or Matt Madison's MMK "make" utility. Matt Madison's MMK utility can be found at ftp://ftp.madgoat.com/madgoat/MMK.zip With that said and done, here are the instructions for building the OSU HTTPD server with SSL support using the SSL_TASK program. 1. If you don't have the OSU HTTPD server already installed and running you need to unpack the OSU distribution kit somewhere. (For the purpose of this discussion we'll assume you unpacked it in a directory called DISK$WORK:[HTTP_SERVER]). If you already have the OSU HTTPD server installed, you are set. 2. Go to the [.BASE_CODE] directory in the OSU HTTPD distribution. 3. You need to build the OSU HTTPD server so that it will use the shareable image TCP/IP interface. This is done as follows. $ MMS/MACRO=(SHARE_TCP=xxxx) Where the "xxxx" is one of the following. CMUTCP CMU TCP/IP MULTINET Multinet TCP/IP TCPWARE TCPWare TCP/IP TWGTCP Pathway TCP/IP UCXTCP DEC UCX TCP/IP 4. When that is done running, you need to compile the TSERVER_SSL.C and SSL_SERVER_DNET.C $ CC TSERVER_SSL.C $ CC SSL_SERVER_DNET.C 5. You now need to link the DECNet SSL server using the following. $ @LINK_TCPSHARE SSL "" SSLSHR_SERVER_DNET/OPTION 6. If that went well you should have the file TSERVER_SSL.EXE in your OSU system directory. 7. Unpack the updated replacement TSERVER_TCPSHR_INSTALL.COM file and place it in the OSU HTTPD SYSTEM directory. 8. Copy the SSL_TASK.EXE file from your [SSLEAY-0_8_1a.xxx.EXE.SSL] directory into your OSU SYSTEM directory. Make sure that which ever account you run your OSU server under can access this file. If you didn't compile the SSL_TASK.EXE when you built your SSLeay library, go to the [.SSLEAY-0_8_1A.SSL] directory and use the SSL-LIB.COM script to build it, it accepts the following parameters. P1: ALL Just build everything. LIBRARY Just build the SSL Library SSL_TASK Just build the SSL_TASK.EXE P2: RSAREF Compile using RSAREF routines. NORSAREF Don't compile using the RSAREF routines. P3: DEBUG Compile with debug information. NODEBUG Compile without debug information. P4: VAXC Use the VAXC compiler. DECC Use the DECC compiler. GNUC Use the GNUC compiler. P5: UCX Use the UCX TCP/IP routines. MULTINET Use the Multinet TCP/IP routines. SOCKETSHR Use the SOCKETSHR TCP/IP routines. You have to use the same options you originally used when you built the SSLeay library. You don't have to build the entire SSL library again, just the SSL_TASK. 9. Copy your SSL server certificate into the OSU's SYSTEM directory (you don't have to, but it helps to keep everything together.) and make sure it is readable by whatever account the OSU HTTPD server runs under. 10. Unpack the updated/upgraded WWWSSL.COM and place it in the root directory of the OSU HTTPD server. You might want to look this script over as you can define where you have the SSL_TASK.EXE and your SSL certificate if you choose not to place them in the WWW_SYSTEM directory as well defining an alternate location for the WWWSSL.LOG file. 11. Now you just need to startup the HTTPD server on port 80 and 443 like the following. $ @DISK$WORK:[HTTP_SERVER.SYSTEM]HTTP_STARTUP.COM HTTP_SERVER - DISK$WORK:[HTTP_LOGS]HTTP_ERROR.LOG - DISK$WORK:[HTTP_SERVER.SYSTEM]HTTP_MAIN.CONF - 80 443 And if the server starts up correctly, you should be able to get a secure connection using "https". ------------------------------------------------------------------------ [Previous] [Next] [Table of Contents]