Bug 64199 - Log-files are placed under WorkDir which in default install is readable from a remote browser
Summary: Log-files are placed under WorkDir which in default install is readable from ...
Keywords:
Status: CLOSED DUPLICATE of bug 112888
Alias: None
Product: Red Hat Raw Hide
Classification: Retired
Component: mrtg
Version: 1.0
Hardware: i386
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Miloslav Trmač
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks: 67218 79579 CambridgeTarget
TreeView+ depends on / blocked
 
Reported: 2002-04-28 22:53 UTC by John Eckerdal
Modified: 2007-04-18 16:42 UTC (History)
0 users

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2006-02-21 18:48:48 UTC
Embargoed:


Attachments (Terms of Use)

Description John Eckerdal 2002-04-28 22:53:51 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i586; en-US; rv:0.9.9) Gecko/20020408

Description of problem:
The standard WorkDir location are used to store both the result and the
log-files generated by MRTG. The raw log-files can then later be downloaded from
any browser that can access the http://server/mrtg directory.
While not a security issue since the result is viewable in graphs it would look
cleaner if the logs were placed in /var/logs/mrtg instead since if MRTG
generates graphs for stacked switch there will be two files per connected
computer just for the logs.
And since there is a /var/logs/ present why not just add a /var/logs/mrtg and be
done with it?

From the MRTG reference:

LogDir

LogDir specifies the directory where the logs are stored. This need not be under
htmldir directive.

Example:
Logdir: /www/mrtg/logs



Version-Release number of selected component (if applicable):


How reproducible:
Always

Steps to Reproduce:
1.Install MRTG
2.Watch where the log-files are placed (/var/www/html/mrtg/)
3.
	

Actual Results:  Log files are placed in /var/www/html/mrtg/

Expected Results:  Log files are placed in /var/www/html/mrtg/

Additional info:

Comment 1 Miloslav Trmač 2004-08-16 20:40:35 UTC

*** This bug has been marked as a duplicate of 112888 ***

Comment 2 Red Hat Bugzilla 2006-02-21 18:48:48 UTC
Changed to 'CLOSED' state since 'RESOLVED' has been deprecated.


Note You need to log in before you can comment on or make changes to this bug.