Bug 337250 - Ask before binding/listening on a specific network IF, firewall rules
Summary: Ask before binding/listening on a specific network IF, firewall rules
Status: RESOLVED NOT A BUG
Alias: None
Product: kdeconnect
Classification: Applications
Component: common (show other bugs)
Version: unspecified
Platform: unspecified Linux
: NOR wishlist
Target Milestone: ---
Assignee: Albert Vaca Cintora
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-07-08 22:24 UTC by Richard Z.
Modified: 2018-01-16 21:43 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Richard Z. 2014-07-08 22:24:59 UTC 
Hi,

in Fedora we would like to puch a hole into the Firewall for KDE Connect automatically, opened this
https://bugzilla.redhat.com/show_bug.cgi?id=1115547

bug report.

Because it might also be a good idea to ask user before binding/listening on a specific network IF,  so I was thinking that if such code is added it would be also the right place to have a hook which would call a distribution supplied scriptlet to open up the firewall.

Reproducible: Always
Comment 1 Albert Vaca Cintora 2014-09-30 02:30:08 UTC 
I don't think we should bother the user with this: maybe we could open the ports automatically when the kdeconnect package is installed (a installation-time script could do it?).
Comment 2 Richard Z. 2014-10-19 17:21:33 UTC 
I think kdeconnect should be enabled only on interfaces where it is expected that such devices will be connected but not eg on company networks. Afaics this is not easy to determine 

In my view the security implications are somewhat similar to Bluetooth devices .. except that BT has a dedicatetd IF with very limited range whereas for kdeconnect the limits must be set manually.
Comment 3 Aleix Pol 2018-01-16 21:43:02 UTC 
Referred bug was closed.