You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@httpd.apache.org by Tim Thorburn <im...@nwconx.net> on 2004/05/17 18:46:49 UTC

Re: [users@httpd] Re: Bug Versions 1.3.28/29 Fixed In 1.3.31 Or Not?

Wow ...

Ok, impartial observer here ... I'm on this list because I'm a web designer 
who uses Apache for hosting and local testing, not a sysadmin or someone 
who makes their living off of the goodness that is Apache.  So far, I'm 
seeing someone present a problem that she feels is a problem, and then be 
ignored or ridiculed for thinking this is a problem.

Personally, I've asked several questions on this list and other similar 
lists wherein those who know (or in many cases those who *think* they know) 
dismiss any question to their ways as absurd remarks from those who should 
not speak.  Now, I'll be the first to admit I'm far from an expert in many 
areas, but when a person is publicly chewed out as Kira has been in this 
case ... it imposes something of an elitist view over the entire Apache 
community - don't you dare ask a question lest we mock you for wasting our 
time in asking this question.

Again, this is not something found only on this mailing list - it is quite 
frequent on the MySQL and PHP lists as well.

Ok, blah blah, who cares, half of you have deleted this message already, 
the other half are prepared your assault weapon words - the point is - 
settle boys and girls, you don't like something you see here, let it go - 
hit the trash can button extra hard if that does it for you.  Yeah, in some 
cases Kira's comments could be taken in an abrasive manner - but if you 
have 3 or 4 ppl blasting you on a public forum, might you not come off as a 
little abrasive too?

Anyways, lunch time - go do whatever it is that you do and come back more 
on the happy shiny side and less on the *i hate all who disagree with me* side.



---------------------------------------------------------------------
The official User-To-User support forum of the Apache HTTP Server Project.
See <URL:http://httpd.apache.org/userslist.html> for more info.
To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
   "   from the digest: users-digest-unsubscribe@httpd.apache.org
For additional commands, e-mail: users-help@httpd.apache.org


Re: [users@httpd] Re: Bug Versions 1.3.28/29 Fixed In 1.3.31 Or Not?

Posted by Joshua Slive <jo...@slive.ca>.
On Mon, 17 May 2004, Laura Vance wrote:
> I have an idea that should solve all problems.  (yeah, right. ;)  )
>
> What I would propose is to allow a directive in the httpd.conf file that
> would be something like this:
>
> <methodLogging>
>     DENY SEARCH etc.
>     ALLOW ALL
> </methodLogging>
>

The thing is, there is already a flexible conditional logging method using
mod_setenvif and env= on CustomLog.  It is just that certain very specific
types of malformed requests will skip the usual mod_setenvif processing.
Is it really worth it to reimpliment an existing feature just to catch
this very specific case?  (Surely some people would say yes; but I guess
nobody who is willing to code it up has said so.)

Conditional logging in apache is very flexible, but probably more
complicated than it need be.  In my ideal world, you would be able to do
conditional logging based on any of the % directives specified in
LogFormat (including the request method).  But again, many developers see
this as a low priority, since most web admins want a complete log file and
can do any necessary processing after-the-fact.

Joshua.

---------------------------------------------------------------------
The official User-To-User support forum of the Apache HTTP Server Project.
See <URL:http://httpd.apache.org/userslist.html> for more info.
To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
   "   from the digest: users-digest-unsubscribe@httpd.apache.org
For additional commands, e-mail: users-help@httpd.apache.org


Re: [users@httpd] Re: Bug Versions 1.3.28/29 Fixed In 1.3.31 OrNot?

Posted by Robert Andersson <ro...@profundis.nu>.
Purl Gurl wrote:
> Should a script kiddie decide to wipe out your disk storage,
> what would you do?

A general advice: do never put your log files on your system partition.

Logging can always eat up disk space, therefor you should configure your box
so it still will run even if the logs cannot be written. This is generally
why we have /var on its own partition.

Regards,
Robert Andersson


---------------------------------------------------------------------
The official User-To-User support forum of the Apache HTTP Server Project.
See <URL:http://httpd.apache.org/userslist.html> for more info.
To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
   "   from the digest: users-digest-unsubscribe@httpd.apache.org
For additional commands, e-mail: users-help@httpd.apache.org


Re: [users@httpd] Re: Bug Versions 1.3.28/29 Fixed In 1.3.31 OrNot?

Posted by Stephen Cook <kr...@optonline.net>.
> Your comment is a classic example of Ad Hominem, easily
> recognized by this English professor and flim flam artist.

...

> You need to pay attention. Your lack of attention, your lack
> of comprehension of what is previously written, shows well.


???


---------------------------------------------------------------------
The official User-To-User support forum of the Apache HTTP Server Project.
See <URL:http://httpd.apache.org/userslist.html> for more info.
To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
   "   from the digest: users-digest-unsubscribe@httpd.apache.org
For additional commands, e-mail: users-help@httpd.apache.org


RE: [users@httpd] Re: Bug Versions 1.3.28/29 Fixed In 1.3.31 OrNot?

Posted by Ben Chabot <vo...@amninc.net>.
> -----Original Message-----
> From: Purl Gurl [mailto:purlgurl@purlgurl.net] 
> Sent: Monday, May 17, 2004 7:26 PM
> To: users@httpd.apache.org
> Subject: Re: [users@httpd] Re: Bug Versions 1.3.28/29 Fixed 
> In 1.3.31 OrNot?
> 
> You need to pay attention. Your lack of attention, your lack
> of comprehension of what is previously written, shows well.

I'm glad to see you really are here to, "present the facts."  Your,
"firm and fair demeanor," are well displayed as well as your constant
claims to bring nothing but enlightenment to the rest of us.

Insulting the people trying to explain this problem really does nothing
but further impress the idea on the rest of us that you don't understand
what you're talking about and that you haven't spent enough time reading
anyone's replies as you have not comprehended anything that's been
discussed.
 
> Perhaps I need to lower my language level as I do for students,
> but with great hesitation and annoyance.

I must be really confused, because I thought you already did that when
you started insulting anyone with a dissenting view.

> Your comment is a classic example of Ad Hominem, easily
> recognized by this English professor and flim flam artist.

ad hom.i.nem  adj. 

Appealing to personal considerations rather than to logic or reason:
Debaters should avoid ad hominem arguments that question their
opponents' motives. 
 
> Most ironic, yes?

Only as ironic as your continued misuse of the phrase.  :-D

Ben


---------------------------------------------------------------------
The official User-To-User support forum of the Apache HTTP Server Project.
See <URL:http://httpd.apache.org/userslist.html> for more info.
To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
   "   from the digest: users-digest-unsubscribe@httpd.apache.org
For additional commands, e-mail: users-help@httpd.apache.org


Re: [users@httpd] Re: Bug Versions 1.3.28/29 Fixed In 1.3.31 OrNot?

Posted by Purl Gurl <pu...@purlgurl.net>.
Ben Chabot wrote:
 
(snipped)

> It doesn't take 30k cisco machine to do the job.  As I've said, I
> believe snort or any number of things

Did I not "SNORT" in my article?

You need to pay attention. Your lack of attention, your lack
of comprehension of what is previously written, shows well.

Perhaps I need to lower my language level as I do for students,
but with great hesitation and annoyance.


> P.S. Kira, look up the definition of Ad Hominem arguments.  Seriously.
> It's embarassing.

Your comment is a classic example of Ad Hominem, easily
recognized by this English professor and flim flam artist.

Most ironic, yes?


Kira

---------------------------------------------------------------------
The official User-To-User support forum of the Apache HTTP Server Project.
See <URL:http://httpd.apache.org/userslist.html> for more info.
To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
   "   from the digest: users-digest-unsubscribe@httpd.apache.org
For additional commands, e-mail: users-help@httpd.apache.org


Re: [users@httpd] Re: Bug Versions 1.3.28/29 Fixed In 1.3.31 OrNot?

Posted by Purl Gurl <pu...@purlgurl.net>.
Ben Chabot wrote:

(snipped)

> > With SNORT, this WebDav exploit is fingerprinted using
> > a depth setting of eight characters and can actually be
> > fingerprinted in seven characters. Your SNORT reacts,
> > if you have your rule set for  react:block  and you never
> > see the exploit at all; the connection is dropped, this
> > is, you won't see it in an Apache log.
 
> Why don't you just do that then and quit complaining?

I have previously discussed SNORT. Pay attention
and stop complaining. Research, read and learn about
SNORT. Although an impressive bit of code, SNORT is
passive and may or may not block transactions along
with being highly platform dependent.

Do you have suggestions for a viable solution for this
lack of an ability to hook some request methods?

 
> > Using your logic, now SNORT is useless as are firmware
> > appliances which employ SNORT as an IDS.
 
> Is Apache an IDS?
 
Yes, very much so. Research, read and learn about Apache's
ability to filter incoming transactions then craft an
appropriate response. Apache has wonderful default features
and custom features allowing significant intrusion detection.

You will benefit by researching and reading about a nice
collection of Apache modules which are dedicated solely to
security needs.

Should you look around, should you research, should you
learn, you will discover I have been working on this
Apache WebDav bug for many months, through many different
sources, and just recently presented this problem here.

None of this is new to me. All of this is exceptionally
familiar to me. Specific to this topic, you are a newbie.
Nonetheless, even a newbie may offer a brilliant idea
no others considered. I am looking for solutions not
typical newsgroup acrimonious banter.


Kira

---------------------------------------------------------------------
The official User-To-User support forum of the Apache HTTP Server Project.
See <URL:http://httpd.apache.org/userslist.html> for more info.
To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
   "   from the digest: users-digest-unsubscribe@httpd.apache.org
For additional commands, e-mail: users-help@httpd.apache.org


RE: [users@httpd] Re: Bug Versions 1.3.28/29 Fixed In 1.3.31 OrNot?

Posted by Ben Chabot <vo...@amninc.net>.
> With SNORT, this WebDav exploit is fingerprinted using
> a depth setting of eight characters and can actually be
> fingerprinted in seven characters. Your SNORT reacts,
> if you have your rule set for  react:block  and you never
> see the exploit at all; the connection is dropped, this
> is, you won't see it in an Apache log.

Why don't you just do that then and quit complaining?
 
> Using your logic, now SNORT is useless as are firmware
> appliances which employ SNORT as an IDS.

Is Apache an IDS?


---------------------------------------------------------------------
The official User-To-User support forum of the Apache HTTP Server Project.
See <URL:http://httpd.apache.org/userslist.html> for more info.
To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
   "   from the digest: users-digest-unsubscribe@httpd.apache.org
For additional commands, e-mail: users-help@httpd.apache.org


Re: [users@httpd] Re: Bug Versions 1.3.28/29 Fixed In 1.3.31 OrNot?

Posted by Purl Gurl <pu...@purlgurl.net>.
Ben Chabot wrote:
 
> > It is not a matter of preventing logging. This is a matter of
> > logical "clean" logging.
 
> Logical logging is to log all connection attempts.

I did not state to not log connections nor hinted at this.

Please pay attention or resist this temptation to twist
my words into something I did not write.

I very clearly state, "...logical clean logging." Your
twisting of my words into what they are not, is deceit.

 
> > Check your internet resources for
> > an actual transcript of a WebDav exploit. It is thirty-thousand
> > to fifty-thousand bytes of repeating "binary" like code. That
> > garbage is of no value for later analysis. That garbage only
> > serves to bloat logfiles, to break log parsers, to annoy
> > and to lead me to rants.
 
> It _is_ of value for later analysis.  It's called NOPs and shellcode.
> And I assure you it is not just garbage.  Like I said, today it doesn't
> affect apache.  But something might at some point and you won't be
> logging it.  That will be amusing, trying to figure out what happened
> with no logs.
 
I did not state to not log connection requests. This is twice
now you have written this. This prompts me to hold an opinion
you are deliberately practicing deceit. That is inappropriate.

You are not thinking clearly. If a request method exceeds the
set URI length limit, Apache will return a 414 error and there
is absolutely nothing you can do about this. So, if a 414 error
is generated, no hack will be successful. However, your log file
is slobbered with kilobytes of garbage.

Yes, it is garbage. With a 414 response their is no need for
analysis, the data is useless; garbage. It may be of some
entertainment value, might disclose a new exploit but you
will never be able to address whatever is found; 414.
Once Apache cops a 414 error, you are out of the loop.

Doesn't matter if someone sends an extremely long secret
code to the location of Long John Silver's hidden treasure,
you are out of the loop; you cannot respond. Apache will not
allow you to respond.

So you discover a new exploit which turns your Linux
box into a Commodore. What are you going to do? Nada,
zippo, zero, nothing because Apache cops a 414.

Give thought to your words before writing.

With SNORT, this WebDav exploit is fingerprinted using
a depth setting of eight characters and can actually be
fingerprinted in seven characters. Your SNORT reacts,
if you have your rule set for  react:block  and you never
see the exploit at all; the connection is dropped, this
is, you won't see it in an Apache log.

Using your logic, now SNORT is useless as are firmware
appliances which employ SNORT as an IDS.

So which is it? Am I the blithering idiot for wanting
to capture WebDav, truncate the data and form a response
to deal with it or are high end technogeeks, like those
who developed SNORT or those who manufacture expensive
firewall appliances, are they idiots for not allowing
a capture of exploit data? SNORT and firmware do have
configuration settings for, no log, fast log, packet
log and many other options. You can choose to not log
at all or discard data. A serious blunder, you think?

Apache allows lots of nice parsing of incoming data
which does make it in. You can select to record all
data, disregard host name lookup, record or not record
referer [sic] data, almost anything you like.

So now Apache developers are the idiots for allowing
a user to discard data rather than log every bit of
it for analysis. Your logic is not good.

Your logic is not good because you are performing
a critique of me while deliberately ignoring what
I suggest and would like to do, is very popular
and incorporated by almost all professionals.

Why is this not ok for me but ok all others?

You are not thinking clearly. Not only are you resorting
to a tiresome tactic of word twisting, you are also making
an attempt to critique me for suggesting methods which
are precisely what well known commericial software writers
use most routinely.

So, if I am to be the idiot according to your logic,
then SNORT writers and high end software writers are
the idiots, as well.

What you are really doing is twisting my words around,
employing deceit, concealing known methods, using very
poor logic, to afford yourself a chance to critique.

I am here to share information, to learn, to make suggestions
which might help Apache become a better server.

Why are you here? A rhetorical question begging no answer.

I am very dismayed by this lack of professionalism displayed
by a select few here. I am dismayed because you select few
tend to ruin this mailing list, just as others ruin newsgroups
by engaging in the same or similar inappropriate behavior.

Some readers have shared valuable thoughts and input.
Consider not discouraging those few gentle and polite
participants from joining in, by personal attacks.

I do hope, you the reader, plural, will give thought
to my writings and assess if ad hominem behavior is
beneficial for this mailing list.

Moving back on topic, for those actually interested,
last night I looked at source code for 1.3.29 which is
significantly different than 1.3.27 version.

Within protocol.c for 1.3.27 version, I have discovered
potential for crafting a custom Apache server which
handles a 414 error quite differently. Version 1.3.27
affords a lot of code entry points for white hat hacks.

Changing the wording of a 414 response takes only a
minute, not counting compilation time and copying
in new compiled files.

There is also potential for changing the precedence
order of a 414 error, moving it into an allowed status
enabling an ability to capture WebDav, then work with
it and craft a custom response. A word of caution.
There is a need to defeat URI length to allow this.
Doesn't matter, the data is already in a buffer, it
is there so defeating URI length has no effect on
system resource usage.

A reader might find entertainment is looking at
http_protocol.c from line 2868 downward, or
"CHARSET_EBCDIC" downward, version 1.3.27 tarball.

There is lot of potential there for hooking using
Apache's core export feature. I do find a number
of entry points for direct module hooking, as well.


Kira

---------------------------------------------------------------------
The official User-To-User support forum of the Apache HTTP Server Project.
See <URL:http://httpd.apache.org/userslist.html> for more info.
To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
   "   from the digest: users-digest-unsubscribe@httpd.apache.org
For additional commands, e-mail: users-help@httpd.apache.org


RE: [users@httpd] Re: Bug Versions 1.3.28/29 Fixed In 1.3.31 OrNot?

Posted by Ben Chabot <vo...@amninc.net>.
> It is not a matter of preventing logging. This is a matter of
> logical "clean" logging. 

Logical logging is to log all connection attempts.

> Check your internet resources for
> an actual transcript of a WebDav exploit. It is thirty-thousand
> to fifty-thousand bytes of repeating "binary" like code. That
> garbage is of no value for later analysis. That garbage only
> serves to bloat logfiles, to break log parsers, to annoy
> and to lead me to rants.

It _is_ of value for later analysis.  It's called NOPs and shellcode.
And I assure you it is not just garbage.  Like I said, today it doesn't
affect apache.  But something might at some point and you won't be
logging it.  That will be amusing, trying to figure out what happened
with no logs.

> "SEARCH /\x90\x02\xb1\x02\xb1\x02\
> 
> However, you cannot prevent logging of the default eight-thousand
> bytes of garbage. You cannot send a method not allowed message.
> You cannot ip block offenders. You cannot do anything but eat it.
> 
> That is a bug.

I believe it's been posted at least 3 times how you could solve this, in
the way you are so obstinately ranting about.
 
> Yes, completely blocking logging is not a good idea. It is also
> not a good idea to allow eight-thousand bytes of garbage into
> your logs, without any control. 

It's called log filtering, there's your control.  Or rotating logs.
(Zipping them up periodically, and keeping a few back entries, deleting
the older ones.)

> Ya know, I could wipe out a server's disk storage in a matter
> of an hour or two, by sending WebDav at a rate of one-hundred
> per second, which would not trigger a DOS response.

You certainly could not.  You think you can send 100G of data in an
hour?  Not only that, like I said, most people rotate their logs, so
once it gets to X size, it is backed up, zipped and the log is cleared.
Once there's X many backups the oldest one is deleted.  So I find it
curious as to what your problem is.  I guess it's because windows
doesn't come with logrotate?  Heh.

> Should a script kiddie decide to wipe out your disk storage,
> what would you do? Nothing. You would eat it. That is what
> you would do; you are completely naked and defenseless, unless
> you have a thirty-thousand dollar Cisco firewall.

Or you log to another machine via syslogd.  Or you have any sort of
firewall.
It doesn't take 30k cisco machine to do the job.  As I've said, I
believe snort or any number of things, if upstream, could drop the
packets before they hit apache.  And most people would restore from
backup, if their data was lost, not that this is going to cause any data
loss whatsoever.

Man, it is time to leave this list. =)
Been fun folks... get me entertained for a day!
Later!
Ben

P.S. Kira, look up the definition of Ad Hominem arguments.  Seriously.
It's embarassing.


---------------------------------------------------------------------
The official User-To-User support forum of the Apache HTTP Server Project.
See <URL:http://httpd.apache.org/userslist.html> for more info.
To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
   "   from the digest: users-digest-unsubscribe@httpd.apache.org
For additional commands, e-mail: users-help@httpd.apache.org


Re: [users@httpd] Re: Bug Versions 1.3.28/29 Fixed In 1.3.31 OrNot?

Posted by Purl Gurl <pu...@purlgurl.net>.
Laura Vance wrote:

> I have an idea that should solve all problems.  (yeah, right. ;)  )

If your quip was only true! Many would grovel before you.

I like this idea you present. Your idea would be a benefit
for Apache servers.

 
> What I would propose is to allow a directive in the httpd.conf file that
> would be something like this:

> <methodLogging>
>     DENY SEARCH etc.
>     ALLOW ALL
> </methodLogging>

If you don't mind searching a newsgroup, rummage around in
alt.apache.configuration. You will discover a lot of people,
including me, tossing ideas back and forth trying to resolve
this request method / logging problem. No solutions but a lot
of great ideas. Well, some solutions. All are either expensive
or require adjunct software.

A solution tried is limiting the string length of an URI
as can be done with other request methods. Disallowed methods,
you cannot limit URI string length; you are garbage clobbered.

Another solution tried is much like your idea, use a limit container.

> or something like that to deny specific request logging and allow all
> the others.  Since it's been stated that request methods that are not
> configured don't actually get "processed", this would just keep them
> from showing up in the log.  I mean, if they're not processed, there's
> no risk of contamination of any kind, right?

A module to manipulate http response for specific request methods
would be viable. A module like this would be adaptable and afford
a wide range of options.
 
> With that being said, I personally have no reason to stop any methods
> from reaching my log, but who's to say that someone just doesn't care
> for it.

It is not a matter of preventing logging. This is a matter of
logical "clean" logging. Check your internet resources for
an actual transcript of a WebDav exploit. It is thirty-thousand
to fifty-thousand bytes of repeating "binary" like code. That
garbage is of no value for later analysis. That garbage only
serves to bloat logfiles, to break log parsers, to annoy
and to lead me to rants.

"SEARCH /\x90\x02\xb1\x02\xb1\x02\

I only need to see that much to know it is a WebDav exploit.
There is no need to look at the remaining default eight-thousand
bytes to realize what type of exploit this is.

However, you cannot prevent logging of the default eight-thousand
bytes of garbage. You cannot send a method not allowed message.
You cannot ip block offenders. You cannot do anything but eat it.

That is a bug.


Your method logging syntax is a good idea and I would support
this. It is a method similar to limit and limitexcept which
work well, sometimes, if a core hook is allowed.

A very simple solution is simply to allow string length control
as you can do with other request methods.

Yes, completely blocking logging is not a good idea. It is also
not a good idea to allow eight-thousand bytes of garbage into
your logs, without any control. 

Ya know, I could wipe out a server's disk storage in a matter
of an hour or two, by sending WebDav at a rate of one-hundred
per second, which would not trigger a DOS response.

Sure, some will argue the same could be done with post data,
for example. GET, yes, potential. Some are arguing this, 
most illogically. Those methods and others can be controlled,
especially by ip blocking. I would challenge any reader to
present a method to control WebDav before sunset here on
the left hand coast. 

Should a script kiddie decide to wipe out your disk storage,
what would you do? Nothing. You would eat it. That is what
you would do; you are completely naked and defenseless, unless
you have a thirty-thousand dollar Cisco firewall.

* SNORTS *

Got spare change?


Kira

---------------------------------------------------------------------
The official User-To-User support forum of the Apache HTTP Server Project.
See <URL:http://httpd.apache.org/userslist.html> for more info.
To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
   "   from the digest: users-digest-unsubscribe@httpd.apache.org
For additional commands, e-mail: users-help@httpd.apache.org


Re: [users@httpd] Re: Bug Versions 1.3.28/29 Fixed In 1.3.31 Or Not?

Posted by Laura Vance <va...@winfreeacademy.com>.
Hello,

I have an idea that should solve all problems.  (yeah, right. ;)  )

What I would propose is to allow a directive in the httpd.conf file that 
would be something like this:

<methodLogging>
    DENY SEARCH etc.
    ALLOW ALL
</methodLogging>

or something like that to deny specific request logging and allow all 
the others.  Since it's been stated that request methods that are not 
configured don't actually get "processed", this would just keep them 
from showing up in the log.  I mean, if they're not processed, there's 
no risk of contamination of any kind, right?

The reason I think this might help is that while most of us want to have 
our logs so that we can look back to before a problem happened to see 
what led up to it, others do not want this function.  Just as it's not 
one person's place to say what I want, it's not my place to say what 
they want either.

With that being said, I personally have no reason to stop any methods 
from reaching my log, but who's to say that someone just doesn't care 
for it.  I guess an example (if one is needed) is that you can tell 
someone that the paint is wet, but until they touch it, they don't know 
for sure.  One thing to think about is if someone does have their logs 
set to not log anything, then if they ask for help because someone 
hacked their server, the question could be "what's in your logs?"  If 
the response is "they were turned off" you can feel justified in saying 
"why weren't you logging?  we can't help you without logs."

Also just to clarify, I don't see detailed logs as a "bug", but the 
ability to select what you log would be more of a feature request.  
Isn't that partly why we love Linux and the open source movement... the 
"man" can't tell us what to do (or log as the case may be).

-- 
Thanks,
Laura Vance
Systems Engineer
Winfree Academy Charter Schools, Data-Business Office
1711 W. Irving Blvd. Ste 310
Irving, Tx  75061
Web: www.winfreeacademy.com



---------------------------------------------------------------------
The official User-To-User support forum of the Apache HTTP Server Project.
See <URL:http://httpd.apache.org/userslist.html> for more info.
To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
   "   from the digest: users-digest-unsubscribe@httpd.apache.org
For additional commands, e-mail: users-help@httpd.apache.org


Re: [users@httpd] Re: Bug Versions 1.3.28/29 Fixed In 1.3.31 Or Not?

Posted by Joshua Slive <jo...@slive.ca>.
On Mon, 17 May 2004, Tim Thorburn wrote:
> Ok, impartial observer here ... I'm on this list because I'm a web designer
> who uses Apache for hosting and local testing, not a sysadmin or someone
> who makes their living off of the goodness that is Apache.  So far, I'm
> seeing someone present a problem that she feels is a problem, and then be
> ignored or ridiculed for thinking this is a problem.

What you perhaps don't realize is that this person has made exactly the
same claims in several different forums.  Each time, someone has described
to her/him in detail why these claims are incorrect.  But she/he doesn't
seem to understand or accept the explanations and keeps making these false
claims.

Personally, I have not attempted to ridicule Kira.  I made one comment
where I pointed out the continued use of overgeneralizations from limited
experience.  Other than that, I have simply stated facts.

In general, people (including myself) are sometimes rude on technical
mailing lists, and this is something we should try to avoid.  But much
more often what happens is that people who don't understand the tone of a
technical mailing list will interpret a curt, factual response as a rude
response, when no such thing was intended.  You need to be very careful
reading tone into email.

Joshua.

---------------------------------------------------------------------
The official User-To-User support forum of the Apache HTTP Server Project.
See <URL:http://httpd.apache.org/userslist.html> for more info.
To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
   "   from the digest: users-digest-unsubscribe@httpd.apache.org
For additional commands, e-mail: users-help@httpd.apache.org


Re: [users@httpd] Re: Bug Versions 1.3.28/29 Fixed In 1.3.31Or Not?

Posted by Purl Gurl <pu...@purlgurl.net>.
Tim Thorburn wrote:

(snipped)

> Ok, impartial observer here ... I'm on this list because I'm a web designer
> who uses Apache for hosting and local testing, not a sysadmin or someone
> who makes their living off of the goodness that is Apache.  So far, I'm
> seeing someone present a problem that she feels is a problem, and then be
> ignored or ridiculed for thinking this is a problem.
 
> Personally, I've asked several questions on this list and other similar
> lists wherein those who know (or in many cases those who *think* they know)
> dismiss any question to their ways as absurd remarks from those who should
> not speak.  Now, I'll be the first to admit I'm far from an expert in many
> areas, but when a person is publicly chewed out as Kira has been in this
> case ... it imposes something of an elitist view over the entire Apache
> community - don't you dare ask a question lest we mock you for wasting our
> time in asking this question.
 
Very typical behavior you describe!

Many of us have been dealing with the less-than-educated for
literally decades, here on the net. Amuses me to know some of
us have been programming, have been involved with the net, for
more years than some are old.

Cabal Syndrome. Sadly there are those whose only life is a
mailing list, a newsgroup, a forum, programming, whatever.
Once involved, some develop exaggerated self-importance
and believe they are in total charge; a cabal boss.
This is sad because other realize those people truly
have no life, no outside interest, no potential to be
really successful in life, to really enjoy life.

I have two internet stalkers. One faced criminal charges
and restraining orders. Both have been stalking our family
since 1995, on the net, and in "real life." As I write this,
one of them is trying to figure out how to hack our server,
which delights me. This delights me because I am robbing him
of precious time out of his life, with no effort.

Same applies to mailing lists and forums like this. Some
will waste their time, and waste time of readers, through
satuation of their need to feel in control of others. They
would do better to learn to control themselves, not others.

Your thoughts are appreciated by many readers. Almost all
appreciate those who work at bringing logic, intelligence
and goodwill to forums like this.

Easy enough to ignore those who do not appreciate efforts
such as yours. Easy enough to pity those without a life.

Sometimes people mistake my firm but fair demeanor for
being abrasive. Some are not accustomed to those who
are assertive, yet dimplomatic. Some live a fantasy.

Eventually, some will realize these problems I present
are bugs, are problems and need to be addressed. In time,
viable solutions will be offered, after the cabal bosses
finish displaying their true colors, much to my personal
humor and personal entertainment.

Solutions will come forth. All will benefit. Cabal bosses
will be embarrassed. That's reality!


Kira

---------------------------------------------------------------------
The official User-To-User support forum of the Apache HTTP Server Project.
See <URL:http://httpd.apache.org/userslist.html> for more info.
To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
   "   from the digest: users-digest-unsubscribe@httpd.apache.org
For additional commands, e-mail: users-help@httpd.apache.org


Re: [users@httpd] Re: Bug Versions 1.3.28/29 Fixed In 1.3.31 Or Not?

Posted by Robert Andersson <ro...@profundis.nu>.
Tim Thorburn wrote:
> but when a person is publicly chewed out as Kira has been in this
> case ... it imposes something of an elitist view over the entire
> Apache community

The situation usually arise when someone propose a problem/question which is
either badly founded or illformed. This is then, initially kindly, pointed
out, and the original person takes it as an insult and starts to act
unreasonable; unwilling to listen, do not answer counter-questions, do not
take proven fallacies into account, etc. "We" are here to help (and learn
while doing it), and when someone refuse/ignores the help given, "we" get
annoyed.

The problem is: what are "we" to do in such situation? Ignore the person?
Not very nice. Start writing things "we" know are untrue, to make that
someone feel better? Probably not.

This I have observered in many hacker/technical forums. Whether the above
description applies to the current discussion, and to what extent, I do not
say, but leave that to each observer to judge.

Regards,
Robert Andersson


---------------------------------------------------------------------
The official User-To-User support forum of the Apache HTTP Server Project.
See <URL:http://httpd.apache.org/userslist.html> for more info.
To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
   "   from the digest: users-digest-unsubscribe@httpd.apache.org
For additional commands, e-mail: users-help@httpd.apache.org