Page MenuHomePhabricator

kdeconnectd
Closed, ResolvedPublic

Description

This is the Android integration daemon that listens on all interfaces by default in Debian Stretch.

To minimize GW attack surface it must be removed or somehow disabled. Brief experimenting shows there is no obvious service that can be disabled - Its mentioned that its tied to DBUS. Not much documentation on how to disable it either. What worked was purging the kconnect package.

Details

Impact
Normal

Event Timeline

Kdeconnect package is installed by default? I just did a fresh image of developers-14 plus upgrade, and I don't see kdeconnect installed or kdeconnectd running.

JasonJAyalaP (Jason J. Ayala P.):

My mistake. I asked on the kde forums:

https://forum.kde.org/viewtopic.php?f=66&t=140535

Please ask how to do that from command line.

Forum said:

I don't know for sure, so I did a little bit of perusing of the dbus API, I dug up "qdbus org.kde.kde /modules/kdeconnect [start|stop]" which looks like it should start/stop the kdeconnect module (service?).

I don't have exactly those service names. Through tab completion I found something close with kde5, but no kdeconnect stop/start.

We shouldn't disable it through qdbus - because that won't persist across reboots. It only disables it for a session, in memory. qdbus isn't great since we want to disable it using a package / by dropping a config snippet into the right place.

The solution would probably look similar to this:

https://github.com/Whonix/kde-lowfat/blob/master/usr/share/kde-lowfat/nepomukserverrc

or this https://github.com/Whonix/kde-lowfat/blob/master/usr/share/kde-lowfat/krunnerrc

@HulaHoop

Wait. I don't see this package on GW.

dpkg -l | grep kdeconnect
killall -9 kdeconnectd
/usr/share/dbus-1/services/org.kde.kdeconnect.service
qdbus org.kde.kde /modules/kdeconnect stop

It's also not on the workstation.

This is the Android integration daemon that listens on all interfaces by default in Debian Stretch.

Check for unwanted listen ports.

sudo netstat -anltp

If that is understood, then this ticket can be probably resolved.