Re: Conflit with apache13 when I use apache13-modssl
On Monday 25 February 2008 11:32:50 Nicolas Letellier wrote: > I use apache13-modssl. However, when I want to install a port like > "php5", I have this error : > > > ===> Installing for apache-1.3.41 > > ===> apache-1.3.41 conflicts with installed package(s): > apache+mod_ssl-1.3.41+2.8.31 > > They install files into the same place. > Please remove them first with pkg_delete(1). > *** Error code 1 > > > php5 port requires port apache13. How could I repair this problem? php5 > port is already installed but I have this warning. How precise I want to > use apache13-modssl and not apache13 ? echo APACHE_PORT=www/apache13-modssl >>/etc/make.conf -- Mel ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Conflit with apache13 when I use apache13-modssl
Mel a écrit : On Monday 25 February 2008 11:32:50 Nicolas Letellier wrote: I use apache13-modssl. However, when I want to install a port like "php5", I have this error : ===> Installing for apache-1.3.41 ===> apache-1.3.41 conflicts with installed package(s): apache+mod_ssl-1.3.41+2.8.31 They install files into the same place. Please remove them first with pkg_delete(1). *** Error code 1 php5 port requires port apache13. How could I repair this problem? php5 port is already installed but I have this warning. How precise I want to use apache13-modssl and not apache13 ? echo APACHE_PORT=www/apache13-modssl >>/etc/make.conf It's perfect ! Thank you ! -Nicolas ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Conflit with apache13 when I use apache13-modssl
Hello, I use apache13-modssl. However, when I want to install a port like "php5", I have this error : ===> Installing for apache-1.3.41 ===> apache-1.3.41 conflicts with installed package(s): apache+mod_ssl-1.3.41+2.8.31 They install files into the same place. Please remove them first with pkg_delete(1). *** Error code 1 php5 port requires port apache13. How could I repair this problem? php5 port is already installed but I have this warning. How precise I want to use apache13-modssl and not apache13 ? Thanks. Nicolas ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
mod_rewrite does not work with apache13-modssl and enabled modaccel
Hello I compiled apache13-modssl with WITH_APACHE_MODACCEL=YES. With enabled MODACCEL my mod_rewrite does not work as expected. I get this error message: [error] [client xxx.xxx.xxx.xxx] attempt to make remote request from mod_rewrite without proxy enabled: proxy:http://mysite/foobar/traffic System: Freebsd 4.11 Apache13-modssl port from 1. August 2006 ssl_config.include: ProxyRequests Off RewriteRule ^/login/foobar/monitor/(.*)$ http://mysite/foobar/traffic/$1 [P,L] ProxyPassReverse /login/foobar/monitor/ http://mysite/foobar/traffic/ I rebuilded apache13-modssl without MODACCEL and then everything works perfectly. So i doubt that's a config error. Is this a known behavior? regards, Thomas ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: FreeBSD 6.0-RELEASE apache13-modssl signal 11s
On Mon, 23 Jan 2006 13:38:56 +0200 Omer Faruk Sen <[EMAIL PROTECTED]> wrote: > I have installed apache13-modssl 1.3.34+2.8.25_2 to my FreeBSD > 6.0-RELEASE. But when I try to start server using -DSSL I get signal > 11s. But when I disable mod_ssl httpd works fine. Does anybody lived > something like that with FreeBSD 6.0-RELEASE I've got something similar on 5.4, not tested on 6.0. The fix in my case was building the port against openssl-stable (i.e. 0.9.7i) Try building the port using WITH_OPENSSL_STABLE=YES Cheers -- Adi Pircalabu (PGP Key ID 0x04329F5E) -- This message was scanned for spam and viruses by BitDefender. For more information please visit http://www.bitdefender.com/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: FreeBSD 6.0-RELEASE apache13-modssl signal 11s
Omer Faruk Sen wrote: I have installed apache13-modssl 1.3.34+2.8.25_2 to my FreeBSD 6.0-RELEASE. But when I try to start server using -DSSL I get signal 11s. But when I disable mod_ssl httpd works fine. Does anybody lived something like that with FreeBSD 6.0-RELEASE Checked logs? It could be something simple, like key problems or mismatching, etc., or it could be something more sinister. It seems like I've had trouble with this before, but I'm not grepping it in my "diary". KDK -- Some primal termite knocked on wood. And tasted it, and found it good. And that is why your Cousin May Fell through the parlor floor today. -- Ogden Nash P.S. Ooh, a favorite. Maybe I should keep this one ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
FreeBSD 6.0-RELEASE apache13-modssl signal 11s
I have installed apache13-modssl 1.3.34+2.8.25_2 to my FreeBSD 6.0-RELEASE. But when I try to start server using -DSSL I get signal 11s. But when I disable mod_ssl httpd works fine. Does anybody lived something like that with FreeBSD 6.0-RELEASE --- Omer Faruk Sen http://www.EnderUNIX.ORG Software Development Team @ Turkey http://www.Faruk.NET For Public key: http://www.enderunix.org/ofsen/ofsen.asc *** AcikAcademy published a Turkish TCP/IP Book Acik Akademi'nin yeni kitabini duydunuz mu? http://www.acikakademi.com/catalog/tcpip/ Life is trouble.. Only Death is not! -Alexis Zorba ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: apache13-modssl-1.3.33+2.8.22_1 port broken??
On Wed, 27 Jul 2005, Viren Patel wrote: I am trying to install apache+mod_ssl-1.3.33+2.8.22_1 and get the following: #make ===> apache+mod_ssl-1.3.33+2.8.22_1 has known vulnerabilities: => apache -- http request smuggling. Reference: <http://www.FreeBSD.org/ports/portaudit/651996e0-fe07-11d9-8329-000e0c2e438a.html> => Please update your ports tree and try again. *** Error code 1 Stop in /usr/ports/www/apache13-modssl. I have updated the ports tree and the files directory contains the patch for this vulnerability (patch-secfix-CAN-2005-2088). I need to install this port urgently. What am I doing wrong?? If the vulnerability has not been fixed, how can I force install? TIA. # make -DDISABLE_VULNERABILITIES will override portaudit. -Warren Block * Rapid City, South Dakota USA ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
apache13-modssl-1.3.33+2.8.22_1 port broken??
I am trying to install apache+mod_ssl-1.3.33+2.8.22_1 and get the following: #make ===> apache+mod_ssl-1.3.33+2.8.22_1 has known vulnerabilities: => apache -- http request smuggling. Reference: <http://www.FreeBSD.org/ports/portaudit/651996e0-fe07-11d9-8329-000e0c2e438a.html> => Please update your ports tree and try again. *** Error code 1 Stop in /usr/ports/www/apache13-modssl. I have updated the ports tree and the files directory contains the patch for this vulnerability (patch-secfix-CAN-2005-2088). I need to install this port urgently. What am I doing wrong?? If the vulnerability has not been fixed, how can I force install? TIA. -- Viren ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
RE: Portupgrade breaks Apache13-modssl
That seemed to work. I removed the openssl extension from the php extensions.ini file and all seems to work fine now. Thanks, Eric -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Tim Kellers Sent: Saturday, May 21, 2005 11:01 To: postmaster Cc: 'Kris Kennaway'; Eric Sheesley Subject: Re: Portupgrade breaks Apache13-modssl On Saturday 21 May 2005 10:39 am, Eric Sheesley wrote: > When I did the portupgrade I did 'portupgrade -arR'. Apache fails to > start at boot. If I run it manually with 'httpd' it works fine but if > I do 'httpd -DSSL' it fails. I've even rebuilt the apache13-modssl > port with no luck. Not sure what other details I can give besides the > messages log reports a core dump. > > -Original Message- > From: Kris Kennaway [mailto:[EMAIL PROTECTED] > Sent: Saturday, May 21, 2005 02:38 > To: Eric Sheesley > Cc: freebsd-questions@freebsd.org > Subject: Re: Portupgrade breaks Apache13-modssl > > On Sat, May 21, 2005 at 12:47:41AM -0400, Eric Sheesley wrote: > > I am running Freebsd 5.3 and just did a portupgrade(upgraded php, > > amavis, clamav, and cyrus-sasl. When I rebooted apache refused to > > start. I can get apache started with no ssl but not with it. I > > have apache13-modssl installed. It wasn't modified during the > > upgrade though. So it would seem taht teh ssl mod is crashing. Any ideas? > > Anyone else experience this? > > You need to > > * make sure you also update the ports that depend on those you > updated, e.g. by using portupgrade -a, -r, etc. > > * provide more details in your support requests. "It is crashing", > etc is not helpful. Show exact commands you are running and exact > output, and exact errors, if any. > > Thanks, > Kris > > ___ > freebsd-questions@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to > "[EMAIL PROTECTED]" I have had upgrades to php mysteriously (that is with no apparent logfile error) break apache. Try commenting out the following lines from your httpd.conf file: LoadModule php4_module AddModule mod_php4.c and restart apache. If that works, look in /usr/local/etc/php/extensions.ini and see if there are any obvious php conflicting modules and comment them out --extension=recode.so has sometimes gotten placed back in that file even though it's a known conflict after an upgrade. Then restart apache. If there is no "obvious" conflict like the recode conflict, you may have to begin commenting out the extensions in that file one by one, restarting apache until it starts again. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]" ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Portupgrade breaks Apache13-modssl
On Saturday 21 May 2005 10:39 am, Eric Sheesley wrote: > When I did the portupgrade I did 'portupgrade -arR'. Apache fails to start > at boot. If I run it manually with 'httpd' it works fine but if I do > 'httpd -DSSL' it fails. I've even rebuilt the apache13-modssl port with no > luck. Not sure what other details I can give besides the messages log > reports a core dump. > > -Original Message- > From: Kris Kennaway [mailto:[EMAIL PROTECTED] > Sent: Saturday, May 21, 2005 02:38 > To: Eric Sheesley > Cc: freebsd-questions@freebsd.org > Subject: Re: Portupgrade breaks Apache13-modssl > > On Sat, May 21, 2005 at 12:47:41AM -0400, Eric Sheesley wrote: > > I am running Freebsd 5.3 and just did a portupgrade(upgraded php, > > amavis, clamav, and cyrus-sasl. When I rebooted apache refused to > > start. I can get apache started with no ssl but not with it. I have > > apache13-modssl installed. It wasn't modified during the upgrade > > though. So it would seem taht teh ssl mod is crashing. Any ideas? > > Anyone else experience this? > > You need to > > * make sure you also update the ports that depend on those you updated, > e.g. by using portupgrade -a, -r, etc. > > * provide more details in your support requests. "It is crashing", etc is > not helpful. Show exact commands you are running and exact output, and > exact errors, if any. > > Thanks, > Kris > > ___ > freebsd-questions@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to > "[EMAIL PROTECTED]" I have had upgrades to php mysteriously (that is with no apparent logfile error) break apache. Try commenting out the following lines from your httpd.conf file: LoadModule php4_module AddModule mod_php4.c and restart apache. If that works, look in /usr/local/etc/php/extensions.ini and see if there are any obvious php conflicting modules and comment them out --extension=recode.so has sometimes gotten placed back in that file even though it's a known conflict after an upgrade. Then restart apache. If there is no "obvious" conflict like the recode conflict, you may have to begin commenting out the extensions in that file one by one, restarting apache until it starts again. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
RE: Portupgrade breaks Apache13-modssl
Here is the error from the log: May 21 10:49:30 rogue kernel: pid 69446 (httpd), uid 0: exited on signal 11 (core dumped) -Original Message- From: Kris Kennaway [mailto:[EMAIL PROTECTED] Sent: Saturday, May 21, 2005 02:38 To: Eric Sheesley Cc: freebsd-questions@freebsd.org Subject: Re: Portupgrade breaks Apache13-modssl On Sat, May 21, 2005 at 12:47:41AM -0400, Eric Sheesley wrote: > I am running Freebsd 5.3 and just did a portupgrade(upgraded php, > amavis, clamav, and cyrus-sasl. When I rebooted apache refused to > start. I can get apache started with no ssl but not with it. I have > apache13-modssl installed. It wasn't modified during the upgrade > though. So it would seem taht teh ssl mod is crashing. Any ideas? Anyone else experience this? You need to * make sure you also update the ports that depend on those you updated, e.g. by using portupgrade -a, -r, etc. * provide more details in your support requests. "It is crashing", etc is not helpful. Show exact commands you are running and exact output, and exact errors, if any. Thanks, Kris ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
RE: Portupgrade breaks Apache13-modssl
When I did the portupgrade I did 'portupgrade -arR'. Apache fails to start at boot. If I run it manually with 'httpd' it works fine but if I do 'httpd -DSSL' it fails. I've even rebuilt the apache13-modssl port with no luck. Not sure what other details I can give besides the messages log reports a core dump. -Original Message- From: Kris Kennaway [mailto:[EMAIL PROTECTED] Sent: Saturday, May 21, 2005 02:38 To: Eric Sheesley Cc: freebsd-questions@freebsd.org Subject: Re: Portupgrade breaks Apache13-modssl On Sat, May 21, 2005 at 12:47:41AM -0400, Eric Sheesley wrote: > I am running Freebsd 5.3 and just did a portupgrade(upgraded php, > amavis, clamav, and cyrus-sasl. When I rebooted apache refused to > start. I can get apache started with no ssl but not with it. I have > apache13-modssl installed. It wasn't modified during the upgrade > though. So it would seem taht teh ssl mod is crashing. Any ideas? Anyone else experience this? You need to * make sure you also update the ports that depend on those you updated, e.g. by using portupgrade -a, -r, etc. * provide more details in your support requests. "It is crashing", etc is not helpful. Show exact commands you are running and exact output, and exact errors, if any. Thanks, Kris ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Portupgrade breaks Apache13-modssl
On Sat, May 21, 2005 at 12:47:41AM -0400, Eric Sheesley wrote: > I am running Freebsd 5.3 and just did a portupgrade(upgraded php, amavis, > clamav, and cyrus-sasl. When I rebooted apache refused to start. I can get > apache started with no ssl but not with it. I have apache13-modssl > installed. It wasn't modified during the upgrade though. So it would seem > taht teh ssl mod is crashing. Any ideas? Anyone else experience this? You need to * make sure you also update the ports that depend on those you updated, e.g. by using portupgrade -a, -r, etc. * provide more details in your support requests. "It is crashing", etc is not helpful. Show exact commands you are running and exact output, and exact errors, if any. Thanks, Kris pgpYV7IHPgcPq.pgp Description: PGP signature
Portupgrade breaks Apache13-modssl
I am running Freebsd 5.3 and just did a portupgrade(upgraded php, amavis, clamav, and cyrus-sasl. When I rebooted apache refused to start. I can get apache started with no ssl but not with it. I have apache13-modssl installed. It wasn't modified during the upgrade though. So it would seem taht teh ssl mod is crashing. Any ideas? Anyone else experience this? Thanks, Eric ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Installing apache13-modssl from packages: how to deal with apache13 deps?
On Tue, Jan 18, 2005 at 11:41:24AM -0500, Kyle Jensen wrote:
> However, (I'm a noob to packages, sorry for the upcoming
> question) apache13-modssl conflicts with apache13 and
> anything that depends on apache13 will complain about
> apache13-modssl.
>
> I worked around this via the '-rf' flag to pkg_add. Is there
> a better solution?
Yes: install from ports.
If you want to use apache13-modssl instead of apache13, you will need
to put:
APACHE_PORT=www/apache13-modssl
into /etc/make.conf. All apache-based ports pretty much respect that.
Then delete and re-install apache and any apache modules you've
already got installed -- by using the ports to compile from source.
Note that you /cannot/ use the pre-compiled apache module packages
from the FTP sites with apache13-modssl, even if you force the
install. The packages default to depending on the apache13 port and
are linked against the API provided by that port when they are built.
Unfortunately apache13-modssl incorporates a bunch of patches to use
what is called the 'EAPI' (extended API) -- different to plain
apache13. Which means that you have to compile any other apache
modules you want to use yourself. ie. don't use 'pkg_add', use the
ports.
Cheers,
Matthew
--
Dr Matthew J Seaman MA, D.Phil. 8 Dane Court Manor
School Rd
PGP: http://www.infracaninophile.co.uk/pgpkey Tilmanstone
Tel: +44 1304 617253 Kent, CT14 0JL UK
pgpFu7x2ClGQQ.pgp
Description: PGP signature
Installing apache13-modssl from packages: how to deal with apache13 deps?
Hi! I am installing the Horde's IMP webmail program from the packages system (the horde port was broken when I last tried). I'd like to use apache13-modssl instead of plain old apache13. However, (I'm a noob to packages, sorry for the upcoming question) apache13-modssl conflicts with apache13 and anything that depends on apache13 will complain about apache13-modssl. I worked around this via the '-rf' flag to pkg_add. Is there a better solution? Thanks so much for your advice! Kyle com D0T gmail AT kljretail ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
problems starting apache13-modssl
hello, I'm trying to get apache13-modssl running and I can't seem to accomplish it. ps -aux after reboot gives me a an entry of "readproctitle service errors." How does one do this or where do I look? I'm running 4.10. Thanks, Aaron ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: apache13-modssl
Matthew Seaman wrote: [ ... ] http://cve.mitre.org/cgi-bin/cvekey.cgi?keyword=apache+2 http://cve.mitre.org/cgi-bin/cvekey.cgi?keyword=apache+1 Errr -- did you look at the lists of entries those searches actually turn up? [ ...some analysis snipped... ] I don't think that simply counting CVE entries is going to tell you very much useful. No, I didn't look closely at the results. Without a lot more knowledge of the anonymous friend's security concerns (what their security policy is; whether local compromise vs remote matters, for instance; exploits related to specific modules they were running [simply considering the interactions of mod_ssl with OpenSSL vulnerabilities is a topic of considerable complexity]; etc), the # of CVE entries is as relevant as any other statistic. I agree with you, in other words: not very...useful. :-) However, someone who cared to make a meaningful comparision might start with the CVEs, plus checking the ChangeLogs, security-focus/bugtrak/etc mailing lists, and any other convenient data sources besides. -- -Chuck ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: apache13-modssl
On Mon, Apr 12, 2004 at 03:39:44PM -0400, Chuck Swiger wrote: > Matthew Seaman wrote: > [ ... ] > >Your friend is being unnecessarily alarmist. apache2 is not > >significantly different to apache13 in security terms. > > There have been 16 CVE entries list for Apache 2, and 8 for Apache 1.x: > > http://cve.mitre.org/cgi-bin/cvekey.cgi?keyword=apache+2 > http://cve.mitre.org/cgi-bin/cvekey.cgi?keyword=apache+1 Errr -- did you look at the lists of entries those searches actually turn up? Quite a few of the entries for the 'apache+2' search are actually apache-1.3.x specific... In fact, by my reckoning most of the CVE entries which are generic apache problems (i.e. they aren't OS or distribution specific, or they don't depend on some 3rd party code, like PHP) -- most of those apply equally to both apache-1.3.x and apache-2.0.x. If you search for the currently released apache versions, there are 2 entries mentioning apache-1.3.29 (one of which is actually for versions *before* 1.3.29), and also 2 mentioning apache-2.0.49 (again one of which only applies to versions *before* 2.0.49) I don't think that simply counting CVE entries is going to tell you very much useful. Cheers, Matthew -- Dr Matthew J Seaman MA, D.Phil. 26 The Paddocks Savill Way PGP: http://www.infracaninophile.co.uk/pgpkey Marlow Tel: +44 1628 476614 Bucks., SL7 1TH UK pgp0.pgp Description: PGP signature
Re: apache13-modssl
Matthew Seaman wrote: [ ... ] Your friend is being unnecessarily alarmist. apache2 is not significantly different to apache13 in security terms. There have been 16 CVE entries list for Apache 2, and 8 for Apache 1.x: http://cve.mitre.org/cgi-bin/cvekey.cgi?keyword=apache+2 http://cve.mitre.org/cgi-bin/cvekey.cgi?keyword=apache+1 ...so, if anything, one could argue that Apache 1 is a better bet in terms of security (not surprising, 1.x is more widely used and better tested). However, it is (I think) still a bit bigger and slower than apache13, plus support for all of the vast panoply of add-on modules etc. is yet to appear. However, apache2 works very well, and has some extra functionality (like improved IPv6 support and better threading) which may make it the preferrred choice at some sites. I don't have rigorous benchmarks to prove this opinion :-), but observation suggests that platforms which have very good thread support (ie, Solaris and MacOS X) tend to run Apache 2 better than platforms which have OK thread support (Windows, FreeBSD, Linux). The same observation tends to apply to Java as well, and if one is generating dynamic web content using a JVM, the condition of thread support on the local platform matters even more. -- -Chuck ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: apache13-modssl
On Mon, Apr 12, 2004 at 05:55:11AM -0500, Michael A. Alestock wrote: > I recently uninstalled the Apache2 port to be able to use the Apache13-modssl > port for SSL pages. > > However, I had a friend tell me that Apache13-modssl is alot less secure than > Apache2. > > Is there a modssl for Apache2 that I could use/install so it's more secure than > Apache13-modssl?? Your friend is being unnecessarily alarmist. apache2 is not significantly different to apache13 in security terms. However, it is (I think) still a bit bigger and slower than apache13, plus support for all of the vast panoply of add-on modules etc. is yet to appear. However, apache2 works very well, and has some extra functionality (like improved IPv6 support and better threading) which may make it the preferrred choice at some sites. One of the extra bits of functionality in apache2 is that mod_ssl has now been rolled into the base distribution. All you need to do is enable the SSL functionality by editing the configuration files, and get yourself a suitable server key and certificate. Cheers, Matthew -- Dr Matthew J Seaman MA, D.Phil. 26 The Paddocks Savill Way PGP: http://www.infracaninophile.co.uk/pgpkey Marlow Tel: +44 1628 476614 Bucks., SL7 1TH UK pgp0.pgp Description: PGP signature
apache13-modssl
I recently uninstalled the Apache2 port to be able to use the Apache13-modssl port for SSL pages. However, I had a friend tell me that Apache13-modssl is alot less secure than Apache2. Is there a modssl for Apache2 that I could use/install so it's more secure than Apache13-modssl?? ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: apache13 to apache13-modssl port migration
I wrote:
> >
> > The transition is easy.
> >
> > 1) deinstall all your ports(modules) depended on apache13
> > 2) install apache13-modssl.
> > 3) recompile all ports(modules)
> >
> > You can use apache13-modssl just as a replacment to apache13.
> > But apache13-modssl uses extrand API, so you have to
> > recompile all apache modules with "apache13-modssl" installed.
> >
> > all modules will build, install and run fine, maybe portupgrade
> > will see wrong dependencys.
> >
> > some ports suports this very well using in /etc/make.conf
> > APACHE_PORT=www/apache13-modssl
> >
> > still some ports use a "obsolete" setting like:
> > APACHE_PORT=${PORTSDIR}/www/apache13-modssl
> > AP_PORT=www/apache13-modssl
> > AP_PORT=apache13-modssl
> >
> > This might be improved after The 4.9 Release
> > http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/32604
cully wrote:
> Would you avoid portupgrade for this?
>
> I am a little shaky in the knees at this prospect. This is on a
> production web server getting over 1 million page views per day. I use
> mod_php4, mod_auth_pgsql, mod_gzip, mailman, and I have some other ports
> installed like squirrelmail, mnogosearch, a bunch of pear libraries (not
> even sure if they are dependent on apache13), phpMyAdmin and probably a
> few other things I haven't even thought of.
>
> Once this is done do all these ports change to think they are dependent
> on apache13-modssl rather than www/apache13?
Yes, the PR#32604 will fix this.
But even now, you don't have to worry,
just be sure the modules are compiled with only www/apache13-modssl
installed, if portupgrade dones not overwrite with with "www/apache13"
in some coases you are perfectly fine, even if some ports register
a wrong dependency.
kind regards Dirk
- Dirk Meyer, Im Grund 4, 34317 Habichtswald, Germany
- [EMAIL PROTECTED],[EMAIL PROTECTED],[EMAIL PROTECTED]
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: apache13 to apache13-modssl port migration
> culley harrelson wrote: > > I am a little shaky in the knees at this prospect. This is on a > > production web server getting over 1 million page views per day. I use > > mod_php4, mod_auth_pgsql, mod_gzip, mailman, and I have some other ports > > installed like squirrelmail, mnogosearch, a bunch of pear libraries (not > > even sure if they are dependent on apache13), phpMyAdmin and probably a > > few other things I haven't even thought of. > > You have complete backups, right? You probably should have a test server where > you can test the software upgrade under non-production conditions... > If you have another machine you can do this with much less stress. 1.Build the second machine (aka "new" server); 2. Rsync the files over (or from a backup). 3. Pull the network plug on the original; 4. Run a script to fire off any extra ip addresses for your "new" server. 5. Apachectl startssl on the "new" server. Now it should be running and you can do spot checks to see how your crucial sites are doing... If everything is ok thats great! If not then pull the network plug on the "new" server and plug the old one back in while you see where the problems are on the new one... HTH, Lewis ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: apache13 to apache13-modssl port migration
You have complete backups, right? You probably should have a test server where you can test the software upgrade under non-production conditions... Yes of course. I am 1/2 way through a 4 month stint on the road and all I have is a laptop... ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: apache13 to apache13-modssl port migration
culley harrelson wrote: I am a little shaky in the knees at this prospect. This is on a production web server getting over 1 million page views per day. I use mod_php4, mod_auth_pgsql, mod_gzip, mailman, and I have some other ports installed like squirrelmail, mnogosearch, a bunch of pear libraries (not even sure if they are dependent on apache13), phpMyAdmin and probably a few other things I haven't even thought of. You have complete backups, right? You probably should have a test server where you can test the software upgrade under non-production conditions... -- -Chuck ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: apache13 to apache13-modssl port migration
The transition is easy.
1) deinstall all your ports(modules) depended on apache13
2) install apache13-modssl.
3) recompile all ports(modules)
You can use apache13-modssl just as a replacment to apache13.
But apache13-modssl uses extrand API, so you have to
recompile all apache modules with "apache13-modssl" installed.
all modules will build, install and run fine, maybe portupgrade
will see wrong dependencys.
some ports suports this very well using in /etc/make.conf
APACHE_PORT=www/apache13-modssl
still some ports use a "obsolete" setting like:
APACHE_PORT=${PORTSDIR}/www/apache13-modssl
AP_PORT= www/apache13-modssl
AP_PORT= apache13-modssl
This might be improved after The 4.9 Release
http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/32604
kind regards Dirk
Would you avoid portupgrade for this?
I am a little shaky in the knees at this prospect. This is on a
production web server getting over 1 million page views per day. I use
mod_php4, mod_auth_pgsql, mod_gzip, mailman, and I have some other ports
installed like squirrelmail, mnogosearch, a bunch of pear libraries (not
even sure if they are dependent on apache13), phpMyAdmin and probably a
few other things I haven't even thought of.
Once this is done do all these ports change to think they are dependent
on apache13-modssl rather than www/apache13?
culley
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: apache13 to apache13-modssl port migration
I made the same transition... I had apache13 installed from ports, and then found myself in need of SSL support. I didn't uninstall apache13, I simply went to the apache13-modssl port and typed: make all install clean No problems. There was a new httpsd.conf file under my /usr/local/etc/apache directory and I simply cut and pasted the virtual host information from my httpd.conf to httpsd.conf file. Then I followed the instructions on the mod-ssl web site. http://www.modssl.org/ Good luck Peter Elsner At 08:04 PM 9/9/2003 -0700, you wrote: I am currently running /usr/ports/www/apache13 and I want to switch to /usr/ports/www/apache13-modssl. Has anyone make this transition? I don't know what to expect and I don't have a freebsd test box right now. I am worried about the ports dependent on apache13-- what happens to them if I just install apache13-modssl on top? I do use portupgrade. culley ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]" Peter Elsner <[EMAIL PROTECTED]> Vice President Of Customer Service (And System Administrator) 1835 S. Carrier Parkway Grand Prairie, Texas 75051 (972) 263-2080 - Voice (972) 263-2082 - Fax (972) 489-4838 - Cell Phone ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: apache13 to apache13-modssl port migration
Don't install it on top of you old installation. cd /usr/ports/www/apache13 make deinstall - or - pkg_delete -f apache-1.3.xx Then: cd /usr/ports/www/apache13-modssl make install clean make certificate (optional) Your original httpd.conf won't be deleted. You can use the new one (httpd.conf-dist) as a reference for the SSL directives and migrate your settings. You should also manually replace the old startup script with the new one (apache.sh-sample) as it is slightly different (it enables mod_ssl at startup). > I am currently running /usr/ports/www/apache13 and I want to switch to > /usr/ports/www/apache13-modssl. Has anyone make this transition? I > don't know what to expect and I don't have a freebsd test box right now. > I am worried about the ports dependent on apache13-- what happens to > them if I just install apache13-modssl on top? I do use portupgrade. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
apache13 to apache13-modssl port migration
I am currently running /usr/ports/www/apache13 and I want to switch to /usr/ports/www/apache13-modssl. Has anyone make this transition? I don't know what to expect and I don't have a freebsd test box right now. I am worried about the ports dependent on apache13-- what happens to them if I just install apache13-modssl on top? I do use portupgrade. culley ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Anyone built apache13-modssl since June 04?
For the archives ... I'm not sure what was wrong, but I completely reinstalled the machine with FreeBSD 4.8 and the port then built without issue. Not sure what I did to this test machine to cause it to act so, but I hope the production server doesn't have the same problem! Dirk Meyer wrote: Bill Moran schrieb:, I'm trying to build/install the apache13-modssl port and I'm getting continual failures at the same point Anyone else having trouble with this. Looks like the last commit was made on the 4th, so this could be fairly recent breakage. nope ... builds here on stable and current. cc -c -I/usr/local/include -I../os/unix -I../include -DHARD_SERVER_LIMIT=512 -DDOCUMENT_LOCATION=\"/usr/local/www/data/\" -DDEFAULT_PATH=\"/usr/local/bin :/bin:/usr/bin\" -DACCEPT_FILTER_NAME=\"httpready\" -DFD_SETSIZE=1024 -funsig ned-char -DMOD_SSL=208114 -DEAPI -DEAPI_MM -DUSE_EXPAT -I../lib/expat-lite -O -pipe -DNO_IDEA -Wl,-rpath,/usr/lib:/usr/local/lib `../apaci` alloc.c alloc.c:146: syntax error before `*' alloc.c:146: warning: data definition has no type or storage class alloc.c: In function `free_blocks': alloc.c:324: `AP_MM_LOCK_RW' undeclared (first use in this function) your mm looks broken. Please reinstall your mm $ cd /usr/ports/devel/mm && make deinstall $ cd /usr/ports/devel/mm && make install kind regards Dirk - Dirk Meyer, Im Grund 4, 34317 Habichtswald, Germany - [EMAIL PROTECTED],[EMAIL PROTECTED],[EMAIL PROTECTED] -- Bill Moran Potential Technologies http://www.potentialtech.com ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Anyone built apache13-modssl since June 04?
Dirk Meyer wrote: Bill Moran schrieb:, I'm trying to build/install the apache13-modssl port and I'm getting continual failures at the same point Anyone else having trouble with this. Looks like the last commit was made on the 4th, so this could be fairly recent breakage. nope ... builds here on stable and current. What version of mm are you using? I've tried installing multiple times and each time I get the exact same failure. I've reinstalled mm at least 3 times, refetched the source for mm twice and tried using pkg_add to install mm once and nothing changes. I've upgraded to 4.8, rebuilt world and kernel without grief, so I'm assuming the hardware is sound. Any guess why mm won't work? cc -c -I/usr/local/include -I../os/unix -I../include -DHARD_SERVER_LIMIT=512 -DDOCUMENT_LOCATION=\"/usr/local/www/data/\" -DDEFAULT_PATH=\"/usr/local/bin :/bin:/usr/bin\" -DACCEPT_FILTER_NAME=\"httpready\" -DFD_SETSIZE=1024 -funsig ned-char -DMOD_SSL=208114 -DEAPI -DEAPI_MM -DUSE_EXPAT -I../lib/expat-lite -O -pipe -DNO_IDEA -Wl,-rpath,/usr/lib:/usr/local/lib `../apaci` alloc.c alloc.c:146: syntax error before `*' alloc.c:146: warning: data definition has no type or storage class alloc.c: In function `free_blocks': alloc.c:324: `AP_MM_LOCK_RW' undeclared (first use in this function) your mm looks broken. Please reinstall your mm $ cd /usr/ports/devel/mm && make deinstall $ cd /usr/ports/devel/mm && make install -- Bill Moran Potential Technologies http://www.potentialtech.com ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Anyone built apache13-modssl since June 04?
Dirk Meyer wrote: Bill Moran schrieb:, I'm trying to build/install the apache13-modssl port and I'm getting continual failures at the same point Anyone else having trouble with this. Looks like the last commit was made on the 4th, so this could be fairly recent breakage. nope ... builds here on stable and current. cc -c -I/usr/local/include -I../os/unix -I../include -DHARD_SERVER_LIMIT=512 -DDOCUMENT_LOCATION=\"/usr/local/www/data/\" -DDEFAULT_PATH=\"/usr/local/bin :/bin:/usr/bin\" -DACCEPT_FILTER_NAME=\"httpready\" -DFD_SETSIZE=1024 -funsig ned-char -DMOD_SSL=208114 -DEAPI -DEAPI_MM -DUSE_EXPAT -I../lib/expat-lite -O -pipe -DNO_IDEA -Wl,-rpath,/usr/lib:/usr/local/lib `../apaci` alloc.c alloc.c:146: syntax error before `*' alloc.c:146: warning: data definition has no type or storage class alloc.c: In function `free_blocks': alloc.c:324: `AP_MM_LOCK_RW' undeclared (first use in this function) your mm looks broken. Please reinstall your mm I did 3 times. Once with a 4.7-RELEASE system Then upgrade to RELENG_4_8 Then tried 2 more times make clean && pkg_delete in between each one. I'll try again. Perhaps I can figure out more from this. -- Bill Moran Potential Technologies http://www.potentialtech.com ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Anyone built apache13-modssl since June 04?
Hey all, I'm trying to build/install the apache13-modssl port and I'm getting continual failures at the same point (included at the end of the email) Anyone else having trouble with this. Looks like the last commit was made on the 4th, so this could be fairly recent breakage. p.s. Please keep me in the CC, I'm not subscribed at this time. ===> src/main cc -c -I/usr/local/include -I../os/unix -I../include -DHARD_SERVER_LIMIT=512 -DDOCUMENT_LOCATION=\"/usr/local/www/data/\" -DDEFAULT_PATH=\"/usr/local/bin:/bin:/usr/bin\" -DACCEPT_FILTER_NAME=\"httpready\" -DFD_SETSIZE=1024 -funsigned-char -DMOD_SSL=208114 -DEAPI -DEAPI_MM -DUSE_EXPAT -I../lib/expat-lite -O -pipe -DNO_IDEA -Wl,-rpath,/usr/lib:/usr/local/lib `../apaci` gen_test_char.c cc: -rpath: linker input file unused since linking not done cc: /usr/lib:/usr/local/lib: linker input file unused since linking not done cc -DHARD_SERVER_LIMIT=512 -DDOCUMENT_LOCATION=\"/usr/local/www/data/\" -DDEFAULT_PATH=\"/usr/local/bin:/bin:/usr/bin\" -DACCEPT_FILTER_NAME=\"httpready\" -DFD_SETSIZE=1024 -funsigned-char -DMOD_SSL=208114 -DEAPI -DEAPI_MM -DUSE_EXPAT -I../lib/expat-lite -O -pipe -DNO_IDEA -Wl,-rpath,/usr/lib:/usr/local/lib `../apaci` -L/usr/local/lib -o gen_test_char gen_test_char.o -lcrypt -lmm ./gen_test_char >test_char.h cc -c -I/usr/local/include -I../os/unix -I../include -DHARD_SERVER_LIMIT=512 -DDOCUMENT_LOCATION=\"/usr/local/www/data/\" -DDEFAULT_PATH=\"/usr/local/bin:/bin:/usr/bin\" -DACCEPT_FILTER_NAME=\"httpready\" -DFD_SETSIZE=1024 -funsigned-char -DMOD_SSL=208114 -DEAPI -DEAPI_MM -DUSE_EXPAT -I../lib/expat-lite -O -pipe -DNO_IDEA -Wl,-rpath,/usr/lib:/usr/local/lib `../apaci` gen_uri_delims.c cc: -rpath: linker input file unused since linking not done cc: /usr/lib:/usr/local/lib: linker input file unused since linking not done cc -DHARD_SERVER_LIMIT=512 -DDOCUMENT_LOCATION=\"/usr/local/www/data/\" -DDEFAULT_PATH=\"/usr/local/bin:/bin:/usr/bin\" -DACCEPT_FILTER_NAME=\"httpready\" -DFD_SETSIZE=1024 -funsigned-char -DMOD_SSL=208114 -DEAPI -DEAPI_MM -DUSE_EXPAT -I../lib/expat-lite -O -pipe -DNO_IDEA -Wl,-rpath,/usr/lib:/usr/local/lib `../apaci` -L/usr/local/lib -o gen_uri_delims gen_uri_delims.o -lcrypt -lmm ./gen_uri_delims >uri_delims.h cc -c -I/usr/local/include -I../os/unix -I../include -DHARD_SERVER_LIMIT=512 -DDOCUMENT_LOCATION=\"/usr/local/www/data/\" -DDEFAULT_PATH=\"/usr/local/bin:/bin:/usr/bin\" -DACCEPT_FILTER_NAME=\"httpready\" -DFD_SETSIZE=1024 -funsigned-char -DMOD_SSL=208114 -DEAPI -DEAPI_MM -DUSE_EXPAT -I../lib/expat-lite -O -pipe -DNO_IDEA -Wl,-rpath,/usr/lib:/usr/local/lib `../apaci` alloc.c alloc.c:146: syntax error before `*' alloc.c:146: warning: data definition has no type or storage class alloc.c: In function `free_blocks': alloc.c:324: `AP_MM_LOCK_RW' undeclared (first use in this function) alloc.c:324: (Each undeclared identifier is reported only once alloc.c:324: for each function it appears in.) alloc.c: In function `make_sub_pool_internal': alloc.c:503: `AP_MM_LOCK_RW' undeclared (first use in this function) alloc.c: In function `ap_init_alloc_shared': alloc.c:626: `EAPI_MM_CORE_MAXSIZE' undeclared (first use in this function) alloc.c:631: warning: assignment makes pointer from integer without a cast alloc.c:633: warning: assignment makes pointer from integer without a cast alloc.c: In function `ap_clear_pool': alloc.c:679: `AP_MM_LOCK_RW' undeclared (first use in this function) alloc.c: In function `ap_destroy_pool': alloc.c:724: `AP_MM_LOCK_RW' undeclared (first use in this function) alloc.c: At top level: alloc.c:755: syntax error before `ap_pool_lock_mode' alloc.c: In function `ap_acquire_pool': alloc.c:758: `p' undeclared (first use in this function) alloc.c:760: `mode' undeclared (first use in this function) alloc.c:760: `AP_POOL_RD' undeclared (first use in this function) alloc.c:760: `AP_MM_LOCK_RD' undeclared (first use in this function) alloc.c:760: `AP_MM_LOCK_RW' undeclared (first use in this function) alloc.c: In function `ap_palloc': alloc.c:945: `AP_MM_LOCK_RW' undeclared (first use in this function) alloc.c: In function `psprintf_flush': alloc.c:1114: `AP_MM_LOCK_RW' undeclared (first use in this function) *** Error code 1 Stop in /usr/ports/www/apache13-modssl/work/apache_1.3.27/src/main. *** Error code 1 Stop in /usr/ports/www/apache13-modssl/work/apache_1.3.27/src. *** Error code 1 Stop in /usr/ports/www/apache13-modssl/work/apache_1.3.27. *** Error code 1 Stop in /usr/ports/www/apache13-modssl/work/apache_1.3.27. *** Error code 1 Stop in /usr/ports/www/apache13-modssl. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
apache13-modssl + mod_perl (static) from the ports
Hello users, Is there a way to install modperl1 statically with apache-1.3.27 from the ports tree?. This used to be there sometimes back but my memory crashed! ;) I would like to install apache-modssl from the ports and have modperl1 installed statically with it. Thanks for any pointers -Wash -- Odhiambo Washington <[EMAIL PROTECTED]> "The box said 'Requires Wananchi Online Ltd. www.wananchi.com Windows 95, NT, or better,' Tel: +254 2 313985-9 +254 2 313922 so I installed FreeBSD." GSM: +254 72 743223 +254 733 744121 This sig is McQ! :-) Although golf was originally restricted to wealthy, overweight Protestants, today it's open to anybody who owns hideous clothing. -- Dave Barry To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-questions" in the body of the message
Re: apache13-modssl + mod_php4, php not interpreted
Hi Tom, Thanks I was missing the 'Addtype ...' lines in my http.conf file. Once I added those and restarted the server everything worked. Thanks again, Nigel On Thu, 03 Oct 2002, Thomas T. Veldhouse wrote: > First, did you start your server with SSL? Second, unless you want php to > run ONLY with SSL, I would move it out of that block so that it will start > anytime. Lastly, make sure you have the following in your config. > > [...] > DirectoryIndex index.php index.html > [...] > AddType application/x-httpd-php .php > AddType application/x-httpd-php-source .phps > [...] > > Tom Veldhouse > > - Original Message - > From: "Nigel Soon" <[EMAIL PROTECTED]> > To: <[EMAIL PROTECTED]> > Sent: Thursday, October 03, 2002 1:15 PM > Subject: apache13-modssl + mod_php4, php not interpreted > > > > Hello, > > > > I have a problem with php not being interpreted now that I have > > started using apache13-modssl instead of apache13. > > > > I am running freebsd 4.6-RELEASE. The procedure I went through > > was removing mod_php4 then removing apache. I then changed the > > dependency of mod_php4 to use apache13-modssl and recompiled. > > > > The web server starts fine using ssl but the php web pages are > > not interpreted. I have the following lines in my http.conf > > file which leads me to believe the php modules are being loaded > > > > --- > > > > LoadModule ssl_module libexec/apache/libssl.so > > LoadModule php4_modulelibexec/apache/libphp4.so > > > > . > > . > > . > > . > > > > AddModule mod_ssl.c > > AddModule mod_php4.c > > > > --- > > > > > > Does anybody have any ideas? > > > > Thanks, > > > > Nigel > > > > > > To Unsubscribe: send mail to [EMAIL PROTECTED] > > with "unsubscribe freebsd-questions" in the body of the message > > > To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-questions" in the body of the message
RE: apache13-modssl + mod_php4, php not interpreted
Make sure that the following lines are also present in httpd.conf AddType application/x-httpd-php .php AddType application/x-httpd-php-source .phps Without these, apache will not interpret php. Good luck! - Octavian -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] On Behalf Of Nigel Soon Sent: Thursday, October 03, 2002 11:16 AM To: [EMAIL PROTECTED] Subject: apache13-modssl + mod_php4, php not interpreted Hello, I have a problem with php not being interpreted now that I have started using apache13-modssl instead of apache13. I am running freebsd 4.6-RELEASE. The procedure I went through was removing mod_php4 then removing apache. I then changed the dependency of mod_php4 to use apache13-modssl and recompiled. The web server starts fine using ssl but the php web pages are not interpreted. I have the following lines in my http.conf file which leads me to believe the php modules are being loaded --- LoadModule ssl_module libexec/apache/libssl.so LoadModule php4_modulelibexec/apache/libphp4.so .. .. .. .. AddModule mod_ssl.c AddModule mod_php4.c --- Does anybody have any ideas? Thanks, Nigel To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-questions" in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-questions" in the body of the message
Re: apache13-modssl + mod_php4, php not interpreted
First, did you start your server with SSL? Second, unless you want php to run ONLY with SSL, I would move it out of that block so that it will start anytime. Lastly, make sure you have the following in your config. [...] DirectoryIndex index.php index.html [...] AddType application/x-httpd-php .php AddType application/x-httpd-php-source .phps [...] Tom Veldhouse - Original Message - From: "Nigel Soon" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Thursday, October 03, 2002 1:15 PM Subject: apache13-modssl + mod_php4, php not interpreted > Hello, > > I have a problem with php not being interpreted now that I have > started using apache13-modssl instead of apache13. > > I am running freebsd 4.6-RELEASE. The procedure I went through > was removing mod_php4 then removing apache. I then changed the > dependency of mod_php4 to use apache13-modssl and recompiled. > > The web server starts fine using ssl but the php web pages are > not interpreted. I have the following lines in my http.conf > file which leads me to believe the php modules are being loaded > > --- > > LoadModule ssl_module libexec/apache/libssl.so > LoadModule php4_modulelibexec/apache/libphp4.so > > . > . > . > . > > AddModule mod_ssl.c > AddModule mod_php4.c > > --- > > > Does anybody have any ideas? > > Thanks, > > Nigel > > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-questions" in the body of the message > To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-questions" in the body of the message
apache13-modssl + mod_php4, php not interpreted
Hello, I have a problem with php not being interpreted now that I have started using apache13-modssl instead of apache13. I am running freebsd 4.6-RELEASE. The procedure I went through was removing mod_php4 then removing apache. I then changed the dependency of mod_php4 to use apache13-modssl and recompiled. The web server starts fine using ssl but the php web pages are not interpreted. I have the following lines in my http.conf file which leads me to believe the php modules are being loaded --- LoadModule ssl_module libexec/apache/libssl.so LoadModule php4_modulelibexec/apache/libphp4.so . . . . AddModule mod_ssl.c AddModule mod_php4.c --- Does anybody have any ideas? Thanks, Nigel To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-questions" in the body of the message
RE: latest apache13-modssl does not compile
For the archives, this worked fine. Many thanks! James > -Original Message- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED]]On Behalf Of James Green > Sent: 24 September 2002 15:08 > To: Matthew Seaman > Cc: [EMAIL PROTECTED] > Subject: RE: latest apache13-modssl does not compile > > > Mathew, > > bash-2.05a$ pkg_info |grep apache > apache-1.3.26_3 The extremely popular Apache http server. Very fast, > very > > Hard to see how an existing copy of the same version would cause a > problem... > > I'll remove and try again I guess. > > James. > > > > -Original Message- > > From: [EMAIL PROTECTED] > > [mailto:[EMAIL PROTECTED]]On Behalf Of Matthew Seaman > > Sent: 24 September 2002 14:49 > > To: James Green > > Cc: Matthew Seaman; [EMAIL PROTECTED] > > Subject: Re: latest apache13-modssl does not compile > > > > > > On Tue, Sep 24, 2002 at 02:16:58PM +0100, James Green wrote: > > > > > mm is already 1.2.1: > > > > > > bash-2.05a$ pkg_info |grep ^mm > > > mm-1.2.1Shared memory allocation library for > > applications with > > > pre- > > > > > > Any other ideas? > > > > Actually yes. It's deja-vu all over again... > > > > http://groups.google.co.uk/groups?hl=en&lr=lang_en&ie=UTF-8&oe=UTF > > -8&safe=off&threadm=al4vsp%24ahf%241%40FreeBSD.csie.NCTU.edu.tw&rn > > um=1&prev=/groups%3Fhl%3Den%26ie%3DUTF-8%26oe%3DUTF-8%26safe%3Doff > > %26q%3DFreeBSD%2Bapache%2Bap_mm.h%26sa%3DN%26tab%3Dwg > > > > Short answer: you need to remove the old apache header files 'ap_*.h' > > from /usr/local/include before you do the build. > > > > As you're at least the second person to run into this, it's definitely > > time to send-pr --- it seems this problem only occurs when you've got > > a previous installation of apache on the system. Do you mind telling > > me what apache version you've currently got installed so I can try and > > reproduce the problem? > > > > Cheers, > > > > Matthew > > > > -- > > Dr Matthew J Seaman MA, D.Phil. 26 The Paddocks > > Savill Way > > Marlow > > Tel: +44 1628 476614 Bucks., SL7 1TH UK > > > > To Unsubscribe: send mail to [EMAIL PROTECTED] > > with "unsubscribe freebsd-questions" in the body of the message > > > > > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-questions" in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-questions" in the body of the message
RE: latest apache13-modssl does not compile
Mathew, bash-2.05a$ pkg_info |grep apache apache-1.3.26_3 The extremely popular Apache http server. Very fast, very Hard to see how an existing copy of the same version would cause a problem... I'll remove and try again I guess. James. > -Original Message- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED]]On Behalf Of Matthew Seaman > Sent: 24 September 2002 14:49 > To: James Green > Cc: Matthew Seaman; [EMAIL PROTECTED] > Subject: Re: latest apache13-modssl does not compile > > > On Tue, Sep 24, 2002 at 02:16:58PM +0100, James Green wrote: > > > mm is already 1.2.1: > > > > bash-2.05a$ pkg_info |grep ^mm > > mm-1.2.1Shared memory allocation library for > applications with > > pre- > > > > Any other ideas? > > Actually yes. It's deja-vu all over again... > > http://groups.google.co.uk/groups?hl=en&lr=lang_en&ie=UTF-8&oe=UTF > -8&safe=off&threadm=al4vsp%24ahf%241%40FreeBSD.csie.NCTU.edu.tw&rn > um=1&prev=/groups%3Fhl%3Den%26ie%3DUTF-8%26oe%3DUTF-8%26safe%3Doff > %26q%3DFreeBSD%2Bapache%2Bap_mm.h%26sa%3DN%26tab%3Dwg > > Short answer: you need to remove the old apache header files 'ap_*.h' > from /usr/local/include before you do the build. > > As you're at least the second person to run into this, it's definitely > time to send-pr --- it seems this problem only occurs when you've got > a previous installation of apache on the system. Do you mind telling > me what apache version you've currently got installed so I can try and > reproduce the problem? > > Cheers, > > Matthew > > -- > Dr Matthew J Seaman MA, D.Phil. 26 The Paddocks > Savill Way > Marlow > Tel: +44 1628 476614 Bucks., SL7 1TH UK > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-questions" in the body of the message > To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-questions" in the body of the message
Re: latest apache13-modssl does not compile
On Tue, Sep 24, 2002 at 02:16:58PM +0100, James Green wrote: > mm is already 1.2.1: > > bash-2.05a$ pkg_info |grep ^mm > mm-1.2.1Shared memory allocation library for applications with > pre- > > Any other ideas? Actually yes. It's deja-vu all over again... http://groups.google.co.uk/groups?hl=en&lr=lang_en&ie=UTF-8&oe=UTF-8&safe=off&threadm=al4vsp%24ahf%241%40FreeBSD.csie.NCTU.edu.tw&rnum=1&prev=/groups%3Fhl%3Den%26ie%3DUTF-8%26oe%3DUTF-8%26safe%3Doff%26q%3DFreeBSD%2Bapache%2Bap_mm.h%26sa%3DN%26tab%3Dwg Short answer: you need to remove the old apache header files 'ap_*.h' from /usr/local/include before you do the build. As you're at least the second person to run into this, it's definitely time to send-pr --- it seems this problem only occurs when you've got a previous installation of apache on the system. Do you mind telling me what apache version you've currently got installed so I can try and reproduce the problem? Cheers, Matthew -- Dr Matthew J Seaman MA, D.Phil. 26 The Paddocks Savill Way Marlow Tel: +44 1628 476614 Bucks., SL7 1TH UK To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-questions" in the body of the message
RE: latest apache13-modssl does not compile
Hi Mathew, mm is already 1.2.1: bash-2.05a$ pkg_info |grep ^mm mm-1.2.1Shared memory allocation library for applications with pre- Any other ideas? James. > -Original Message- > From: Matthew Seaman [mailto:[EMAIL PROTECTED]] > Sent: 24 September 2002 14:12 > To: James Green > Cc: [EMAIL PROTECTED] > Subject: Re: latest apache13-modssl does not compile > > > On Tue, Sep 24, 2002 at 11:12:46AM +0100, James Green wrote: > > > I've got three boxes running FreeBSD4.5 with no src upgrades. > I've got an up > > to date ports collection using cvsup. > > > > Gone into /usr/ports/www/apache13-modssl and done 'make build'. > It gives me: > > > > cc -c -I/usr/local/include -I../os/unix -I../include > -DHARD_SERVER_LIMIT=51 > > 2 -DDOCUMENT_LOCATION=\"/usr/local/www/data/\" > -DDEFAULT_PATH=\"/usr/local > > /bin:/bin:/usr/bin\" -DACCEPT_FILTER_NAME=\"httpready\" > -funsigned-char -DM > > OD_SSL=208110 -DEAPI -DEAPI_MM -DUSE_EXPAT -I../lib/expat-lite -O -pipe > > `../apaci` alloc.c > > alloc.c:146: syntax error before `*' > > alloc.c:146: warning: data definition has no type or storage class > > alloc.c: In function `free_blocks': > > alloc.c:324: `AP_MM_LOCK_RW' undeclared (first use in this function) > > alloc.c:324: (Each undeclared identifier is reported only once > > alloc.c:324: for each function it appears in.) > > Update your devel/mm port to version 1.2.1 > > Cheers, > > Matthew > > -- > Dr Matthew J Seaman MA, D.Phil. 26 The Paddocks > Savill Way > Marlow > Tel: +44 1628 476614 Bucks., SL7 1TH UK > To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-questions" in the body of the message
Re: latest apache13-modssl does not compile
On Tue, Sep 24, 2002 at 11:12:46AM +0100, James Green wrote: > I've got three boxes running FreeBSD4.5 with no src upgrades. I've got an up > to date ports collection using cvsup. > > Gone into /usr/ports/www/apache13-modssl and done 'make build'. It gives me: > > cc -c -I/usr/local/include -I../os/unix -I../include -DHARD_SERVER_LIMIT=51 > 2 -DDOCUMENT_LOCATION=\"/usr/local/www/data/\" -DDEFAULT_PATH=\"/usr/local > /bin:/bin:/usr/bin\" -DACCEPT_FILTER_NAME=\"httpready\" -funsigned-char -DM > OD_SSL=208110 -DEAPI -DEAPI_MM -DUSE_EXPAT -I../lib/expat-lite -O -pipe > `../apaci` alloc.c > alloc.c:146: syntax error before `*' > alloc.c:146: warning: data definition has no type or storage class > alloc.c: In function `free_blocks': > alloc.c:324: `AP_MM_LOCK_RW' undeclared (first use in this function) > alloc.c:324: (Each undeclared identifier is reported only once > alloc.c:324: for each function it appears in.) Update your devel/mm port to version 1.2.1 Cheers, Matthew -- Dr Matthew J Seaman MA, D.Phil. 26 The Paddocks Savill Way Marlow Tel: +44 1628 476614 Bucks., SL7 1TH UK To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-questions" in the body of the message
latest apache13-modssl does not compile
Hi all, Sorry if this has been posted before, but I've not seen anything in the bug report db. I've got three boxes running FreeBSD4.5 with no src upgrades. I've got an up to date ports collection using cvsup. Gone into /usr/ports/www/apache13-modssl and done 'make build'. It gives me: cc -c -I/usr/local/include -I../os/unix -I../include -DHARD_SERVER_LIMIT=51 2 -DDOCUMENT_LOCATION=\"/usr/local/www/data/\" -DDEFAULT_PATH=\"/usr/local /bin:/bin:/usr/bin\" -DACCEPT_FILTER_NAME=\"httpready\" -funsigned-char -DM OD_SSL=208110 -DEAPI -DEAPI_MM -DUSE_EXPAT -I../lib/expat-lite -O -pipe `../apaci` alloc.c alloc.c:146: syntax error before `*' alloc.c:146: warning: data definition has no type or storage class alloc.c: In function `free_blocks': alloc.c:324: `AP_MM_LOCK_RW' undeclared (first use in this function) alloc.c:324: (Each undeclared identifier is reported only once alloc.c:324: for each function it appears in.) alloc.c: In function `make_sub_pool_internal': alloc.c:503: `AP_MM_LOCK_RW' undeclared (first use in this function) alloc.c: In function `ap_init_alloc_shared': alloc.c:626: `EAPI_MM_CORE_MAXSIZE' undeclared (first use in this function) alloc.c:631: warning: assignment makes pointer from integer without a cast alloc.c:633: warning: assignment makes pointer from integer without a cast alloc.c: In function `ap_clear_pool': alloc.c:679: `AP_MM_LOCK_RW' undeclared (first use in this function) alloc.c: In function `ap_destroy_pool': alloc.c:724: `AP_MM_LOCK_RW' undeclared (first use in this function) alloc.c: At top level: alloc.c:755: syntax error before `ap_pool_lock_mode' alloc.c: In function `ap_acquire_pool': alloc.c:758: `p' undeclared (first use in this function) alloc.c:760: `mode' undeclared (first use in this function) alloc.c:760: `AP_POOL_RD' undeclared (first use in this function) alloc.c:760: `AP_MM_LOCK_RD' undeclared (first use in this function) alloc.c:760: `AP_MM_LOCK_RW' undeclared (first use in this function) alloc.c: In function `ap_palloc': alloc.c:945: `AP_MM_LOCK_RW' undeclared (first use in this function) alloc.c: In function `psprintf_flush': alloc.c:1106: `AP_MM_LOCK_RW' undeclared (first use in this function) *** Error code 1 Stop in /usr/ports/www/apache13-modssl/work/apache_1.3.26/src/main. *** Error code 1 Stop in /usr/ports/www/apache13-modssl/work/apache_1.3.26/src. *** Error code 1 Stop in /usr/ports/www/apache13-modssl/work/apache_1.3.26. *** Error code 1 Stop in /usr/ports/www/apache13-modssl/work/apache_1.3.26. *** Error code 1 Stop in /usr/ports/www/apache13-modssl. I'm therefore looking for guidenance as to where to go now. Any ideas? TIA. -- James Green Developer Stealthnet.co.uk To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-questions" in the body of the message
