From: Kim Nielsen <knielsen@proventum-solutions.net>
To: gentoo-dev@gentoo.org
Subject: [gentoo-dev] Apache security hole and ebuild
Date: 19 Jun 2002 13:05:26 +0200 [thread overview]
Message-ID: <1024484726.1197.7.camel@knielsen> (raw)
Hi,
I have a production site and have problems with the apache ebuild
its version 1.3.24-r6 and this is what I get:
fopen: No such file or directory
apache: could not open document config file /usr/conf/apache.conf
fopen: No such file or directory
apache: could not open document config file /usr/conf/apache.conf
fopen: No such file or directory
apache: could not open document config file /usr/conf/apache.conf
Could someone please fix this and patch the security hole while they are
at it ?
I have tried the #gentoo-dev channel but was not allowed to write .. so
here goes!
/Kim
--
I am the face that stares at you from the shadows.
http://www.insecurity.dk
next reply other threads:[~2002-06-19 11:05 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-19 11:05 Kim Nielsen [this message]
2002-06-19 12:39 ` [gentoo-dev] Apache security hole and ebuild Sloan Poe
2002-06-19 13:44 ` Grant Goodyear
2002-06-19 18:37 ` Doug Goldstein
2002-06-19 19:30 ` Kim Nielsen
2002-06-19 22:13 ` Bjarke Sørensen
2002-06-20 11:46 ` Wout Mertens
2002-06-20 13:48 ` Bjarke Sørensen
2002-06-20 14:58 ` Jean-Michel Smith
2002-06-21 4:00 ` [gentoo-dev] gperf and gprof Luke Graham
2002-06-21 7:24 ` Luke Graham
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1024484726.1197.7.camel@knielsen \
--to=knielsen@proventum-solutions.net \
--cc=gentoo-dev@gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox