2012/5/10 Jari Aalto :
> I'm planning to NMU with changes listed in previous mail's patch to help
> migrate away from deprecated dpatch.
>
> Please let me know if an update is alredy being worked on, or if the
> previous patch needs adjustments, or if there is anything that should
> delay the NMU.
Package: wnpp
Severity: normal
I am no longer a user of this software and bug #358058 won't be fixed
upstream (the software doesn't seem to be maintained anymore).
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas..
On 11/03/2010 12:48, Jan Hauke Rahm wrote:
Package: wmnetload
Version: 1.3-1.1
Severity: important
User: debian...@lists.debian.org
Usertags: proposed-orphan
Dear Lorenzo,
while reviewing some packages, your package came up as a package that
should maybe be orphaned by its maintainer. You have
Rogério Brito ha scritto:
> Hi again,
>
> On Apr 09 2009, Rogério Brito wrote:
>> On May 27 2008, Alexandre Lymberopoulos wrote:
>>> The program causes a segmentation fault when X starts and the device
>>> to be monitored is not up. When the monitored device is up wmnetload
>>> seems to work perfe
On 7/12/07, Matthew King <[EMAIL PROTECTED]> wrote:
> Here's a better patch which can include directories in locations other
> than /etc/shorewall
Thank you. I'll update the package as soon as possible.
-- lm
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Troubl
On 6/16/07, Michael Prokop <[EMAIL PROTECTED]> wrote:
* Michael Prokop <[EMAIL PROTECTED]> [20070501 10:15]:
[...]
Any chance to get an answer?
The problem will be fixed by the next upload.
-- l
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact
Package: xfce4-genmon-plugin
Version: 3.1-1
Severity: normal
--- Please enter the report below this line. ---
The process spawned when the icon plugin is left clicked remains zombie
because the plugin process does not wait for the termination of the child.
As a workaround the following patch can
Geoffrey L. Brimhall wrote:
> Package: splashy
> Version: 0.3.2
> Severity: important
>
> There is a race condition between when splashy ends and gdm starts that
> happens on my system about 1 in 3 boots, when it happens the splashy
> screen is just "hangs" and console switching to X doesn't work.
Ted Merrill wrote:
> Package: shorewall
> Version: 3.2.9-1
> Severity: normal
>
>
> The latest debian unstable shorewall release, shorewall 3.2.9-1,
> incorrectly
> modifies some SIP packets during network address translation, thereby
> causing
> all subsequent voice packets to be lost.
> Actuall
Jeffrey B. Green wrote:
> Good. It's always a real pain if the bug cannot be reproduced.
>
> Here the info on ulogd:
>
> ii ulogd 1.23-6The Netfilter
> Userspace Logging Daemon
This is the bogus version. The bug against ulogd has a
Jeffrey B. Green wrote:
> Package: shorewall
> Version: 3.2.6-2
> Severity: wishlist
>
> The packets being written to the ulogd log file have only the following
> for the MAC address information:
>
> MAC=00
>
> i.e. only the two digits 00. This problems shows up in the logs on Feb 9
> (to narrow
Jacobo Tarrio wrote:
> Package: shorewall
> Severity: wishlist
> Tags: l10n patch
>
> It is attached to this report.
Thanks. It will be included in the next revision of the package.
-- lm
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL P
Aurélien Le Provost - Ribaltchenko wrote:
> Package: shorewall
> Version: 3.2.6-2
> Severity: important
>
> Hi.
>
> Since I upgraded my server from sarge to etch, I noticed that NAT
> (masquerade) rules are lost after a reboot.
>
> I have this line in /etc/shorewall/masq :
> eth0eth2
Paul Gear wrote:
> Aurélien Le Provost - Ribaltchenko wrote:
>> Package: shorewall
>> Version: 3.2.6-2
>> Severity: minor
>>
>> Hi,
>>
>> In /etc/shorewall/shorewall.conf I have
>> VERBOSITY=0
>> because I don't want my console spamed by shorewall. But it has no effect...
>> Don't know why.
>
> Th
Jeffrey B. Green wrote:
> Package: shorewall
> Version: 3.2.6-2
> Severity: wishlist
>
> The packets being written to the ulogd log file have only the following
> for the MAC address information:
>
> MAC=00
>
> i.e. only the two digits 00. This problems shows up in the logs on Feb 9
> (to narrow
Flavio Visentin wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Tom Eastep contacted me and gave me the solution.
To meke this configuration work it's enough to specify the option
"routeback" on the interface definition, like the following:
/etc/shorewall/interfaces
#ZONE INTERFACE
Dr. Markus Waldeck wrote:
> Package: autopsy
> Version: 2.08-1
> Severity: important
>
> starting autopsy results in
> ERROR: Sleuth Kit ils executable missing
>
> % dpkg -L sleuthkit| grep ils | grep bin
> /usr/bin/ils-sleuthkit
>
> -- System Information:
> Debian Release: 4.0
> APT prefers t
* Paul Gear <[EMAIL PROTECTED]>:
> That is true, but in both of the machines i've upgraded to Shorewall
> 3.2.4, they have not started successfully. Shorewall does not start
> without the STARTUP_ENABLED variable being present, which i think is bad
> backwards-compatibility behaviour. I'll have
* Greg Norris <[EMAIL PROTECTED]>:
> At the very least, README.Debian should be updated to reflect this
> change in behaviour. Currently the file says:
>
>1. AUTOMATIC STARTUP
>
>
>In order to avoid the startup of the firewall on an unconfigured
>machine, a
* Lars Wirzenius <[EMAIL PROTECTED]>:
> Package: shorewall
> Version: 3.0.4-1
>
> When testing shorewall with piuparts, I get the following error:
>
> 0m7.6s ERROR: Package purging left files on system:
> /etc/shorewall
> owned by: shorewall
> /etc/shorewall/tcstart
>
> This is due to p
* Paul Gear <[EMAIL PROTECTED]>:
> Johannes Graumann wrote:
> > Package: shorewall
> > Version: 3.0.4-1
> > Severity: normal
> >
> >
> > The recent update to a3.0.4-1 presents the problem of installing a new
> > /etc/shorewall/shorewall.conf file without making the admin aware of
> > customiza
Package: wnpp
Severity: wishlist
Owner: Lorenzo Martignoni <[EMAIL PROTECTED]>
* Package name: python-pynids
Version : 0.5
Upstream Author : Michael J. Pomraning <[EMAIL PROTECTED]>
* URL : http://pilcrow.madison.wi.us/pynids/
* License : GPL
* Sam Morris <[EMAIL PROTECTED]>:
> Lorenzo Martignoni wrote:
> >but, as you can see, on my own system ipv6 seems to be disabled
> >correctly.
> >
> >What happens on your system if you clear all firewall rules and policies
> >and then issue a "shor
* Daniel Nylander <[EMAIL PROTECTED]>:
> Package: shorewall
> Version: 3.0.4-1
> Severity: wishlist
> Tags: patch l10n
>
>
> Here is the swedish translation of the debconf template for shorewall.
>
> Regards,
> Daniel
Thank you very much. I'll include it soon.
-- lorenzo
--
To UNSUBSCRIBE,
* Paul Gear <[EMAIL PROTECTED]>:
> Thijs Kinkhorst wrote:
> >>/etc/init.d/shorewall stop will keep applied some of the shorewall settings
> >
> >
> > I experienced a problem that I think reduces to the same issue: I executed
> > "/etc/init.d/shorewall stop", thinking that it would disable the sh
Package: scapy
Severity: wishlist
According to the webpage http://www.secdev.org/projects/scapy/ the new version
1.0.2 is available.
-- System Information:
Debian Release: testing/unstable
APT prefers unstable
APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: i386 (i686)
Shell:
* Jeroen van Wolffelaar <[EMAIL PROTECTED]>:
> Package: shorewall
> Version: 2.2.3-2
>
> The default shorewall config says:
>
> | # Setting DISABLE_IPV6=Yes will cause Shorewall to disable IPV6 traffic
> | # to/from and through your firewall system. This requires that you have
> | # ip6tables in
* Michael Gilbert <[EMAIL PROTECTED]>:
> Package: autopsy
> Version: 2.06-1
> Severity: wishlist
>
> when autopsy is run as non-root, the following error will be generated,
> "Can't open log: autopsy.log at /usr/share/autopsy/lib//Print.pm line
> 316". it wolud be much better if the message wa
* Clytie Siddall <[EMAIL PROTECTED]>:
> Sorry, my translation program has been munging text after finishing.
> The fixed file is attached below.
>
> from Clytie
Thank you.
-- lorenzo
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROT
* Jari Aalto <[EMAIL PROTECTED]>:
> Package: shorewall
> Version: 3.0.1-1
> Severity: important
>
> After upgrade to v4 shorewall I changed the zone file to (ipsecfile is
> empty):
>
> #ZONE TYPEOPTIONS
>
> fw firewall
> net ipv4
> loc
* FX <[EMAIL PROTECTED]>:
> package: shorewall
> version: 2.2.3-2
>
> On 2005-07-30, the bogons file in version 2.2.6 was updated to reflect
> recent IANA allocations.
>
> Please backport the updated bogons file, /usr/share/shorewall/bogons, to
> the stable branch.
In order to backport the bo
* matthieu castet <[EMAIL PROTECTED]>:
> Package: shorewall
> Version: 2.4.5-1
> Severity: important
>
>
> Hi,
>
> you should add some check on /var/lib/shorewall/lock in init.d script or
> add information.
>
> For an unknow reason (hard reset ?) /var/lib/shorewall/lock was still
> here, and I
* Lorenzo Martignoni <[EMAIL PROTECTED]>:
> * John Summerfield <[EMAIL PROTECTED]>:
> > Package: shorewall
> > Version: 2.2.3-1
> > Severity: normal
> >
> > I maintain the software on several systems remotely, connecting over
> > they Internet.
* Jari Aalto <[EMAIL PROTECTED]>:
> Package: shorewall
> Version: 2.2.3-1
> Severity: wishlist
>
> Please add rules for Apple iTunes service (Linux daapd and mt-daapd servers):
>
> Port 3689 tcp + udp
Hello,
in my opinion is useless to add new actions, like this one, to Shorewall
because su
* Jari Aalto <[EMAIL PROTECTED]>:
> Package: shorewall
> Version: 2.2.3-1
> Severity: wishlist
>
> The Distributed Checksum Clearinghouse or DCC is a cooperative, dis-
> tributed system intended to detect "bulk" mail or mail sent to many
> peo- ple. It allows individuals receiving a single mail
* Jari Aalto <[EMAIL PROTECTED]>:
> Package: shorewall
> Version: 2.4.5-1
> Severity: important
>
> It appears that once a DNAT rule has been done, it persists even
> accross 'restart' or 'force-reload'. This is a serious security hole,
> because the old rules should not be there any more if chna
* Robert Millan <[EMAIL PROTECTED]>:
> Package: shorewall
> Version: 2.4.5-1
> Severity: normal
>
> Shorewall floods klogd / dmesg buffers with useless log messages. This makes
> the console almost unusable (you can barely read what you type).
>
> Please see what upstream says about it:
>
>
* Jari Aalto <[EMAIL PROTECTED]>:
> Package: shorewall
> Version: 2.4.5-1
> Severity: wishlist
>
> Jabber is IM protocol that uses TCP ports:
>
> 5222 non-encrypted (outgoing client)
> 5223 encrypted
> 5269 Jabber server intercommunication
>
>
* Sam Morris <[EMAIL PROTECTED]>:
> Package: shorewall
> Version: 2.2.3-2
> Severity: important
>
> Shorewall doesn't seem to disable IPv6 during bootup. I have
> DISABLE_IPV6=Yes set in /etc/shorewall/shorewall.conf, and yet, after a
> reboot:
>
> $ sudo ip6tables --list
> Password:
> Chain INP
* Martin Schulze <[EMAIL PROTECTED]>:
> Florian Weimer wrote:
> > >> (Note that I have yet to test Lorenzo's new package.)
> > >
> > > Are you in a position to do so?
> >
> > Sure, but the question is if you want to rely on the results. You
> > don't seem to trust my judgement on this matter, fo
* Florian Weimer <[EMAIL PROTECTED]>:
> * Lorenzo Martignoni:
>
> > The patch has been tested by me and by Paul Gear but further tests will
> > be better, so your feedback will be very precious.
>
> Apart from the lack of CVE entry in the changelog, the pac
* Pieter Ennes <[EMAIL PROTECTED]>:
> Package: shorewall
> Version: 2.4.3-1
> Severity: normal
>
> Shorewall packages >2.4.x seem to be missing the providers file in
> /usr/share/doc/shorewall/default-config.
Hello,
thank you for your report. I added the missing file and built a new
package (2.
* Florian Weimer <[EMAIL PROTECTED]>:
> * Martin Schulze:
>
> >> > What was the behaviour pre-sarge?
> >> > What is the behaviour post-sarge (or rather in sarge)?
> >>
> >> Do you mean "before and after the upstream security update"? The
> >> terms pre-sarge/post-sarge do not make much sense to
* Florian Weimer <[EMAIL PROTECTED]>:
> * Martin Schulze:
>
> > What was the behaviour pre-sarge?
> > What is the behaviour post-sarge (or rather in sarge)?
>
> Do you mean "before and after the upstream security update"? The
> terms pre-sarge/post-sarge do not make much sense to me in this
> c
The bug affects Shorewall 2.2.x and 2.4.x but the only affected Debian
package is shorewall_2.2.3-1 which is currently in Sarge.
The problem with this bug is that clients which mac addresses are known
can bypass the firewall rules and do whatever they want: if
MACLIST_DISPOSITION is set to ACCEPT
* Manoj Srivastava <[EMAIL PROTECTED]>:
> Package: shorewall
> Version: 2.4.1-2
> Severity: normal
>
> Hi,
>
> On upgrade, shorewall asks the scary looking question:
> "Did you check your configuration and do you want to restart
> Shorewall right now?"
>
> Followed by:
>
Package: shorewall
Version: 2.4.1-2
Severity: critical
Tags: security
A client accepted by MAC address filtering can bypass any other rule.
If MACLIST_TTL is set to a value greater than 0 or MACLIST_DISPOSITION
is set to "ACCEPT" in /etc/shorewall/shorewall.conf (default is
MACLIST_TTL=0 and MACLI
* Remi Vanicat <[EMAIL PROTECTED]>:
> Package: shorewall
> Severity: wishlist
>
> Hello,
>
> the fireflier documentation say that it could be used in parallel to
> another firewall, fireflier using is own user-space rule, and the
> other firewall ruling the iptables (who can use the QUEUE target
* Christian Perrier <[EMAIL PROTECTED]>:
> Package: shorewall
> Version: N/A
> Severity: wishlist
> Tags: patch l10n
>
> Please find attached the french debconf templates update, proofread by the
> debian-l10n-french mailing list contributors.
Thank you very much.
> Please, for the next updates
* Debian User <[EMAIL PROTECTED]>:
> Package: shorewall
> Version: 2.0.15-1
> Severity: important
>
> An upgrade from a version < 2.0.1 to a more recent version does not
> touch the the old configuration under /etc/shorewall, in particular the
> obosolete rf1918 file is left, which will then be u
* Jari Aalto <[EMAIL PROTECTED]>:
> Package: shorewall
> Version: 2.2.3-1
> Severity: wishlist
>
> Please all following AllowNFS and DenyNFS rules:
>
> rpcinfo -p
> 102 tcp111 portmapper
> 102 udp111 portmapper
> 134 tcp 2049 nfs
> 1000
* John Summerfield <[EMAIL PROTECTED]>:
> Package: shorewall
> Version: 2.2.3-1
> Severity: normal
>
> I maintain the software on several systems remotely, connecting over
> they Internet.
>
> I am concerned that one day an upgrade to shorwall will leave me with a
> broken firewall and the need
* Patrice Weber <[EMAIL PROTECTED]>:
> Package: shorewall
> Version: 2.2.2-1
> Severity: important
>
> Hello,
>
> The list of subnetworks generated by the python program and present in
> the rfc1918 file are not correct (for example : 83.0.0.0/8).
>
> This is why I went to
> http://www.shorewal
* Miroslav Kure <[EMAIL PROTECTED]>:
> Package: shorewall
> Severity: wishlist
> Tags: l10n, patch
>
> Hi, in attachement there is initial Czech translation (cs.po) of
> shorewall debconf messages, please include it.
Hi,
thank you for the translation. It will be included in the next release
of
* Christian Perrier <[EMAIL PROTECTED]>:
> Package: shorewall
> Version: N/A
> Severity: wishlist
> Tags: patch l10n
>
> Please find attached the french debconf templates update, proofread by the
> debian-l10n-french mailing list contributors.
>
> Please, for the next updates you make to this pa
* Juergen Kreileder <[EMAIL PROTECTED]>:
> Package: shorewall
> Version: 2.0.15-1
> Severity: normal
> Tags: patch
>
> There's a typo in /usr/share/shorewall/firewall that breaks the rejNotSyn
> action. Here's a fix:
> [...]
Thank you for your report and for your patch. I informed the upstream
* Brian May <[EMAIL PROTECTED]>:
> Package: shorewall
> Version: 2.0.7-1
> Severity: important
>
> Hello,
>
> We route outgoing packets for several satellite connections.
>
> After a big set of upgrades (including kernel version) today, these
> asymmetric connections stopped
> working.
>
> I
* Kenny Duffus <[EMAIL PROTECTED]>:
> Package: autopsy
> Version: 2.03-2
> Severity: normal
> Tags: patch
>
> Autopsy defines the locations of programs to produce MD5 and SHA1
> checksums in /usr/share/autopsy/conf.pl however these variables are not
> used everywhere. As a result autopsy tries t
* Kenny Duffus <[EMAIL PROTECTED]>:
> Package: autopsy
> Version: 2.03-2
> Severity: normal
> Tags: patch
>
> In 1.73-3 the sleuthkit package renamed dstat to datastat to
> solve duplicate filenames.
Hello,
I fixed the bugs and notified my sponsor. He will upload the new
packages soon.
In the
* Kenny Duffus <[EMAIL PROTECTED]>:
> Package: autopsy
> Version: 2.03-2
> Severity: normal
> Tags: patch
>
> In 1.73-3 the sleuthkit package renamed dstat to datastat to
> solve duplicate filenames.
Thank you for your report and for your patch. The new version of the
packages fixed the reported
60 matches
Mail list logo
