Add an "inet6" option for enabling IPv6 support.
Add a "ban" option for enabling mod_ban.
Make the "wrap" option compile all binaries successfully.
Fix generating language catalog with older versions of msgfmt.
Changes since 1.3.1rc3
----------------------
- Bug 2944 - mod_sql_mysql fails to compile due to missing quotation.
- Bug 2946 - Anonymous logins fail if the mod_facl module is enabled.
- Bug 2947 - SIGBUS on Mac OS X when dynamically loading shared libs.
- Bug 2950 - Hostname with multiple IP addresses might cause "ai_family not
supported" error if IPv6 support enabled.
- Bug 2955 - Undeclared identifier MAP_FAILED for mod_delay on AIX.
- Bug 2958 - mod_wrap2 does not handle multiple rules in access files.
- Bug 2963 - Use of -A option for LIST/NLST commands not cleared for
subsequent commands.
- Bug 2964 - Building RPM fails because of *snprintf trying to be redefined.
This is actually caused by a particular combination of compiler flags
(-O2 and -Wp,-D_FORTIFY_SOURCE=2), which are used by the `rpmbuild'
command in some Linux releases.
- Bug 2974 - Install error if multiple modules, using their own build script,
are built as shared modules.
- Bug 2981 - Command-line long options --ipv4 and --ipv6 do not work.
- Bug 2795 - Improvements to RPM .spec file to build more of the modules, plus
better optional packaging organization.
Hello, ProFTPD community. The ProFTPD Project team is pleased to announce
that the third release candidate for ProFTPD 1.3.1 is now available
for public consumption.
The 1.3.1rc3 release includes a number of minor bugfixes, including
segfaults when handling the NLST command, dealing assigning IPv6 addresses
for the EPSV command, and better handling of Display files in chrooted
sessions.
Please read the included NEWS and ChangeLog files for the full details.
+ Fixed mod_sql's handling of WHERE clauses
+ Fixed segfaults ocurring after SIGHUP when shared modules are used
+ Fixed copying of symlinks in skeleton directory for CreateHome
The 1.3.1rc1 release includes major new features and numerous bugfixes,
including:
+ Support for UTF8 and translated response messages (NLS support)
+ New configuration directives:
DisplayChdir
DisplayFileTransfer
UseIPv6
UseUTF8
+ Deprecated configuration directives:
DisplayFirstChdir
The DisplayFirstChdir directive is deprecated; sites should use
the new DisplayChdir directive (which allows for files to
be displayed on every directory change, rather than just the
first time for a directory change).
HiddenStor
The HiddenStor directive is deprecated; simply use HiddenStores
instead.
SQLHomedirOnDemand
The SQLHomedirOnDemand directive will be removed in future
releases; use the CreateHome directive instead.
+ New modules:
mod_ban, a module handling dynamic client "black lists"
See doc/contrib/mod_ban.html
+ Enhanced modules:
The mod_tls module can now make use of cryptographic accelerator
cards with the new TLSCryptoDevice directive. It can also use
a program for obtaining certificate passphrases via the new
TLSPassPhraseProvider directive.
+ Documentation
The 1.3.0rc5 release includes a number of minor bugfixes, including a
workaround for getting proper timestamps in chrooted process logs
if glibc-2.3 is present, and a fix for daemon processes hanging when
shutting down on Mac OS X.
The 1.3.0rc4 release includes a number of minor bugfixes, including fixed
run-time detection of Unix domain sockets, portability tweaks for
Mac OSX 10.4, and logging fixes for NetBSD and Solaris.
And always is defined as share/examples/rc.d
which was the default before.
This rc.d scripts are not automatically added to PLISTs now also.
So add to each corresponding PLIST as required.
This was discussed on tech-pkg in late January and late April.
Todo: remove the RCD_SCRIPTS_EXAMPLEDIR uses in MESSAGES and elsewhere
and remove the RCD_SCRIPTS_EXAMPLEDIR itself.
It includes the correct buildlink3.mk file from either Linux-PAM
(security/PAM) or OpenPAM (security/openpam) and eventually will
support solaris-pam. pam.buildlink3.mk will:
* set PAMBASE to the base directory of the PAM files;
* set PAM_TYPE to the PAM implementation used.
There are two variables that can be used to tweak the selection of
the PAM implementation:
PAM_DEFAULT is a user-settable variable whose value is the default
PAM implementation to use.
PAM_ACCEPTED is a package-settable list of PAM implementations
that may be used by the package.
Modify most packages that include PAM/buildlink3.mk to include
pam.buildlink3.mk instead.
