[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-bugs-dist
Subject:    [Bug 79676] New: kmldonkey is listening on all addresses/interfaces
From:       Alexei Dets <adets () idsk ! com>
Date:       2004-04-15 6:50:02
Message-ID: 20040415065002.23409.qmail () ktown ! kde ! org
[Download RAW message or body]

------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
      
http://bugs.kde.org/show_bug.cgi?id=79676      
           Summary: kmldonkey is listening on all addresses/interfaces and
                    this is not configurable
           Product: kmldonkey
           Version: 0.10pre3
          Platform: unspecified
        OS/Version: Linux
            Status: UNCONFIRMED
          Severity: wishlist
          Priority: NOR
         Component: general
        AssignedTo: gibreel gibreel net
        ReportedBy: adets idsk com


Version:           0.10pre3 (using KDE 3.2.1-0.fdr.5.1, Fedora Core release 1 \
                (Yarrow))
Compiler:          gcc version 3.3.2 20031022 (Red Hat Linux 3.3.2-1)
OS:          Linux (i686) release 2.4.22-1.2174.nptlsmp

Kmldonkey (and its kicker applet) are always opening listening UDP sockets:

# netstat --inet --numeric-hosts -pl | grep "0 0.0.0.0"
...
udp        0      0 0.0.0.0:34537           0.0.0.0:*                           \
14833/kdeinit: appl udp        0      0 0.0.0.0:34538           0.0.0.0:*             \
15011/kmldonkey

I suppose that they are listening for the mldonkey core. It will be really nice if \
listening address will be configurable (like in mldonkey core itself) or at least it \
can check mldonkey core IP address & listen only on 127.0.0.1 if mldonkey core is \
local.

Of course, firewall (like iptables) can help but it is much more complicated (for \
ex., kmldonkey selects random UDP ports), requires root priveleges etc.

I think that this can improve system security a bit...


[prev in list] [next in list] [prev in thread] [next in thread]