on FreeBSD)
- Move mpm-itk patch to EXTRA_PATCHES to avoid conflicts with
alternative mpm patches [1]
- update PLIST_SUBS when SLAVE_PORT_MPM is defined
Requested by: Jille Timmermans [1]
- Completely shut up rc.d script when no profiles are enabled
(add add support to disable profiles) [2]
- Fix CVE-2008-2939 for mod_proxy_ftp
(XSS attacks when using wildcards in the path of the FTP URL)
- Add "apache22_fib" to start apache22 prefixed by
"setfib -F ${apache22_fib}", so apache can use an alternate
network view (not carefully tested yet)
- Revert previous patch to "fix" missing rc.d scripts. It
actually breaks profiles.
- Bump PORTREVISION
PR: ports/126670 [1],
ports/116627 [2]
Submitted by: Joseph S. Atkinson [1],
Eygene Ryabinkin [2]
Security: CVE-2008-2939
Special thanks to: pgollucci@
- Add WITH_SVN knob. It enables BDB for apache22 port and
force dependency on dev/apr-svn when WITH_APR_FROM_PORTS is
defined. (should help fixing [2]).
Introduce APR_PORT.
- Add support for db-4.7 [3]
- Add mod_ldap OPTIONS fixup [4]
- Sometimes, rc scripts aren't included in package
Try to fix this. [5]
PR: ports/126053 [2], ports/125520 [3]
ports/124651 [4], ports/126670 [5] (partially)
Reported by: QA Tindy [1],
Crazig Leres [2],
Larry Rosenman [4]
Kirk Strauser [3],
Joseph S. Atkinson [5]
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
- Remove CONFIGURE_TARGET hack in various bsd.*.mk
- USE_GNOME=gnometarget is now an no-op
Changes to individual ports, other than removing the CONFIGURE_TARGET hack:
= pkg-plist changed (due to the ugly CONFIGURE_TARGET prefix in * executables)
- comms/gnuradio
- science/abinit
- science/elmer-fem
- science/elmer-matc
- science/elmer-meshgen2d
- science/elmerfront
- science/elmerpost
= use x86_64 as ARCH
- devel/g-wrap
= other changes
- print/magicfilter
GNU_CONFIGURE -> HAS_CONFIGURE since it's not generated by autoconf
Total # of ports modified: 1,027
Total # of ports affected: ~7,000 (set GNU_CONFIGURE to yes)
PR: 126524 (obsoletes 52917)
Submitted by: rafan
Tested on: two pointyhat 7-amd64 exp runs (by pav)
Approved by: portmgr (pav)
- Preserve index.html
- We no longer install images in default DocumentRoot (there're still in icons/)
- Various plist cleanup
- bump PORTREVISION since we are now safe with index.html
Reminded by: bland@
- add PCRE_FROM_PORTS to OPTIONS
- use @dirrmtry for include/apache22
- workaround plist issues when upgrading, but it's not as safe as I
would expect, it requires more work.
Spotted by: bland@ [1]
From UPDATING:
By popular request, OPTIONS support has been added. When actived
(default), these knobs are ignored:
* WITH_<CATEGORY>_MODULES
* WITHOUT_<CATEGORY>_MODULES
* WITH_CUSTOM_<CATEGORY>
* WITH_MODULES
* WITHOUT_MODULES
* WITH_STATIC_MODULES
However, you can disable OPTIONS by defining WITHOUT_APACHE_OPTIONS.
- move envvars support to the beginning of apache22_checkconfig() to be
sure we're using envvars during configtest [1]
PR: ports/116329 [1]
Submitted by: Ruud Althuizen <ruud@il.fontys.nl> [1]
- Add support for PCRE from ports (WITH_PCRE_FROM_PORTS) [2]
- Install split-logfile [3]
Submitted by: Christopher Shumway <cshumway at titan-project dot org> [1]
Requested by: Gergely CZUCZY <phoemix at harmless dot hu>, [2]
many [3]
All people using mod_rewrite are strongly encouraged to update.
An off-by-one flaw exists in the Rewrite module, mod_rewrite.
Depending on the manner in which Apache httpd was compiled, this
software defect may result in a vulnerability which, in combination
with certain types of Rewrite rules in the web server configuration
files, could be triggered remotely. For vulnerable builds, the nature
of the vulnerability can be denial of service (crashing of web server
processes) or potentially allow arbitrary code execution.
This issue has been rated as having important security impact
by the Apache HTTP Server Security Team
Updates to latest versions will follow soon.
Notified by: so@ (simon)
Obtained from: Apache Security Team
Security: CVE-2006-3747
We have not checked for this KEYWORD for a long time now, so this
is a complete noop, and thus no PORTREVISION bump. Removing it at
this point is mostly for pedantic reasons, and partly to avoid
perpetuating this anachronism by copy and paste to future scripts.
