Your message dated Mon, 24 Apr 2006 11:59:52 -0600
with message-id <[EMAIL PROTECTED]>
and subject line WNPP bug closing
has caused the attached Bug report to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Debian bug tracking system administrator
(administrator, Debian Bugs database)

--- Begin Message ---
Package: wnpp
Severity: wishlist

* Package name    : ftwall2
  Version         : x.y.z
  Upstream Author : Chris Lowth <[EMAIL PROTECTED]>
* URL             : http://www.lowth.com/p2pwall/ftwall2/
* License         : GPL
  Description     : P2P network firewall (Kazaa, Winmx, opennap, iMesh etc.)

(Include the long description here.)

NEW: http://www.lowth.com/p2pwall/ftwall2/
OLD: http://sourceforge.net/projects/p2pwall

MORE INFO

Linux journal article 2003-08-31: Securing Your Network against Kazaa
http://www.linuxjournal.com/article.php?sid=6945

DESCRIPTION

The P2Pwall project aims to provide iptables add-ins for the control
of Peer to peer file sharing traffic from applications such as Kazaa,
iMesh and others.

Ftwall-2 is an updated version of the original ftwall-1 software which
adds new P2p protocols to the set it can control.

Ftwall-2 is an add-on for linux firewalls that allows the control of
"Fast Track" peer-to-peer traffic (such as is used by "Kazaa" and it's
derivatives), WinMX and others using the OpenNAP protocol.

It is designed to block network traffic from P2P client applications
running in the "home" (or "green") network from making access to any
peers on the public internet. It is designed primarily for use in
networks where the security reigme allows "open access" for outbound
connections and "tightly limited" access for inbound ones. Ftwall-2
can be used in networks like this to prevent outbound P2P access from
the supported protocols, hence restricting illegal file downloads and
uploads.

A Fast track "home network" client that establishes an "outbound"
connection is (worryingly) immediately available to accept inbound
connections through the established TCP/IP socket - even if the
gateway firewall blocks all in-bound connections via "normal" TCP/IP
and UDP mechanisms. This is a kind of limited "tunnelling" and gives
rise to a number of concerns. Other P2P applications and protocols
present similar security challenges. Ftwall solves this (and other)
problems for the protocols it understands.

- "Ftwall" is short for "Fast Track traffic Firewall".
- "Fast track" is the networking protocol used by Kazaa, KazaaLite,
  iMesh and Grokster.
- "Ftwall" is part of the "p2pwall" project, which aims to provide
  similar mechanisms for other peer-to-peer file sharing protocols in 
  future.
- "P2pwall" is short for "Peer-to-peer traffic firewall".
- Ftwall version 2 is also capable of blocking WinMX and OpenNAP - and
  in this, it's name is a historical misnoma.

-- System Information:
Debian Release: 3.1
  APT prefers unstable
  APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: i386 (i686)
Kernel: Linux 2.6.10-1-686
Locale: LANG=C, LC_CTYPE=C (charmap=ISO-8859-1) (ignored: LC_ALL set to en_US)


--- End Message ---
--- Begin Message ---
Hello,

This is an automatic mail sent to close the RFP you have reported or 
are involved with.

Your RFP wnpp bug is being closed because of the following reasons:
- It is, as of today, older than 365 days.
- It hasn't had any activity recently.

As this is an automatic procedure, it could of course have something
wrong and probably it would be closing some bugs that are not 
intended by owners and submitters (like you) to be closed, for
example if the RFP is still of your interest, or there has been 
some kind of activity around it. In that case, please reopen the
bug, do it, DO IT NOW! (I don't want to be blamed because of
mass closing and not let people know that they can easily reopen
their bugs ;-).

To re-open it, you simply have to mail [EMAIL PROTECTED]
with a body text like this:

reopen 305050
thanks bts

Further comments on the work done in the bug sent to
[EMAIL PROTECTED] would be truly welcomed.
Anyway, if you have any kind of problems when dealing with
the BTS, feel free to contact me and I'd be more than happy to help
you on this: <[EMAIL PROTECTED]>.

A similar process is being applied to other kind of wnpp bugs.

Thanks for your cooperation,

 -- David Moreno Garza <[EMAIL PROTECTED]>.
 

--- End Message ---

Reply via email to