ProFTPD is a highly configurable ftp daemon for Unix
and Unix-like operating systems. ProFTPD is designed
to be somewhat of a "drop-in" replacement for wu-ftpd
with a configuration format like Apache.
Full online documentation is available at
http://www.proftpd.org/, including a server
configuration directive reference manual.
===> The following configuration options are available for proftpd-1.3.8c_3:
DOCS=on: Build and/or install documentation
HTMLDOCS=off: Include HTML documentation
IPV6=on: IPv6 protocol support
LIBSODIUM=on: Stronger key algorithm support using libsodium
MEMCACHE=off: Memcache support using libmemcached
NLS=on: Native Language Support
REDIS=off: Redis support using hiredis
====> PCRE library to use: you can only select none or one of them
PCRE1=off: Use Perl Compatible Regular Expressions
PCRE2=on: Use Perl Compatible Regular Expressions version 2
===> Use 'make config' to modify these settings
ftp/proftpd: update to 1.3.8b and add libsodium support
Provides mitigation for "Terrapin" SSH attack.
Support stronger key algorithms using libsodium by default.
PR: 265590, 276168
Security: CVE-2023-48795
devel/gettext: Update to 0.22
Convert post-patch commands to real patches. This way there are errors
when the underlying code changes.
*/*: Fix gettext issues. The new gettext tools are more strict.
PR: 272210
Exp-run by: antoine
Fix WWW in parent/child ports
Many of the WWW are overwritten later which means the wrong value
is used. This did not happen before where the children were either
a) just using the pkg-descr from the parents
b) or had their own separate pkg-descr with custom WWW
Use WWW?= in parents when the child's WWW is different.
Children that use the same WWW as the parent can just inherit it,
i.e., the child WWW can be removed.
Approved by: portmgr (implicit)
Remove WWW entries moved into port Makefiles
Commit b7f05445c00f has added WWW entries to port Makefiles based on
WWW: lines in pkg-descr files.
This commit removes the WWW: lines of moved-over URLs from these
pkg-descr files.
Approved by: portmgr (tcberner)
Add WWW entries to port Makefiles
It has been common practice to have one or more URLs at the end of the
ports' pkg-descr files, one per line and prefixed with "WWW:". These
URLs should point at a project website or other relevant resources.
Access to these URLs required processing of the pkg-descr files, and
they have often become stale over time. If more than one such URL was
present in a pkg-descr file, only the first one was tarnsfered into
the port INDEX, but for many ports only the last line did contain the
port specific URL to further information.
There have been several proposals to make a project URL available as
a macro in the ports' Makefiles, over time.
(Only the first 15 lines of the commit message are shown above )
ftp: remove 'Created by' lines
A big Thank You to the original contributors of these ports:
* Aaron Dalton <aaron@FreeBSD.org>
* Alexander Kriventsov
* Anders Nordby <anders@fix.no>
* Andreas Fehlner <fehlner@gmx.de>
* Andrew Pantyukhin <infofarmer@FreeBSD.org>
* Andrey Zakhvatov
* Antonio Carlos Venancio Junior (<antonio@inf.ufsc.br>)
* Chris Piazza <cpiazza@FreeBSD.org>
* Damjan Marion <dmarion@open.hr>
* Emanuel Haupt <ehaupt@critical.ch>
* Eric Freeman <freebsdports@chillibear.com>
(Only the first 15 lines of the commit message are shown above )
ftp/proftpd: Avoid passing USES=cpe to all slave ports
There are some slave ports which are developed independently and have
no CPE entries yet.
Approved by: portmgr (blanket)
The latest version of ftp/proftpd doesn't build with libressl either.
Increase the IGNORE from openssl-devel to include all versions of libressl.
Approved by: SSL blanket
Remove OSVERSION checks that do not make sense any more.
For example (${OSVERSION} >= 900000 && ${OSVERSION} < 900021) is always true,
as is (${OSVERSION} > 900002 || ${OSVERSION} < 900000 && ${OSVERSION} > 800107).
Regarding patches, when an EXTRA_PATCHES is no longer needed, I remove it, when
it is always needed, I renamed it, in one case, I merged two patches.
Differential Revision: https://reviews.freebsd.org/D2209
databases/libmemcached: Update to 1.0.18 and much more
- Update to 1.0.18 and pkg-plist accordingly
- Add LICENSE (BSD3CLAUSE) and LICENSE_FILE
- Add TEST_DEPENDS and regression-test target
- Perl is not required, remove USE_PERL and from USES
- Split LDFLAGS from CONFIGURE_ENV, they're already set there
- Add libmemcachedprotocol to CONFIGURE_ARGS (Now default: off)
- Add OPTIONS for hash functions, debug and dtrace
- pkg-descr: Update WWW: URL
- Add patches for:
* alloca.h include not found on FreeBSD
* cinttypes include location
* clang compatibility
- Strip shared libraries manually since upstream install-strip target is
fail
Changes:
https://launchpad.net/libmemcached/+announcements
[1] https://bugs.launchpad.net/libmemcached/+bug/1245562
[2] https://bugs.launchpad.net/libmemcached/+bug/1400560
Approved by: Mikhail Tsatsenko <m.tsatsenko@gmail.com> (maintainer, via email)
Support LIBS like LDFLAGS.
- Add LIBS="${LIBS}" to MAKE_ENV and CONFIGURE_ENV.
- Add an option helper for LIBS.
- Adjust all ports that already use LIBS. Also remove references to
PTHREAD_CFLAGS and PTHREAD_LIBS while here.
- Some ports did not support having a LIBS environment variable and
required additional patches.
Somewhat simplified a linker command line looks like:
${CC} ${src_LDFLAGS} ${LDFLAGS} ${src_LIBS} ${LIBS}
where src_LDFLAGS and src_LIBS are controlled by upstream and LDFLAGS and
LIBS can be controlled by us. If possible -L and -l flags need to be
(Only the first 15 lines of the commit message are shown above )
Fix unixODBC vs libiodbc conflicts
Always rely on unixODBC each time a port is looking for libodbc.so
Remove odbc compat from libiodbc
This allows to install both kde and gnome at the same time
While here:
- Convert libiodbc to USES=libtool
- Convert a bunch of libiodbc dependencies to USES=libtool
- Chase libiodbc.so shlib change
- Stagify some ports
- Convert some ports to USES=pgsql
Discussed with: rakuco (kde)
With hat: portmgr
- Add DOCS option.
- When the NLS option is enabled the configure script looks for iconv_open()
and libiconv_open() functions in libiconv before trying libc. This means
that on FreeBSD 10 proftpd depends on converters/libiconv when it is
installed but it should use iconv from libc instead.
To fix this add ac_cv_lib_iconv_iconv_open=no and
ac_cv_lib_iconv_libiconv_open=no to CONFIGURE_ARGS to bypass those
configure tests when ICONV_LIB is empty.
- Remove references to -lintl. The configure script detects it correctly.
PR: ports/187860
Submitted by: tijl@FreeBSD.org
Fix installation of ports that rely on cp -n for installing files. r245960
changed cp to exit with a non-zero exit code if the file exists and is not
overwritten thus causing ports to fail installing when e.g. trying to cp
.default -> .conf files that already exist.
We just ignore the error and continue, as we used to.
Reported by: jaset
Approved by: portmgr (bapt)
Unbreak ProFTPD on sparc [1].
Significantly simplify proftpd port options.
Slave ports will follow in separate commits.
PR: 169644 [1]
Submitted by: Dmitry Afanasiev [1]
Update to 1.3.4a
Switch to using dynamic modules
Autosellect required modules instead of exiting with IGNORE
Add slave port infrastructure for building individual modules
In the rc.d scripts, change assignments to rcvar to use the
literal name_enable wherever possible, and ${name}_enable
when it's not, to prepare for the demise of set_rcvar().
In cases where I had to hand-edit unusual instances also
modify formatting slightly to be more uniform (and in
some cases, correct). This includes adding some $FreeBSD$
tags, and most importantly moving rcvar= to right after
name= so it's clear that one is derived from the other.
As of FreeBSD-SA-11:07.chroot, the port now works on both patched and
unpatched systems. On unpatched systems chroot automatically fails.
FreeBSD-SA-11:07.chroot
Add MOD_DYNMASQ
Apply a patch after FreeBSD-SA-11:07.chroot which addresses an arbitrary
code execution vulnerability.
Please note that in order to build this the system needs to be patched
with FreeBSD-SA-11:07.chroot and the resulting binary also needs to the
change because it depends on a new libc API.
Feature safe: yes
Approved by: portmgr, maintainer (mm)
