Summary: | Should be aware of firewalls | ||
---|---|---|---|
Product: | [Applications] systemsettings | Reporter: | Daniel <code> |
Component: | kcm_kdeconnect | Assignee: | Albert Vaca Cintora <albertvaka> |
Status: | CONFIRMED --- | ||
Severity: | wishlist | CC: | aleixpol, kde, plasma-bugs, rdieter, shanmukhateja |
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | Fedora RPMs | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: |
Description
Daniel
2016-01-23 18:37:20 UTC
In that case it would be great if you can ask the Fedora packagers to add a script to allow kdeconnect on the firewall when it is installed. Could you contact them? The Fedora package ships with a FirewallD profile that can be turned on through the GUI client or `firewall-cmd --add-service kde-connect`. However, it’s so unlikely that they will enable more services by default that I wouldn’t even ask. The default policy for Fedora Workstation and KDE spins only include dhcp, mdns, and samba-client. All other services must be added by the users themselves and I’m not aware of any packages that enable themselves (including apache and smtp servers). Which in short brings me back to the generic solution of: detect when ports are blocked by any kind of firewall and display a warning in the UI used to discover and pair devices. marking confirmed wishlist What's the status of this? Is KDE Connect usable in Fedora/Red Hat? fedora's kdeconnect packaging includes a firewalld definition/profile for ports used (per comment #2), and installs it as /usr/lib/firewalld/services/kde-connect.xml It's contents are: <service> <short>KDE Connect</short> <description> KDE Connect allows intercommunicating with mobile devices to receive messages and notifications. </description> <port protocol="tcp" port="1714-1764"/> <port protocol="udp" port="1714-1764"/> </service> This allows users to use firewalld UI's (like firewall-config) to easily allow this communication if they wish (by opting-in to allow it). It cannot be enabled automatically or by default (by policy) As this wishlist is stated, I'm not sure kde-connect itself can tell whether it's communications are being blocked by a firewall (like firewalld). As an aside, I've also lobbied fedora's kde-sig to use 'Fedora Workstation' firewall zone by default (which would allow this out of the box), but that proposal was rejected. Would it make sense to have the file installed by kde connect instead of it being a patch by the distribution? *** Bug 398892 has been marked as a duplicate of this bug. *** |