Mail Archives: djgpp-announce/2013/12/12/21:34:49.1
This is a port of OpenSSL 1.0.1e to MSDOS/DJGPP.
The OpenSSL Project is an Open Source toolkit implementing the Secure Sockets
Layer (SSL v2/v3) and Transport Layer Security (TLS v1) protocols as well as
a full-strength general purpose cryptography library. OpenSSL is based on
the excellent SSLeay library developed from Eric A. Young and Tim J. Hudson.
The OpenSSL toolkit is licensed under a dual-license (the OpenSSL license
plus the SSLeay license) situation, which basically means that you are free
to get and use it for commercial and non-commercial purposes as long as you
fulfill the conditions of both licenses.
The only difference between this release and the previous one is that it has
been compiled using the release 2 of the watt-32 library (wat3222br2.zip).
DJGPP specific changes.
=======================
Fortunately, OpenSSL supports DJGPP out-of-the-box so there is no need to
adjust the source code itself. Neither less there are assumptions made about
the file system used and its capabilities that require some changes in the
perl configuration scripts and in the way source package is unzipped.
- all new DJGPP specific files are store in the /djgpp directory.
- to install, configure and compile the sources LFN support is required.
- all links (linked files) in the archive have been removed. Depending on if
djtar or tar is used and depending on if they are from DJGPP 2.03 or 2.04
all these tar programs create different kind of files to represent those
links and this breaks either the configuration step or later the building
step.
- the /djgpp directory contains unpack.sh. This small shell script uses
djtar to create a file list of the archive, identifies the links, extract
the sources using djtar and removes all links. Of course, if you download
the DJGPP port all this has already been done.
- as usual the /djgpp directory contains also the diffs file. It shows how
I have changed some of the perl scripts used during the configuration and
building steps to check for the OS used and to copy the files instead of
trying to create links even if this is possible.
- the binaries, headers and libraries will be installed in the corresponding
directories of the DJGPP installation tree. All documentation will be
installed in /dev/env/DJDIR/share/ssl/man. This means that you will have
to adjust your MANPATH in djgpp.env if you want that the man program finds
these new manpages.
- to be able to configure and compile this port, the DJGPP port of perl must
be installed. openssl uses a mix of perl scripts and Makefiles to configure
and compile the sources. I have used perl588b but the previous one may work
as well but I have never tested this.
- to be able to configure and compile this port, the DJGPP port of WATT32
must be installed. It can be downloaded as:
ftp://ftp.delorie.com/pub/djgpp/current/v2tk/wat3222br2.zip
or:
ftp://ftp.delorie.com/pub/djgpp/beta/v2tk/wat3222br2.zip
As usual the version from the /current directory is for the use with
djdev203 and the one from the /beta directory is for the use with djdev204.
After having installed the port make sure that the WATT_ROOT environment
variable points to the directory where the headers and the library reside.
This is:
set WATT_ROOT=/dev/env/DJDIR/net/watt
Due to the dependency of WATT-32 and the required value of the WATT_ROOT
environment variable, the source package is not configured at all. You
have to install WATT-32 first and then you can configure and build openssl
as described in the original INSTALL.DJGPP file.
- the port has been configured and compiled to support for zlib compression.
The zlib port used is
ftp://ftp.delorie.com/pub/djgpp/current/v2tk/zlib128b.zip
or:
ftp://ftp.delorie.com/pub/djgpp/beta/v2tk/zlib128b.zip
but any other version of the port may work as well. As usual the version
from the /current directory is for the use with djdev203 and the one from
the /beta directory is for the use with djdev204.
- the test suite passes for both djdev203 and djdev204 except for the last test
that requires some certificate that needs to be requested. For some test,
it is also required that the port of GNU bc is installed.
- the binary package of openssl ist not completely SFN clean. But this
concerns the manpages only. Neither the libraries nor the headers are
affected. I do not have the time to invent SFN clean names for hundreds
of manpages which names may change and become useless with the next openssl
update. Of course, the headers and libraries are 8.3 clean and the use of
the libraries do not require LFN support at all.
- as any cryptographic software, openssl needs a source of unpredictable data
to work correctly. Many open source operating systems provide a "randomness
device" (/dev/urandom or /dev/random) that serves this purpose. As of
version 0.9.7f of openssl the DJGPP port checks upon /dev/urandom$ for a
3rd party "randomness" DOS driver. One such driver, NOISE.SYS, can be
obtained from "http://www.rahul.net/dkaufman/index.html" as:
<http://www.rahul.net/dkaufman/noise063a2.zip>
Please read the instructions carefully. This driver works on DOS and may
be on some versions of Windows but it does not work for all versions of
Windows. For XP it does not work and I have found no replacement. This
means that for WinXP and probably for Win2K there is there is no "randomness"
support for openssl available.
- most but not all programs of the /examples directory can be successfully
compiled but they may not work. I have no intention to fix them, neither
less they may serve as example how to use the library and how to compile
and link your application with this library together with the WAT32 library
and the zlib library.
- the binaries have been build on WinXP using djdev203 or djdev204, gcc473b
and bnu224b.
Configuring, compiling and running the test suite takes around 01:30 h.
For further information about OpenSSL please read the man pages,
various README files and NEWS file. Also visit the home page of openssl.
Please note that I am not an user of openssl. I have only ported it because
I needed it to create another port. This means that I am not able to answer
openssl specific questions.
Please do _NOT_ mix libraries. I you decide to compile your project using
DJGPP 2.03 use the openssl and watt32 libraries from the /current directory.
But if you use DJGPP 2.04 then use the openssl and watt32 libraries from the
/beta directory.
Do _NOT_ mix libraries compiled with different versions of DJGPP.
The port has been compiled using stock djdev203 (patchlevel 2) and consists
of two packages that can be downloaded from ftp.delorie.com and mirrors as
(time stamp 2013-12-12):
OpenSSL 1.0.1e binary, headers, libraries and man format documentation:
ftp://ftp.delorie.com/pub/djgpp/current/v2tk/ssl101ebr2.zip
OpenSSL 1.0.1e source:
ftp://ftp.delorie.com/pub/djgpp/current/v2tk/ssl101esr2.zip
The binaries have been produced a second time using the stock version of
djdev204 beta library. This package is available at ftp.delorie.com and
mirrors as (time stamp 2013-12-12):
OpenSSL 1.0.1e binary, headers, libraries and man format documentation:
ftp://ftp.delorie.com/pub/djgpp/current/v2tk/ssl101ebr2.zip
I have removed the previous release.
Send openssl specific bug reports to <openssl-bugs AT openssl DOT org>.
Send suggestions and bug reports concerning the DJGPP port to
comp.os.msdos.djgpp or <djgpp AT delorie DOT com>.
If you are not sure if the failure is really a openssl failure
or a djgpp specific failure, report it here and *not* to
<openssl-bugs AT openssl DOT org>.
Enjoy.
Guerrero, Juan Manuel <juan DOT guerrero AT gmx DOT de>
- Raw text -