Processing commands for cont...@bugs.debian.org:
severity 561477 wishlist
Bug #561477 [cacti] [security] must not RE-add /etc/apache2/conf.d/cacti.conf
link on upgrade
Severity set to 'wishlist' from 'grave'
retitle 561477 please improve the debconf question about web server
Bug #561477
severity 561477 wishlist
retitle 561477 please improve the debconf question about web server
configuration
thanks
On Thu, Jan 7, 2010 at 11:17 AM, Patrick Schoenfeld
schoenf...@debian.org wrote:
On Wed, Jan 06, 2010 at 05:44:28PM +0200, Teodor MICU wrote:
Ok, now I see that this is a way of
On Wed, Jan 06, 2010 at 05:44:28PM +0200, Teodor MICU wrote:
[please don't use -quiet as I didn't received the responses though I
want to contribute were I can]
2010/1/4 Patrick Schoenfeld schoenf...@debian.org:
I've noticed in the past that cacti RE-adds the symbolic link
Tags 561339 patch
thanks
Hi,
attached is a patch that changes behaviour of postinst so,
that symlink is only created on a fresh installation.
Feel free to use it, if you wish.
Best Regards,
Patrick
diff -u -Nur cacti-0.8.7e.bak/debian/cacti.postinst cacti-0.8.7e/debian/cacti.postinst
---
[please don't use -quiet as I didn't received the responses though I
want to contribute were I can]
2010/1/4 Patrick Schoenfeld schoenf...@debian.org:
I've noticed in the past that cacti RE-adds the symbolic link
conf.d/cacti.conf
on every upgrade even if the source file was *manually*
Tags 561477 moreinfo
I've noticed in the past that cacti RE-adds the symbolic link
conf.d/cacti.conf
on every upgrade even if the source file was *manually* removed by the
sysadmin.
This is done to restrict the access to 'cacti' on each virtual web site (the
default behaviour in Debian).
On Mon, Jan 4, 2010 at 17:35:59 +0100, Patrick Schoenfeld wrote:
I still believe that a check should be added for the symlink. If it
was removed, don't RE-add it, it the source conf file
/etc/cacti/apache.conf doesn't exist remove the broken symlink.
How is this supposed to work? There
On Mon, Jan 04, 2010 at 04:50:05PM +, Julien Cristau wrote:
On Mon, Jan 4, 2010 at 17:35:59 +0100, Patrick Schoenfeld wrote:
I still believe that a check should be added for the symlink. If it
was removed, don't RE-add it, it the source conf file
/etc/cacti/apache.conf doesn't
Package: cacti
Version: 0.8.7e-1.1
Severity: grave
Tags: security
Justification: user security hole
I've noticed in the past that cacti RE-adds the symbolic link conf.d/cacti.conf
on every upgrade even if the source file was *manually* removed by the sysadmin.
This is done to restrict the access
On Thu, 17 Dec 2009 16:13:36 +0200, Teodor wrote:
Package: cacti
Version: 0.8.7e-1.1
Severity: grave
Tags: security
Justification: user security hole
I've noticed in the past that cacti RE-adds the symbolic link
conf.d/cacti.conf
on every upgrade even if the source file was *manually*
On Thu, Dec 17, 2009 at 5:51 PM, Michael Gilbert
michael.s.gilb...@gmail.com wrote:
On Thu, 17 Dec 2009 16:13:36 +0200, Teodor wrote:
As it can be seen postinstall already has a check for the existence of the
config
file /etc/cacti/apache.conf. Please add the same check for creating the
11 matches
Mail list logo
