Hello Michael,
I cannot speak for Red Hat, but the difference between the 2.4 and 2.2
vulnerabilities page is clear.
The fix for CVE-2014-0226 was announced with the release of Apache httpd
2.4.10.
The fix will also be included in Apache httpd 2.2.28 which has not yet
been released.
-
http://
sorry I send it a wrong message this should be on squid mailing-
list
Hello
we all know that access.log file logs the access Info of Squid, something like
that:
125213512.746 41762 192.168.1.17 ..
125213513.746 47616 192.168.1.18 ..
and
we all know that squid use the file /etc/resolv.conf to determine the
DNS server it is dealing wit
On Tue, 29 Jul 2014 20:15:29 +0200
Daniel wrote:
> ServerName and certificate CN should match, and if it's a wildcard it
> should be added to a ServerAlias directive.
Yes, checked all that and still it didn't work under 2.4.9 but worked
just fine under 2.4.10.
--
D'Arcy J.M. Cain
System Adminis
ServerName and certificate CN should match, and if it's a wildcard it
should be added to a ServerAlias directive.
2014-07-29 18:33 GMT+02:00 D'Arcy J.M. Cain :
> On Tue, 15 Jul 2014 04:32:59 -0400
> "D'Arcy J.M. Cain" wrote:
> > I have been trying to upgrade to Apache 2.4.9 on a NetBSD system b
On Tue, 15 Jul 2014 04:32:59 -0400
"D'Arcy J.M. Cain" wrote:
> I have been trying to upgrade to Apache 2.4.9 on a NetBSD system but I
> am running into this issue. The server starts but I get a bunch of
> warnings and the certificate is not served. Here is an example log:
>
> [Tue Jul 15 04:11:
If a vulnerability is listed on the 2.4 page (
https://httpd.apache.org/security/vulnerabilities_24.html) - let's pick on
CVE-2014-0226 for mod_status and it is listed as affecting 2.4.9 down to
2.4.1, would 2.2.x also be vulnerable? It is not specifically listed on
the 2.2 vulnerability page (
On Mon, Jul 28, 2014 at 7:29 AM, Mike Wenzel wrote:
> I got an cgi-script which is creating a file. This file need 775 permissions
> (rwxrwxr-x). I need to get the apache to create this file with 775
> permissions.
>
> I researched, but 90% of all those solutions doesn't work for me or those
> "in
Chris,
have you been able to setup the forward-proxy scenario with Apache?
We are trying to setup a similar configuration but have not been able to do
so.
There is certainly at least a certificate issue that is not easy to solve.
As with termination the client would not *see* the actual end-poin
On Tue, Jul 29, 2014 at 5:33 AM, Mar Imp wrote:
> Hi Jeff,
>
> After the first restart, apache restarted itself 2 more times
> yesterday. Good news: the additional information IS part of the logs:
> [Mon Jul 28 16:48:10.070355 2014] [mpm_winnt:crit] [pid 38752:tid 388]
> (OS 6)The handle is inval
Hi Jeff,
After the first restart, apache restarted itself 2 more times
yesterday. Good news: the additional information IS part of the logs:
[Mon Jul 28 16:48:10.070355 2014] [mpm_winnt:crit] [pid 38752:tid 388]
(OS 6)The handle is invalid. : AH02644: Child: Event handle #0 (8) is
invalid
does it
11 matches
Mail list logo
