[Bug 989278] New: kdeconnect, firewall port not opened
http://bugzilla.opensuse.org/show_bug.cgi?id=989278 Bug ID: 989278 Summary: kdeconnect, firewall port not opened Classification: openSUSE Product: openSUSE Distribution Version: Leap 42.1 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: KDE Applications Assignee: opensuse-kde-bugs@opensuse.org Reporter: epistemepromeneur@free.fr QA Contact: qa-bugs@suse.de Found By: --- Blocker: --- if you install kdeconnect then kdeconnect service is not added in the list of the authorized services in the firewall then port used by kdeconnect are not opened then kdeconnect can't dialog with other kdeconnect then you can't paired other devices. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=989278
Episteme PROMENEUR
http://bugzilla.opensuse.org/show_bug.cgi?id=989278
http://bugzilla.opensuse.org/show_bug.cgi?id=989278#c1
Wolfgang Bauer
http://bugzilla.opensuse.org/show_bug.cgi?id=989278
http://bugzilla.opensuse.org/show_bug.cgi?id=989278#c2
Wolfgang Bauer
But we probably could add a corresponding config file for the SUSE firewall to our package (would still require you to manually allow the service in YaST).
PS, I just saw that our package actually does contain such a service file already. Closing as INVALID then. Feel free to reopen if this doesn't work, i.e. if the service doesn't show up in YaST, or the wrong ports are opened. If you mean that it should open the ports automatically, then this is a WONTFIX. I suppose it would be a severe security risk if random packages/application would just open ports in the firewall by themselves. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=989278
http://bugzilla.opensuse.org/show_bug.cgi?id=989278#c3
--- Comment #3 from Episteme PROMENEUR
http://bugzilla.opensuse.org/show_bug.cgi?id=989278
http://bugzilla.opensuse.org/show_bug.cgi?id=989278#c4
--- Comment #4 from Wolfgang Bauer
with opensuse 13.1 when installing kdeconnect all the steps are executed.
openSUSE 13.1 did not even contain kdeconnect. And the older openconnect-kde4 package in KDE:Extra did/does not open any firewall ports automatically on installation either, I just had a look. It only contains the very same SuSEfirewall service file to make it appear in YaST. Normally all ports on the internal firewall zone are open by default though. So maybe the difference is that your interface was in the internal zone in your 13.1 installation, but is in the external one now, either because you configured it that way or the installer did. That's unrelated to KDE or the kdeconnect package though. And I say it again: I think it would be a severe security problem if random packages would automatically open random ports in the external firewall zone. Not to mention that I don't think any other package in openSUSE does that anyway. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=989278
http://bugzilla.opensuse.org/show_bug.cgi?id=989278#c5
--- Comment #5 from Episteme PROMENEUR
participants (1)
-
bugzilla_noreply@novell.com