www-apache-bugdb mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Mike D <blofi...@earthlink.net>
Subject config/9090: custom layout enduces charg entire system!
Date Thu, 06 Dec 2001 00:51:58 GMT

>Number:         9090
>Category:       config
>Synopsis:       custom layout enduces charg entire system!
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    apache
>State:          open
>Quarter:        
>Keywords:       
>Date-Required:
>Class:          sw-bug
>Submitter-Id:   apache
>Arrival-Date:   Wed Dec 12 12:40:11 PST 2001
>Closed-Date:
>Last-Modified:
>Originator:     blofishy@earthlink.net
>Release:        1.3.22
>Organization:
apache
>Environment:
There is a serious bug in the apache 1.3.22 configuration when using a custom LAYOUT in which
the documentation for some reason installs into the /
directory and then proceeds to charg the entire system.
>Description:
here is a layout I have used for years now to cause a problem
where the documentation will for some reason install in root directory /
and then proceed to charg the entire system and basically can destroy a servers security

<Layout MyNetwork>
    prefix:        /usr/local
    exec_prefix:   $prefix
    bindir:        $exec_prefix/bin
    sbindir:       $bindir
    libexecdir:    $exec_prefix/libexec
    datadir:       $prefix/www
    iconsdir:      $datadir/icons
    htdocsdir:     $datadir/htdocs
    cgidir:        $datadir/cgi-bin
    mandir:        $prefix/man
    includedir:    $prefix/include/apache-1.3
    localstatedir: $prefix/www/server
    sysconfdir:    $prefix/www/server/conf
    runtimedir:    $prefix/www/server/logs
    logfiledir:    $prefix/www/server/logs
    proxycachedir: $prefix/www/server/proxy
</Layout>
>How-To-Repeat:
runing make install with above layout
>Fix:
havnt had time to debug really, sorry
>Release-Note:
>Audit-Trail:
>Unformatted:
 [In order for any reply to be added to the PR database, you need]
 [to include <apbugs@Apache.Org> in the Cc line and make sure the]
 [subject line starts with the report component and number, with ]
 [or without any 'Re:' prefixes (such as "general/1098:" or      ]
 ["Re: general/1098:").  If the subject doesn't match this       ]
 [pattern, your message will be misfiled and ignored.  The       ]
 ["apbugs" address is not added to the Cc line of messages from  ]
 [the database automatically because of the potential for mail   ]
 [loops.  If you do not include this Cc, your reply may be ig-   ]
 [nored unless you are responding to an explicit request from a  ]
 [developer.  Reply only with text; DO NOT SEND ATTACHMENTS!     ]
 
 


Mime
View raw message