-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 08/18/2014 03:43 PM, Elad Alfassa wrote:
On Mon, Aug 18, 2014 at 10:36 PM, Richard Turner <rjt(a)zygous.co.uk
<mailto:rjt@zygous.co.uk>> wrote:
On 18 Aug 2014 20:02, "Elad Alfassa" <elad(a)fedoraproject.org
<mailto:elad@fedoraproject.org>> wrote:
> 3) Do we really need a firewall configuration UI?
What do you propose instead? If there's a firewall installed I
don't want to have to learn how to use iptables, or any other CLI
tool, to configure it. I'm a web developer, that doesn't mean I'm
a networking guru.
I propose configuration that works out of the box.
Right now in the firewalld policy in Fedora Workstation any
non-root port is unblocked by default. If you need a webserver
running on port 80, I assume the best way of fixing this would be
bundling a firewalld configuration file in webserver packages that
will open port 80 and port 443 for you - but that might be out of
scope for the Workstation WG and more in the Server WG realm.
Also, if we don't install it by default you'd still be able to
install it, or install cockpit instead (I don't remember if cockpit
has firewall controls, but it sounds like it's something it
probably would benefit from having).
Cockpit does not currently have a firewall UI, but it's certainly
something worth having there. I'll open an RFE.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1
iEYEARECAAYFAlPyXbgACgkQeiVVYja6o6N7mACghsCYLHdNFoKquEsVtucfOIDE
C4AAn1Sq6QthgAgVeWY+mUK9p7+1JWsJ
=nlUu
-----END PGP SIGNATURE-----