This is frox, a transparent ftp proxy by James Hollingshead.
Current features include:
o rfc959 compliant transparent proxying of ftp connections.
o active --> passive mode conversion for data connections.
o Optional caching support either locally or through an external
HTTP cache.
o Optional virus scanning
o Optional non-transparent proxy support by logging in with
user@host:port.
o Options to bind to a specific interface, chroot, and drop
priveleges for security.
WWW: http://www.hollo.org/frox/
===> The following configuration options are available for frox-0.7.18_4:
CCP=on: Ftp-proxy style command control programs
DOCS=on: Build and/or install documentation
EXAMPLES=on: Build and/or install examples
HTTP_CACHE=on: Enable use of external cache
LOCAL_CACHE=off: Enable use of local cache
ROOT_RUN=off: Allow frox running as root (not recomended)
VIRUS_SCAN=off: Run external virus scaner on each download
====> Options available for the radio PFILTER: you can only select none or one of them
IPFILTER=off: Use ipfilter instead of ipfw
PF=off: Build with pf(4) support
===> Use 'make config' to modify these settings
Remove expired ports:
devel/buildtool-doc
2021-04-01 devel/buildtool: Unmaintained and dead upstream, does not build with
-fno-common (llvm 11)
2021-04-01 misc/floatator: Unmaintained and dead upstream, does not build with
-fno-common (llvm 11)
2021-04-01 finance/wmstock: Unmaintained and dead upstream, does not build with
-fno-common (llvm 11)
2021-04-01 ftp/frox: Unmaintained and dead upstream, does not build with
-fno-common (llvm 11)
Extend expiration of ports broken with -fno-common
Extend the expiration of unmaintained leaf ports that are broken with
-fno-common and previously had a short expiration date. The new date is set
to 2021-04-01, meaning the ports will be in the 2021Q2 branch, giving people
until 2021-06-30 (10 months from now) to fix issues.
Improve the wording of the deprecation message, mentioning both llvm 11 and
-fno-common.
Bump portrevision to force reinstall. This way the warning message about
deprecation will be displayed to users installing or reinstalling the
software.
MFH: 2020Q3 (maybe)
- Fix build with PF OPTION selected [1]
- Move IPFILTER / PF OPTIONS into OPTIONS_RADIO because port does
not build if both are selected [2]
PR: 197412
Submitted by: fidaj@ukr.net [1]
Reviewed by: riggs [2]
Approved by: maintainer timeout
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.
- Add LDFLAGS to CONFIGURE_ENV and MAKE_ENV (as it was done with LDFLAGS)
- Fix all ports that add {CPP,LD}FLAGS to *_ENV to modify flags instead
PR: 157936
Submitted by: myself
Exp-runs by: pav
Approved by: pav
Fix a few "bad example" problems in the rc.d scripts that have been
propogated by copy and paste.
1. Primarily the "empty variable" default assignment, which is mostly
${name}_flags="", but fix a few others as well.
2. Where they are not already documented, add the existence of the _flags
(or other deleted empties) option to the comments, and in some cases add
comments from scratch.
3. Replace things that look like:
prefix=%%PREFIX%%
command=${prefix}/sbin/foo
to just use %%PREFIX%%. In many cases the $prefix variable is only used
once, and in some cases it is not used at all.
4. In a few cases remove ${name}_flags from command_args
5. Remove a long-stale comment about putting the port's rc.d script in
/etc/rc.d (which is no longer necessary).
No PORTREVISION bumps because all of these changes are noops.
Update CONFIGURE_ARGS for how we pass CONFIGURE_TARGET to configure script.
Specifically, newer autoconf (> 2.13) has different semantic of the
configure target. In short, one should use --build=CONFIGURE_TARGET
instead of CONFIGURE_TARGET directly. Otherwise, you will get a warning
and the old semantic may be removed in later autoconf releases.
To workaround this issue, many ports hack the CONFIGURE_TARGET variable
so that it contains the ``--build='' prefix.
To solve this issue, under the fact that some ports still have
configure script generated by the old autoconf, we use runtime detection
in the do-configure target so that the proper argument can be used.
Changes to Mk/*:
- Add runtime detection magic in bsd.port.mk
(Only the first 15 lines of the commit message are shown above )
- Remove the DESTDIR modifications from individual ports as we have a new,
fully chrooted DESTDIR, which does not need such any more.
Sponsored by: Google Summer of Code 2007
Approved by: portmgr (pav)
- Utilize new features: USE_RC_SUBR, SUB_FILES. It simplifies Makefile.
- Fix pkg-message
- Remove redundant code from a startup script
- Install a sample config in EXAMPLESDIR instead of PREFIX/etc
- Refine pkg-descr a little
- Update to 0.7.12
- use rcNG script
- make configure script happy with CONFIGURE_TARGET
- use PORTDOCS to autoaddition docs in PLIST
PR: 61561
Submitted by: maintainer
- Update to 0.7.11
o Fixed running from inetd which was broken by the
0.7.8-->0.7.9 changes
PR: 57370
Submitted by: Sergey Matveychuk <sem@ciam.ru> (maintainer)
* Update to 0.7.7
* Move from minium build to maximum (change WITH_ to WITHOUT_) by default
* Allow to build with local-cache and virus-scan features
* make startup script more smarter
PR: 50674
Submitted by: Sergey Matveychuk <sem@ciam.ru>
