On Sat Mar 02, 2002 at 10:55:55PM -0800, David Walser wrote: > No, not for me it's not that hard to turn on, but I > remember the first time I used Apache, RH 5.2 days. > All I had to do was install it, and it was fully > functional, it was great! I didn't know anything > about web servers at the time, I didn't know it would > be that easy (thought I would have to configure it and > stuff, not that that'd be too bad, I was configuring > samba by hand back then). Now think about a total > newbie. They install Mandrake, and Apache, and it's > not functional. What to do? You even have to find > the options in commonhttpd.conf which isn't even a > standard thing. Sure it wasn't that *hard* for *me* > to do, but it still took a while to figure it out.
What are you talking about? Enabling Indexes by default somehow makes Apache work whereas having it off by default doesn't? Apache works just *fine* without Indexes. And because it is, potentially, a security hole (through inappropriate disclosure), the end user should be forced to enable it where appropriate... which is exactly the case. This has absolutely nothing to do with whether apache works or not "out of the box". -- MandrakeSoft Security; http://www.mandrakesecure.net/ "lynx -source http://www.freezer-burn.org/bios/vdanen.gpg | gpg --import" 1024D/FE6F2AFD 88D8 0D23 8D4B 3407 5BD7 66F9 2043 D0E5 FE6F 2AFD Current Linux kernel 2.4.8-34.1mdk uptime: 40 days 19 hours 16 minutes.
msg58358/pgp00000.pgp
Description: PGP signature
