Axel Beckert wrote:
> Point taken. Will move that line (or an "fwsnort --ipt-flush") into a
> (to be created) prerm and do another QA upload. (Unless you're already
> onto it. Feel free to do that.)
Unfortunately "fwsnort --ipt-flush" only flushes the chains but does
not remove the chains:
#
Control: tag -1 + confirmed - moreinfo
Hi Adrian,
Adrian Bunk wrote:
> > > Tags: security
> >
> > I also disagree with this tag.
>
> messing up the iptables setup at an unexpected time can have bad
> consequences.
bad != security
> > > A case could be made for "fwsnort --ipt-flush" in
Control: severity -1 serious
On Sat, May 13, 2017 at 07:27:27PM +0200, Axel Beckert wrote:
> Control: tag -1 + moreinfo
> Control: severity -1 important
>
> Hi Adrian,
Hi Axel,
> Adrian Bunk wrote:
> > Severity: critical
>
> I think that's overly exaggerated.
>
> > Tags: security
>
> I also
Control: tag -1 + moreinfo
Control: severity -1 important
Hi Adrian,
Adrian Bunk wrote:
> Severity: critical
I think that's overly exaggerated.
> Tags: security
I also disagree with this tag.
> The #861999 fix adds the following on purging:
> grep -v FWSNORT /var/lib/fwsnort/fwsnort.save |
Package: fwsnort
Version: 1.6.5-3
Severity: critical
Tags: security
The #861999 fix adds the following on purging:
grep -v FWSNORT /var/lib/fwsnort/fwsnort.save | iptables-restore
Imagine the following:
1. today I install fwsnort and try it
2. later today I uninstall it
3. 2 years later I
5 matches
Mail list logo
