xplc is marked for autoremoval from testing

2017-05-13 Thread Debian testing autoremoval watch
xplc 0.3.13-6 is marked for autoremoval from testing on 2017-06-13 It is affected by these RC bugs: 858178: uuidcdef: buffer overflow

wvstreams is marked for autoremoval from testing

2017-05-13 Thread Debian testing autoremoval watch
wvstreams 4.6.1-11 is marked for autoremoval from testing on 2017-06-13 It (build-)depends on packages with these RC bugs: 858178: uuidcdef: buffer overflow

gnome-ppp is marked for autoremoval from testing

2017-05-13 Thread Debian testing autoremoval watch
gnome-ppp 0.3.23-2 is marked for autoremoval from testing on 2017-06-13 It (build-)depends on packages with these RC bugs: 858178: uuidcdef: buffer overflow

Bug#862485: fwsnort mustn't set iptables rules when purged

2017-05-13 Thread Axel Beckert
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

Processed: Re: Bug#862485: fwsnort mustn't set iptables rules when purged

2017-05-13 Thread Debian Bug Tracking System
Processing control commands: > tag -1 + confirmed - moreinfo Bug #862485 [fwsnort] fwsnort mustn't set iptables rules when purged Added tag(s) confirmed. Bug #862485 [fwsnort] fwsnort mustn't set iptables rules when purged Removed tag(s) moreinfo. -- 862485:

Processed: Package is completely broken

2017-05-13 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > severity 858178 serious Bug #858178 [uuidcdef] uuidcdef: buffer overflow Severity set to 'serious' from 'normal' > thanks Stopping processing here. Please contact me if you need assistance. -- 858178:

Processed: Re: Bug#862485: fwsnort mustn't set iptables rules when purged

2017-05-13 Thread Debian Bug Tracking System
Processing control commands: > severity -1 serious Bug #862485 [fwsnort] fwsnort mustn't set iptables rules when purged Severity set to 'serious' from 'important' -- 862485: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=862485 Debian Bug Tracking System Contact ow...@bugs.debian.org with

Bug#862485: fwsnort mustn't set iptables rules when purged

2017-05-13 Thread Adrian Bunk
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

Bug#862485: fwsnort mustn't set iptables rules when purged

2017-05-13 Thread Axel Beckert
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 |

Processed: Re: Bug#862485: fwsnort mustn't set iptables rules when purged

2017-05-13 Thread Debian Bug Tracking System
Processing control commands: > tag -1 + moreinfo Bug #862485 [fwsnort] fwsnort mustn't set iptables rules when purged Added tag(s) moreinfo. > severity -1 important Bug #862485 [fwsnort] fwsnort mustn't set iptables rules when purged Severity set to 'important' from 'critical' -- 862485:

Bug#862485: fwsnort mustn't set iptables rules when purged

2017-05-13 Thread Adrian Bunk
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