search for: apache13

...: low >Category: ports >Class: change-request >Release: FreeBSD 4.8-STABLE i386 >Environment: System: FreeBSD users.munk.nu 4.8-STABLE FreeBSD 4.8-STABLE #1: Fri Apr 18 14:38:46 BST 2003 root@users.munk.nu:/usr/obj/usr/src/sys/MUNKBOXEN i386 >Description: The apache13 port control script /usr/local/sbin/apachectl is used to control the apache httpd daemon. However the apachectl script does not start with a clean environment, inheriting the environment of the user that invokes the script. As a consequence the environment variables set by the shell of the user t...

...ith has optional components c1 and c2. This *should not* result in the following package names: port-v port-suf1-v+v1 port-suf2-v+v2 port-suf1-suf2-v+v1+v2 because I need 2^(number of components) entries to catch all possible combinations, for example the recent vulnerability in www/apache13-modssl would need 32 entries in the vulnerability database, which seems a little high. A net effect is that many combinations are not recognized, and users remain unprotected even though they assume the opposite. If you need to record the included components, please do this in the pkg-message, w...

It seems a php-extensions bug. If you comment the mhash.so in /usr/local/etc/php/extensions.ini as: ;entension=mhash.so all works fine and you don't get anymore httpd crash (signal 11) if you use 'apachectl graceful'. Maybe will be a good idea to open PR for this? I hope it helps someone.... (I'm very surprised that this isn't a documented bug in 7.0 yet) -- Thanks, Jordi

Hi, I'm pondering building my own SSL accelerator out of a multi-CPU FreeBSD system and a crypto accelerator. What's the recommended hardware crypto accelerator card these days? Thanks, ==ml -- Michael Lucas mwlucas@FreeBSD.org, mwlucas@BlackHelicopters.org Today's chance of throwing it all away to start a goat farm: 49.1% http://www.BlackHelicopters.org/~mwlucas/

Dear FreeBSD users and system administrators, While the FreeBSD Security Team has traditionally been very good at investigating and responding to security issues in FreeBSD, this only solves half of the security problem: Unless users and administrators of FreeBSD systems apply the security patches provided, the advisories issued accomplish little beyond alerting potential attackers to the