From: Michael Hampicke <gentoo-user@hadt.biz>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] apache-2.2.20 - upstream config files reappear in /etc
Date: Mon, 05 Sep 2011 09:18:44 +0200 [thread overview]
Message-ID: <4E6477D4.9070806@hadt.biz> (raw)
In-Reply-To: <4E62B912.1000005@kraav.com>
> So after upgrading against the Range header vulnerability, I find that
> apache-2.2.20 seems to litter /etc/apache2 with standard configuration
> files, while I don't remember anything at least in 2.2.1x range doing that.
Same thing happend to me, but it seems this new config files are not
included per default. I am not really sure what to make of this. Which
file should I edit from now on?
All files seem to be valid, there are no ophans in my apache2 directory
(excluding my froxlor and ssl config)
# find /etc/apache2/ -type f -print0 | xargs -0 qfile -o | egrep -v
"froxlor|ssl"
#
And if you google for "gentoo apache 2.2.20" guess what you'll find?
Yeah, that right, this Thread! :)
next prev parent reply other threads:[~2011-09-05 7:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-03 23:32 [gentoo-user] apache-2.2.20 - upstream config files reappear in /etc Leho Kraav
2011-09-05 7:18 ` Michael Hampicke [this message]
2011-09-05 15:36 ` Florian Philipp
2011-09-14 21:08 ` [gentoo-user] " Remy Blank
2011-09-15 7:43 ` Michael Hampicke
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=4E6477D4.9070806@hadt.biz \
--to=gentoo-user@hadt.biz \
--cc=gentoo-user@lists.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