On 07/13/2014 06:26 PM, Ed Greshko wrote:
On 07/14/14 07:14, Kevin Kofler wrote:
Dan Mossor wrote:
Wait - you're saying that it's against Fedora Policies to ship firewall
rules for applications that need network access? Somebody needs to let
the Server Working Group know about that - they are working on the
packaging of firewall rules for every role they're creating.
At least in the days before "Fedora Next", the rule has always been that all
ports must be firewalled by default except where FESCo decided that they
should be open by default (which they did for sshd and mDNS), and that
packages must not override those defaults.
But, isn't there a difference between "ports open by default" and "supplying rules that *can* be enabled when needed"? Isn't that what is done for services such as "smtp"?
By default, port 25 is filtered. But, in firewalld there is a check box to open/enable "smtp" services. Isn't that the goal for KDE Connect?
There may have been some confusion over that in particular, but to be
clear...
*my* intent was indeed to simply ship a firewall rule and document it,
but not enable it by default.
-- Rex
_______________________________________________
kde mailing list
kde@xxxxxxxxxxxxxxxxxxxxxxx
https://admin.fedoraproject.org/mailman/listinfo/kde
New to KDE4? - get help from http://userbase.kde.org
