Amos Latteier and Anthony Baxter illuminated thusly:
HTTPS=on
Capital! This was it. Thanks! I've put together a tarball of my additions to ZServer to do https. It can be had here: http://www.post1.com/home/ngps/m2 Here's the README_SSL.txt from the tarball: 12 Oct 1999 ------------- This is a drop-in (well, almost) enhancement to Zope-2.0.1-src to enable https support. Unpack the package in Zope's top-level directory. The files in the tarball are additions to the standard distribution, except ZServer/__init__.py; i.e., the only file clobbered when you unpack this package is ZServer/__init__.py. For the careful, here's the diff to ZServer/__init__.py: --- __init__.py.org Tue Oct 12 22:21:35 1999 +++ __init__.py Tue Oct 12 22:21:35 1999 @@ -121,6 +121,7 @@ from medusa import resolver, logger, asyncore from HTTPServer import zhttp_server, zhttp_handler +from HTTPS_Server import zhttps_server from PCGIServer import PCGIServer from FTPServer import FTPServer from PubCore import setNumberOfThreads The file ca.pem contains my CA certificate. The file server.pem contains a certificate for the server, signed by the CA; its RSA private key is not protected by a passphrase. These certificates are for DEMONSTRATION only. SSL support is provided by M2Crypto, which is available at: http://www.post1.com/home/ngps/m2 Please use the current snapshot. Obtain and install M2Crypto. Then start the Zope https server thusly: ./starts -W 8443 <usual other parameters> HTTPS=on Note that this is alpha software, no warranty, etc. Feedback is very much appreciated. Cheers. -- Ng Pheng Siong <ngps@post1.com>