Bug#709566: RM request

firestarter has been dead upstream for a long time and there appears to be no-one taking over/continuing development. Please remove this package from the archive. Last upstream release - 1.0.3 (2005) http://www.fs-security.com/ Thanks and regards, Paul Cupis -- To UNSUBSCRIBE, email to

Bug#671769: Traffic validation

fixed 671769 1.0.3-9 thanks On 13/05/12 18:20, Mika wrote: I did some testing on the parameters and I found out that if I disable blocking for reserved addresses in the traffic validation section of advanced firewall options I can load https://discussions.apple.com normally. However, as far as I

Bug#615176: firestarter: broken on 2.6.37

On 01/03/11 09:53, QuadCEM wrote: > I upgraded to firestarter 1.0.3-10 and to kernel 2.6.37-2 this afternoon > and it seems to be back to normal now ... did you already release a fix > for this, or did something in the kernel update take care of it? The -10 version doesn't do anything regarding wh

Bug#615176: firestarter: broken on 2.6.37

On 27/02/11 23:57, QuadCEM wrote: > I have attached the iptables output; it seems to be setting rules, but > iptables is still allowing all inbound traffic to connect to the machine > (even non-established traffic). I think the "ACCEPT all -- > 0.0.0.0/00.0.0.0/0" is trumping all

Bug#615176: firestarter: broken on 2.6.37

On 26/02/11 12:57, Charles Munson wrote: > Actually I take that back ... the firewall doesn't appear to be working at > all for incoming connections anymore. Even in restrictive mode connections > to my services can still be made. Maybe the priority should be raised to > critical rather than norm

Bug#615264: firestarter creates dchpd.conf at wrong place

On 26/02/11 15:33, Denis Prost wrote: > Package: firestarter > Version: 1.0.3-8 > Severity: important > > isc-dhcp-server seems to look at /etc/dhcp/dhcpd.conf while firestarter > creates > dhcpd.conf in /etc when it is configured to act as a gateway/dhcp server. > So, though dhcp is configured th

Bug#542224: Broken in version 1.0.3-8 (Device not found)

I believe this was fixed by patch 21 in firestarter version 1.0.3-9. Are you able to test/confirm, please? Regards, -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#560967: #560967 firestarter: warning message when restarting firewall

I'm not able to reproduce this on Debian Squeeze with iptables 1.4.8-3. Is this still occuring on your system? -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#599524: quagga: init script should support defaults file

On Fri, Oct 08, 2010 at 02:09:47PM +0200, Marc Haber wrote: > Package: quagga > Version: 0.99.17-2 > Severity: wishlist > > My sites are probably not the only site that only wants to run a small > selection of the quagga daemons (here: bgpd only). To achive this, one > needs to edit the init scrip

Bug#542224: Broken in version 1.0.3-8 (Device not found)

Anthony Mutiso wrote: On doing a reinstall again, the two variables where null and firestart wound not start an my iptables rule set was empty. To confirm, after having a fixed configuration, with the GUI not running, you did: apt-get install --reinstall firestarter and the configuration br

Bug#517424: firestarter: Doesn't start: "A proper configuration for Firestarter was not found"

David wrote: Package: firestarter Version: 1.0.3-7 Severity: grave Justification: renders package unusable This has happened to me in two different computers running sid, so I assume that "grave" is the correct severity. The problem started IIRC on Monday 23 Feb 2009, so it may come from an upg

Bug#495232: Please unblock 0.99.11-1

On Thu, Nov 20, 2008 at 06:20:22PM +0100, Friedemann Stoyan wrote: > I run into the same trouble, quagga 0.99.10-1 is completely unusable for > me. I compiled quagga source 0.99.11-1 from unstable for lenny. This > version fixes the bug. Please unblock quagga 0.99.11-1. Upstream are considering

Bug#389591: Freeswitch debian package

Hi, FreeSWITCH v1.0 was released recently. Is there any progress in packaging it, please? Do you have an WIP pacakges to be tested? I notice that upstream has a debian/ directory and they give instructions to build a package at

Bug#460740: firestarter: please reopen #439852 (when I click on "Firestarter homepage", icedove appears)

giggz wrote: I opened this bug some months ago. And I still have this problem. You answer me, that firestarter use the app selected to open text/html. But my problem is that both icedove and iceweasel are mimetype for text/html. And icedove is used I don't know why (it's the first alphabetiquely)

Bug#443742: linux-2.6: Please enable CONFIG_TCP_MD5SIG

Package: linux-2.6 Severity: wishlist Please enable CONFIG_TCP_MD5SIG in future versions of the kernel. This option was added to the kernel a couple of versions back and is required for people using MD5 TCP signatures to help protect BGP sessions. -- System Information: Debian Release: lenny/sid

Bug#267934: firestarter runlevel

Package: firestarter Followup-For: Bug #267934 Current versions of the firestarter package start the firewall script at runlevel 20, but they will also start firestarters filewall rules with pppd and ifupdown. -- System Information: Debian Release: lenny/sid APT prefers testing APT policy: (5

Bug#436036: O: eagle-usb -- Data for Eagle USB ADSL modems

Package: wnpp Severity: normal I intend to orphan the eagle-usb package. The package description is: This package provides the DSP code needed to use the USB ADSL modems featuring the Eagle chipset. This includes the Sagem [EMAIL PROTECTED] 800 modem. The code is no longer supported upstream

Bug#416553: firestarter: More IANA assignments

Package: firestarter Version: 1.0.3-2 Followup-For: Bug #416553 Please update the non-routables file to reflect the recent allocation of 94/8 and 95/8 to RIPE NCC. -- System Information: Debian Release: lenny/sid APT prefers testing APT policy: (500, 'testing'), (400, 'stable'), (200, 'unstab

Bug#333248: libnet-ssh-perl depends on transitional ssh package

Is there any ETA to getting this bug resolved, please? Regards, -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#422703: file-roller: Recommends dummy package mkisofs instead of genisoimage

Package: file-roller Version: 2.18.2-1 Severity: minor file-roller recommends the package mkisofs, but this has been replaced with genisoimage and the mkisofs package is just a dummy transition packages. The recommends should be updated. Packages: mkisofs Description: Dummy transition package for

Bug#377816: closed by [EMAIL PROTECTED] (Paul Cupis) (#377816 Recommends unavailable eagle-usb-modules)

Luk Claes wrote: I do not believe this is a bug as the recommended packages is provided by the module source once it is built/installed on the local machine. According to Debian Policy packages in main should only have packages from main in Depends and Recommends. So it is a bug and there are t

Bug#418156: /var/run/l2tpns/acct not created by package

Package: l2tpns Version: 2.1.21-1 Severity: normal The default configuration of the l2tpns package contains: set accounting_dir "/var/run/l2tpns/acct" however this directory is not created by the package or the maintenance scripts - by default, therefore, l2tpns will complain about not being abl

Bug#338550: firestarter: Broken remove; Again

Michael Pobega wrote: On Sun, Apr 01, 2007 at 09:05:54PM +0100, Paul Cupis wrote: On Wed, Mar 28, 2007 at 09:40:06PM -0400, Michael Pobega wrote: Package: firestarter Version: 1.0.3-1.3 Followup-For: Bug #338550 It seems that the Etch package for Firestart is indeed broken, because it

Bug#338550: firestarter: Broken remove; Again

On Wed, Mar 28, 2007 at 09:40:06PM -0400, Michael Pobega wrote: > Package: firestarter > Version: 1.0.3-1.3 > Followup-For: Bug #338550 > > It seems that the Etch package for Firestart is indeed broken, because > it happened to me on my system. I just apt-pinned it from unstable > into testing, an

Bug#416553: firestarter: Update non-routables

Package: firestarter Version: 1.0.3-2 Severity: normal Please update the non-routables file to reflect the recent allocation of 92/8 and 93/8 to RIPE NCC. -- System Information: Debian Release: 4.0 APT prefers testing APT policy: (500, 'testing'), (200, 'unstable') Architecture: i386 (i686) S

Bug#288772: #288772 firestarter: Corrupts /etc/resolv.conf at DHCP renewal time

Could anyone affected by this bug please check to see if version 1.0.3-2, recently uploaded to unstable, resolves it, please? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#414007: firestarter: Add support for LSB init functions

Package: firestarter Version: 1.0.3-2 Severity: wishlist Tags: patch Please find attached a patch which uses LSB init-functions in the firestarter init script. -- System Information: Debian Release: 4.0 APT prefers testing APT policy: (500, 'testing'), (200, 'unstable') Architecture: i386 (i

Bug#414000: firestarter: desktop file is in wrong location - does not show on menu

Package: firestarter Version: 1.0.3-2 Severity: normal The firestarter package includes a .desktop file to include the program in the GUI menu system. The current package installs this file to /usr/share/gnome/apps/Internet/firestarter.desktop but the file should be installed to /usr/share/applica

Bug#338550: #338550

On Mon, Mar 05, 2007 at 09:44:58AM +0100, Michel BRIAND wrote: > Le Sun, 4 Mar 2007 00:02:42 +, > [EMAIL PROTECTED] (Paul Cupis) a écrit : > > > > Re: #338550 firestarter: remove problem > > > > I cannot reproduce this on Etch with firestarter package versio

Bug#323192: Tag upstream

tags 323192 + upstream thanks This is an upstream bug - feature request for configuring Netfilter/syslog options. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#407331: Patch for outdated BOGONS list

:28.0 + @@ -1,3 +1,12 @@ +firestarter (1.0.3-1.4) unstable; urgency=low + + * Non-maintainer upload. + * Update non-routables file to reflect changes in BOGON space. +Data from http://www.cymru.com/Documents/bogon-bn-agg.txt +(closes: #407331) + + -- Paul Cupis <[EMAIL PROTECTED]> S

Bug#258064: gnome-ppp and resolvconf

Package: gnome-ppp Followup-For: Bug #258064 Has there been any progress since 2004 which might allow gnome-ppp and resolvconf to co-exist on a Debian system, please? Regards, -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#377816: eagle-usb-data: Recommends eagle-usb-modules

Package: eagle-usb-data Followup-For: Bug #377816 Luk Clases wrote: > Package: eagle-usb-data > Severity: important > Version: 2.1.1-2 > > Your package recommends eagle-usb-modules which is not available in > unstable (anymore). eagle-usb-modules is Provide'd by eagle-usb-modules-`uname -r` which

Bug#404359: masqmail: postinst uses deprecated syntax for "tail"

Package: masqmail Version: 0.2.21-1.2 Severity: minor masqmail uses "tail +number" syntax in postinst, which is now deprecated by coreutils package. $ sudo dpkg-reconfigure -phigh masqmail Stopping MTA (masqmail): listen/queue. tail: Warning: "+number" syntax is deprecated, please use "-n +numbe

Bug#396261: Incompatible debian sarge's firewall frontends leave net unprotected

Antonio R. wrote: > Package: guarddog > Version: 2.4.0-1 > > After I install and configure guarddog firewall, if > firestarter 1.0.3-1.1 is installed and executed (to > add a simple desktop sniffer) then guarddog's firewall > rules are invalid. Once firestarter is closed ports > are unprotecte

Bug#391674: /sbin/fixfiles: bash-ism in /sbin/fixfiles

Package: policycoreutils Version: 1.30.29-1 Severity: normal File: /sbin/fixfiles /sbin/fixfiles contains a bash-ism (let foo=bar) on lines 213 and 230, but states /bin/sh in it's #! line. Changing the first line to /bin/bash resolves this and allows you to run fixfiles on a system where /bin/sh

Bug#366519: guarddog: doesn't work with zeroconf (avahi)

Matej Cepl wrote: > Package: guarddog > Version: 2.5.0-1 > Severity: normal > > Even with the attached rc.firewall customized to allow mDNS, > guarddog generated /etc/rc.firewall blocks port 5353. If you create a user-defined protocol with guarddog, it will allow the specified ports to be used to

Bug#367618: [PATCH] Re: #367618: libexpect5.43.so: cannot open shared object file: No such file or directory

[EMAIL PROTECTED] wrote: > On Sat, May 20, 2006 at 09:09:22AM +0100, Paul Cupis wrote: >> tag 367618 + patch >> thanks >> >> Please find attached my patch which moves libexpect5.43.so back into the >> expect package. >> >> expect-dev Depends on e

Bug#367618: [PATCH] Re: #367618: libexpect5.43.so: cannot open shared object file: No such file or directory

on expect, so 367325 is still fixed. + + -- Paul Cupis <[EMAIL PROTECTED]> Fri, 19 May 2006 20:12:02 +0100 + expect (5.43.0-3) unstable; urgency=high * Applied patch from Alec Berryman, fixing a symlink error. diff -Naur expect-5.43.0-orig/debian/expect-dev.files expect-5.43.0/debian/

Bug#366519: guarddog: doesn't work with zeroconf (avahi)

Matej Cepl wrote: > Package: guarddog > Version: 2.5.0-1 > Severity: normal > > Even with the attached rc.firewall customized to allow mDNS, > guarddog generated /etc/rc.firewall blocks port 5353. Are you modifying the rc.firewall by hand and then re-running it? This will not work, you have to us

Bug#355582: should be "arch: all"

Martin Michlmayr wrote: > Package: doctorj > Version: 5.0.0-2 > Severity: minor > > This package is "arch: any" but it doesn't (afaik) include any > architecture specific code, so it should be "arch: all". After all, > there's only a .jar file and this is supposed to be platform > independent, is

Bug#357338: guarddog active even after "--purge remove"

l which specifies how iptables/ipchains is configured. Regards, Paul Cupis -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#357338: guarddog: Submitter using non-existant email address

Package: guarddog Version: 2.5.0-1 Followup-For: Bug #357338 <[EMAIL PROTECTED]>: host mx1.mail.yahoo.com[4.79.181.14] said: 554 delivery error: dd This user doesn't have a yahoo.com account ([EMAIL PROTECTED]) [0] - mta203.mail.mud.yahoo.com (in reply to end of DATA command) Final-R

Bug#322252: app_dtmftotext.so still fails to load in asterisk-spandsp-plugins 0.0.20050227-1

Wolfgang Alper wrote: > Package: asterisk-app-dtmftotext > Version: 0.0.20050227-1 > > It seems that bug #305624 still exists in the package > asterisk-app-dtmftotext. I thought I'd fixed that with 0.0.20050203-2.1. Patch attached. diff -Naur asterisk-spandsp-plugins.orig/app_dtmftotext.c asteri

Bug#305624: Patch and NMU

.0.20050203-2.1) unstable; urgency=low + + * Replace gethostbyname in app_dtmftotext.c with ast_gethostbyname +as the former is not re-entrant. (closes: #305624) + + -- Paul Cupis <[EMAIL PROTECTED]> Sun, 8 May 2005 11:12:58 +0100 + asterisk-spandsp-plugins (0.0.20050203-2) unstable;

Bug#302862: DSA-177 links to wrong advisory

://lists.debian.org/debian-security-announce/debian-security-announce-2002/msg00101.html not http://lists.debian.org/debian-security-announce/debian-security-announce-2002/msg00100.html Regards, Paul Cupis [EMAIL PROTECTED] -- System Information: Debian Release: 3.1 APT prefers unstable APT policy: (910

Bug#299012: [GD-user] Guarddog is limited to TCP and UDP protocols

> Since using Guarddog on my WLAN I found the following in my syslog: > > Mar 10 21:16:05 kernel: DROPPED IN=ath0 OUT= MAC= > SRC=192.168.37.254 DST=224.0.0.1 LEN=32 TOS=0x00 PREC=0x00 TTL=1 > ID=1556 OPT (9404) PROTO=2 > > Per /etc/protocols PROTO 2 is IGMP, however when attempting to > confi