Fwd: Re: [users@httpd] Unable to create or access scoreboard (anonymous shared memory failure)

2012-03-21 Thread William A. Rowe Jr.
Room for improvement? Forwarding as attach to include formatting. Thanks for the observations, Tianyin! --- Begin Message --- Hi, Martin, Thanks a lot! I found the root cause after diving into code. The error is caused by my wrong settings. I try to create a too big scoreboard file (which is ev

Re: Cannot start httpd v2.4.1 with mpm_build on AIX

2012-03-21 Thread Guenter Knauf
Am 21.03.2012 19:45, schrieb Michael Felt: Unfortunately - 2.4.2 is a nogo... Same compiler warning messages, install and then ... Installation Summary NameLevel PartEvent Result ---

Re: TRACE still enabled by default

2012-03-21 Thread Tim Bannister
On 21 Mar 2012, at 21:46, Stefan Fritsch wrote: > But one thing that would be very interesting in this case, namely the > X-Forwarded-For header, is something that most admins of a reverse-proxied > site do NOT want to disclose at the end-point. They may also not want to > reveal other headers

Re: TRACE still enabled by default

2012-03-21 Thread Stefan Fritsch
On Wednesday 21 March 2012, William A. Rowe Jr. wrote: > On 3/21/2012 2:59 PM, Mark Montague wrote: > > On March 21, 2012 15:33 , "Roy T. Fielding" wrote: > >> TRACE won't work at all if the most popular end-point doesn't > >> support it. > > > > Why would this be a bad thing? Or, to phrase it

one small --with-module=foo:foo tweak

2012-03-21 Thread William A. Rowe Jr.
Playing with the --with-module=foo:foo feature Jim introduced last year, I note that it can almost entirely build mod_foo.c into the server with no supporting build files, except that Makefile.in is required. The minimal contents of Makefile.in consists of include $(top_srcdir)/build/special

Re: TRACE still enabled by default

2012-03-21 Thread William A. Rowe Jr.
On 3/21/2012 2:59 PM, Mark Montague wrote: > On March 21, 2012 15:33 , "Roy T. Fielding" wrote: >> TRACE won't work at all if the most popular end-point doesn't support it. > > Why would this be a bad thing? Or, to phrase it another way, what are the > situations in > which it is desirable tha

Re: TRACE still enabled by default

2012-03-21 Thread Greg Stein
On Wed, Mar 21, 2012 at 16:23, Reindl Harald wrote: > Am 21.03.2012 21:02, schrieb Greg Stein: >> On Wed, Mar 21, 2012 at 15:59, Mark Montague wrote: >>> On March 21, 2012 15:33 , "Roy T. Fielding" wrote: TRACE won't work at all if the most popular end-point doesn't support it. >>> >>>

Re: TRACE still enabled by default

2012-03-21 Thread Reindl Harald
Am 21.03.2012 21:02, schrieb Greg Stein: > On Wed, Mar 21, 2012 at 15:59, Mark Montague wrote: >> On March 21, 2012 15:33 , "Roy T. Fielding" wrote: >>> >>> TRACE won't work at all if the most popular end-point doesn't support it. >> >> Why would this be a bad thing? Or, to phrase it another w

Re: TRACE still enabled by default

2012-03-21 Thread Mark Montague
On March 21, 2012 16:02 , Greg Stein wrote: TRACE won't work at all if the most popular end-point doesn't support it. Why would this be a bad thing? Or, to phrase it another way, what are the situations in which it is desirable that TRACE be already-enabled on a web server as opposed to having

Re: TRACE still enabled by default

2012-03-21 Thread Greg Stein
On Wed, Mar 21, 2012 at 15:59, Mark Montague wrote: > On March 21, 2012 15:33 , "Roy T. Fielding" wrote: >> >> TRACE won't work at all if the most popular end-point doesn't support it. > > Why would this be a bad thing?  Or, to phrase it another way, what are the > situations in which it is desir

Re: TRACE still enabled by default

2012-03-21 Thread Mark Montague
On March 21, 2012 15:33 , "Roy T. Fielding" wrote: TRACE won't work at all if the most popular end-point doesn't support it. Why would this be a bad thing? Or, to phrase it another way, what are the situations in which it is desirable that TRACE be already-enabled on a web server as opposed

Re: TRACE still enabled by default

2012-03-21 Thread Roy T. Fielding
On Mar 21, 2012, at 5:33 AM, Jim Jagielski wrote: > On Mar 20, 2012, at 3:04 PM, Stefan Fritsch wrote: > >> On Saturday 17 March 2012, Roy T. Fielding wrote: We still enable TRACE by default. Is this useful enough to justify making every other poor sap with a secur

Re: Cannot start httpd v2.4.1 with mpm_build on AIX

2012-03-21 Thread Michael Felt
Unfortunately - 2.4.2 is a nogo... Same compiler warning messages, install and then ... Installation Summary NameLevel PartEvent Result --- ASF.httpd.rt

Re: Cannot start httpd v2.4.1 with mpm_build on AIX

2012-03-21 Thread Michael Felt
root@x103:[/data/prj/httpd-trunk]build/aix/buildaix.ksh + ./configure --enable-layout=AIX --with-apr=/opt/bin/apr-1-config --with-apr-util=/opt/bin/apu-1-config --enable-mpms-shared=all --enable-mods-shared=all

Re: svn commit: r1303435 - /httpd/httpd/trunk/server/mpm_unix.c

2012-03-21 Thread Eric Covener
> @@ -937,7 +937,7 @@ AP_DECLARE(apr_status_t) ap_fatal_signal > >  #endif /* NO_USE_SIGACTION */ > > -    pconf = in_pconf; > +    pconf = pconf; >     parent_pid = my_pid = getpid(); Doesn't the parameter name need to be changed back?

Re: Cannot start httpd v2.4.1 with mpm_build on AIX

2012-03-21 Thread Michael Felt
root@x103:[/data/prj/httpd-trunk]mv ../apr ../aprx root@x103:[/data/prj/httpd-trunk]./buildconf You don't have a copy of the apr source in srclib/apr. Please get the source using the following instructions, or specify the location of the source with --with-apr=[path to apr] : svn co http://svn

Re: Cannot start httpd v2.4.1 with mpm_build on AIX

2012-03-21 Thread Michael Felt
On Wed, Mar 21, 2012 at 2:36 AM, Gregg Smith wrote: > Gün, > > It Works! > > > On 3/20/2012 4:18 PM, Guenter Knauf wrote: > >> >> Gregg, can you please run a Windows build? >> >> Gün. >> > > tried to build from fresh apr, apr-util and httpd-trunk could not run buildconf for apr because I do not

Re: TRACE still enabled by default

2012-03-21 Thread Noel Butler
On Wed, 2012-03-21 at 14:48 +0100, Reindl Harald wrote: > > Nessus, despite I do like it, and as it is a respected industry standard, > > has its fair share of false positives, > > for simple example, look at FTP, running a public FTP server you get a > > severity "medium" warning, I mean like.

Re: TRACE still enabled by default

2012-03-21 Thread Reindl Harald
Am 21.03.2012 14:41, schrieb Noel Butler: > On Wed, 2012-03-21 at 13:55 +0100, Reindl Harald wrote: >> > Firstly, as stated previously, I agree TRACE should be disabled by default > because those that need it are probably > at about 1 in 1, and I'd like to see a proper vote called on it :)

Re: TRACE still enabled by default

2012-03-21 Thread Noel Butler
On Wed, 2012-03-21 at 13:55 +0100, Reindl Harald wrote: > Firstly, as stated previously, I agree TRACE should be disabled by default because those that need it are probably at about 1 in 1, and I'd like to see a proper vote called on it :) however... > > fact is that nessus-scans usually

Re: TRACE still enabled by default

2012-03-21 Thread Reindl Harald
Am 21.03.2012 13:48, schrieb Tim Bannister: > On 21 Mar 2012, at 12:39, Reindl Harald wrote: > >> 1 out of a million servers needs TRACE enabled >> >> it was ALWAYS a good idea to disable ANYTHING by default what is not really >> needed and this principle will stay > > inetd normally ships wit

Re: TRACE still enabled by default

2012-03-21 Thread Tim Bannister
On 21 Mar 2012, at 12:39, Reindl Harald wrote: > 1 out of a million servers needs TRACE enabled > > it was ALWAYS a good idea to disable ANYTHING by default what is not really > needed and this principle will stay inetd normally ships with echo not running, but kernels usually ship with ICMP e

Re: TRACE still enabled by default

2012-03-21 Thread Reindl Harald
Am 17.03.2012 10:24, schrieb Roy T. Fielding: > On Mar 16, 2012, at 7:18 AM, Eric Covener wrote: > >> We still enable TRACE by default. >> >> Is this useful enough to justify making every other poor sap with a >> security scanner have to manually turn it off? > > Yes. > >> I'm hoping 2.4.x is

Re: TRACE still enabled by default

2012-03-21 Thread Jim Jagielski
On Mar 20, 2012, at 3:04 PM, Stefan Fritsch wrote: > On Saturday 17 March 2012, Roy T. Fielding wrote: >>> We still enable TRACE by default. >>> >>> >>> >>> Is this useful enough to justify making every other poor sap with >>> a security scanner have to manually turn it off? >> >> Yes. >> >>