[Has anyone figured-out what makes the number 393 so interesting to PW, now?]
I wonder what was going through Jordan's head during his infamous
$Id$-smashing commit.
Before I forget....
Thanks to naddy@mips.rhein-neckar.de (Christian Weisgerber) for prompting
this commit. See msg-id: 7geokh$tje$1@mips.rhein-neckar.de
This fixes two really nasty bugs, so users are encouraged to upgrade.
Additionally a little bit more portlint cleanups were done and switched to
HAS_CONFIGURE from GNU_CONFIGURE now that we've the CONFIG_TARGET stuff...
were alternated so the user does not have to get 10 apache MASTER_SITEs when all
they need is one 'mod' MASTER_SITE, which is what would happen if we used a
MASTER_SITE_APACHE or added all of the mirrors in a row.
Approved By: apache maintainers, asami
Submitted By: Brian Feldman <green@unixhelp.org>, billf
This is the first port version for the new mod_ssl version 2.1.
As a summary, here are its main SSL/TLS-related features:
o Open-Source software (BSD-style license)
o Useable for both commercial and non-commercial use
o Available for both Unix and Win32 platforms
o 128-bit strong cryptography world-wide
o Support for SSLv2, SSLv3 and TLSv1 protocols
o Clean reviewable ANSI C source code
o Clean Apache module architecture
o Integrates seamlessly into Apache through an Extended API (EAPI)
o Full Dynamic Shared Object (DSO) support
o Support for the SSLeay+RSAref US-situation
o Advanced pass-phrase handling for private keys
o X.509 certificate based authentication for both client and server
o Additional boolean-expression based access control facility
o Backward compatibility to other Apache SSL solutions
o Inter-process SSL session cache
o Powerful dedicated SSL engine logging facility
o Simple and robust application to Apache source trees
o Fully integrated into the Apache 1.3 configuration mechanism
o Additional integration into the Apache Autoconf-style Interface (APACI)
o Assistance in X.509 v3 certificate generation
- use mod_ssl 2.0.10 which automatically disables
DSO for mod_log_config and mod_proxy which caused
problems for the port
- use mod_auth_dbm instead of mod_auth_db because
first DBM is internally mapped to our DB (so
functionality is the same) and this way we
get rid of the nasty conflicts with DB 2.x port.
- fixed the package list, i.e. the port
now packages and deletes correctly
- automatically create dummy certificate, so
the package can be tested immediately after
installing.
- use "apachectl startssl" instead of "apachectl start"
from within apache.sh rc script now.
- removed the outcommented patch pieces for Makefile.tmpl
because they are confusing both inside patches/patch-ab
and under install time.
- use a "post-patch" target to remove all .orig files
mod_ssl's configure script created to avoid their
installation (which confuses the package list).
