Steve Langasek wrote:
severity 340699 important
thanks
On Fri, Nov 25, 2005 at 10:26:43AM +0100, Johannes Wiedersich wrote:
Subject: firestarter breaks nis
Package: firestarter
Version: 1.0.3-1.1
Severity: critical
Justification: breaks unrelated software
Firestarter is a firewalling tool; nis is a network application. These are
not unrelated software.
Given that you can break *any* network application by means of a
misconfigured firewall, and given that your stated solution for this bug was
to make a change to your *nis* config, not to your firestarter config, I
don't see any reason to treat this as a grave bug, either.
This is a workaround, not a solution.
In fact installation/start of firestarter breaks an otherwise working
configuration in nis. The really annoying part of the problem is that no
hints of what gets wrong is displayed by firestarter; no events etc.
The firewall is set up correctly, allowing all connections to the
desired private network. I would prefer to change the configuration via
firestarter, not nis. How should one set up firestarter to allow
broadcassting to 192.168.0.255 for a nis server apart from allowing all
connections to and from 192.168.0.0/24?
To sum it up: the firewall is configured correctly, shows no logs and
nevertheless another application is broken. Problems like this are
extremely difficult to track down for system administrators. I think
this justifies asking for an update of sarge.
Thanks for your quick reply and help.
Johannes
NB: According to reportbug:
breaks unrelated software: breaks unrelated software on the system
(packages that have a dependency relationship are not unrelated)
I used this definition of 'unrelated'. Sorry if this was wrong.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
