Version: unspecified (using KDE 4.5.5) OS: Linux It concerns me that kde4 (reports as version 4.5.59?) listens on a number of high udp ports that are open to the network: tcp 0 0 129.21.92.148:53218 0.0.0.0:* LISTEN 3361/kdeinit4: kded tcp 0 0 129.21.92.148:47953 0.0.0.0:* LISTEN 15097/kded4 tcp 0 0 129.21.92.148:55131 129.21.139.185:2170 ESTABLISHED 3361/kdeinit4: kded tcp 0 0 129.21.92.148:52958 129.21.139.185:2170 ESTABLISHED 15097/kded4 tcp 0 0 129.21.92.148:48761 129.21.114.233:2170 ESTABLISHED 3361/kdeinit4: kded udp 0 0 0.0.0.0:1900 0.0.0.0:* 15097/kded4 udp 114624 0 0.0.0.0:1900 0.0.0.0:* 3361/kdeinit4: kded udp 0 0 129.21.92.148:49153 0.0.0.0:* 3361/kdeinit4: kded udp 0 0 129.21.92.148:49154 0.0.0.0:* 15097/kded4 Shouldn't these ports only be listening on 127.0.0.1 ? Reproducible: Didn't try OS: Linux (i686) release 2.6.35-27-generic-pae Compiler: cc
go into the Services control panel and see which services are running (or query them with `qdbus org.kde.kded | module`.) you can turn the non-activated-only-on-request ones there as well to see if one of those are opening the ports.
That would let me not start them automatically ... but what I'm wodnering is: how can I configure these services to only bind to interface lo (localhost) ? On Wed, Mar 16, 2011 at 11:41 AM, Aaron J. Seigo <aseigo@kde.org> wrote: > https://bugs.kde.org/show_bug.cgi?id=268663 > > > > > > --- Comment #1 from Aaron J. Seigo <aseigo kde org> 2011-03-16 16:41:41 --- > go into the Services control panel and see which services are running (or query > them with `qdbus org.kde.kded | module`.) you can turn the > non-activated-only-on-request ones there as well to see if one of those are > opening the ports. > > -- > Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email > ------- You are receiving this mail because: ------- > You reported the bug. >
Dear Bug Submitter, This bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? I am setting the status to NEEDSINFO pending your response, please change the Status back to REPORTED when you respond. Thank you for helping us make KDE software even better for everyone!
Dear Bug Submitter, This is a reminder that this bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? Thank you for helping us make KDE software even better for everyone!
Thank you for reporting this issue in KDE software. As it was reported on an older version, can we please ask you to see if you cazn reproduce the issue with a more recent software version? If you can confirm this issue still exists in a recent version, please change the version field and the status to "REPORTED" when replying. Thank you!
Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone!
This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone!