Hi all,
I just discovered that at least with Trinity 3.5.12.2, ksmserver is listening on all interfaces by default. This could be a security concern. Nmap detects it as the XFCE Session Manager.
It seems this problem was separately fixed in KDE: https://bugs.kde.org/show_bug.cgi?id=154243
Was anyone aware of this? I guess it would be good to have a fix in place for R14. Is anyone aware of a workaround?
Thanks, Julius
I just discovered that at least with Trinity 3.5.12.2, ksmserver is listening on all interfaces by default. This could be a security concern. Nmap detects it as the XFCE Session Manager.
Running nmap localhost on my R14 systems do not reveal any related open ports. What is the full syntax of the nmap command you ran?
Darrell
Am Montag, 19. Mai 2014 schrieb Darrell:
I just discovered that at least with Trinity 3.5.12.2, ksmserver is listening on all interfaces by default. This could be a security concern. Nmap detects it as the XFCE Session Manager.
Running nmap localhost on my R14 systems do not reveal any related open ports. What is the full syntax of the nmap command you ran?
$ nmap localhost -p1-65535
[...] 46657/tcp open unknown
$ netstat -altp [...] tcp 0 0 *:46657 *:* LISTEN 3206/ksmserver [kin [...] tcp6 0 0 [::]:40456 [::]:* LISTEN 3206/ksmserver [kin
So it' there on debian, too.
nik
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA224
Am Montag, 19. Mai 2014 schrieb Darrell:
I just discovered that at least with Trinity 3.5.12.2, ksmserver is listening on all interfaces by default. This could be a security concern. Nmap detects it as the XFCE Session Manager.
Running nmap localhost on my R14 systems do not reveal any related open ports. What is the full syntax of the nmap command you ran?
$ nmap localhost -p1-65535
[...] 46657/tcp open unknown
$ netstat -altp [...] tcp 0 0 *:46657 *:* LISTEN 3206/ksmserver [kin [...] tcp6 0 0 [::]:40456 [::]:* LISTEN 3206/ksmserver [kin
So it' there on debian, too.
nik
Problem confirmed; fixed in GIT hash c383da9.
Thanks for bringing this to our attention!
Tim