This is the README for HTTPS.1.0.m.NIS.b.tar.gz [Download] [Browse] [Up]
HTTPS v1.0 Package for OmniWeb 3.x (OpenStep 4.2/Mach)
======================================================
Jörgen Möllenhoff (jm@oic.de), January 19, 1998
Description
===========
This Package allows you to use https-URLs (via SSL) with OmniWeb 3.x.
It uses the free SSLeay-lib (Version 0.8.1) from Eric Young
(eay@cryptsoft.com) and the OmniWeb (http://www.omnigroup.com/)
extensible bundle architecture.
This software is supplied without a warranty of any kind. I am not
responsible for any damage that may occur as a result of using this
software. Please keep in mind that this is work in progress. Also,
please bear with the incomplete nature of the package.
Installation
============
ATTENTION:
Before you can install this Package you must install the SSL.pkg which
includes two Frameworks (SSLCrypto, SSL) to /LocalLibrary/Frameworks,
without these Frameworks the bundle doesn't work.
To enable the HTTPS protocol, install the ./HTTPS.omniweb
bundle anywhere in the OmniWeb 3.x bundle path. Then, restart OmniWeb.app.
The recommended location for personal installation is ~/Library/Components
for system-wide installation /LocalLibrary/Components.
If you use a proxy server, you MUST include at least one protocol
for your proxy server (http, ftp, etc. but not https) in the
protocol section of the Proxy-Preferences Panel or add the "https"
protocol to the NonProxiableSchemes like
defaults write OmniWeb NonProxiableSchemes "(file, mailto, omniweb, rlogin, telnet, tn3270, https)"
Without these "workarounds" OmniWeb wraps https calls to http!!!
CONNECT-Protocol (Proxy Support for https)
==========================================
To enable proxy support for https (SSL tunneling) you need another entry in
the Proxy-Preferences Panel. Add a server to the "Proxy Server URL" section
like this: "https:\\whatever-cache:1234\" and add the https protocol to the
"Protocols" section. IMPORTANT: The https proxy MUST be the first server in
the list, because the list of proxy servers is an ordered list.
For example my proxy defaults look like this:
ProxyServers = "(\n {\n destinations = (oic.de); \n proxyURL = \"(non-proxied protocols and destinations)\"; \n }, \n {proxyURL = \"https://www-cache.oic.de:3128/\"; schemes = (https); }, \n {proxyURL = \"http://www-cache.oic.de:3128/\"; }\n)";
History
=======
1.0
- Changed the Proxy-Support. If you need proxy support add the
proxy server now with the Proxy-Preferences Panel of OmniWeb.
- Created a Version for OmniWeb 3.x (OpenStep/Rhapsody) AND OmniWeb 2.x
- The name of the bundle for OmniWeb 3.x (OpenStep/Rhapsody) is "HTTPS", for
OmniWeb 2.x "HTTPSExtension".
0.9 (Beta)
- Added Proxy authentication for the CONNECT-Protocol.
- Fixed a bug in the Hostname resolver. Now it should be possible to
use this bundle without any DNS if you use a proxy server.
0.8 (Beta)
- Adapted the bundle for OmniWeb 3.x
- SSLeay-lib is now located in two Frameworks (SSLCrypto, SSL)
- Renamed it (sorry for that) from HTTPSExtension.omniweb to HTTPS.omniweb,
because the "new" bundle is not compatible with OmniWeb2.x, it works
ONLY for OmniWeb3.x. So it is easier for me to figure out which bundle
you mean if you have some questions about it.
0.7
- It's now SSLeay-lib in version 0.8.1.
- Supports SSLv2 and SSLv3
- Added a Preferences Panel
- Added Proxy-Support (CONNECT-Protocol) (see HTTPS Preferences)
- Added an Installer Package
- Renamed it from https.omni to HTTPSExtension.omniweb
- Fixed some bugs
- Removed the source code
0.6
- Internal version
0.5a
- It's now SSLeay-lib in version 0.5.2a.
- Fixed a little (not important) bug.
- Included the source code
0.5
- First version, which uses the SSLeay-lib in version 0.5.1b
Bugs?
=====
Yes, if you use a proxy server. You MUST include at least one protocol
for your proxy server (http, ftp, etc. but not https) in the
protocol section of the Proxy-Preferences Panel or add the "https"
protocol to the NonProxiableSchemes.
ATTENTION: Without any protocols, OmniWeb wraps https calls to http!!
Send bug reports, suggestions or comments to the address below.
Architectures
=============
ALL Architectures (INTEL, MOTOROLA and SUN) are supported. SUN are not tested!!
Warning!
=======
It is illegal to use this software inside of the USA. The PKP has
exclusive patent rights in the USA on all aspects of public key
cryptography. Sorry, but this is not my fault. If you are interested
in learning more about this, read the documentation for the SSLeay-lib
package.
Copyright
=========
This bundle is free for commercial and non-commercial use.
ToDo
====
- Client certification??
- Display an Icon when a SSL-Connection is in progress??
Source Code
===========
To compile this bundle you need the SSLeay-lib in version 0.8.1 and
the API (Headers) for OmniWeb 3.x. If you modify the source code,
please send a copy of the modifications to me <jm@oic.de>. Thank you.
Thanks
======
Thanks to
"Stefanie R. Herzer <herzer@apple.com>"
"Stephen J. Perkins <perkins@netmass.com>"
"Ken Case <kc@omnigroup.com>"
"Eric Young <eay@cryptsoft.com>"
"Tim Hudson <tjh@cryptsoft.com>"
Contact Information
===================
Jörgen Möllenhoff
OIC - Object Innovation Center
Bochum, Germany
EMail: jm@oic.de (ASCII, NEXT and MIME-Mail)
These are the contents of the former NiCE NeXT User Group NeXTSTEP/OpenStep software archive, currently hosted by Netfuture.ch.