<div dir="ltr"><div class="gmail_extra"><div class="gmail_quote">On Mon, Aug 18, 2014 at 10:36 PM, Richard Turner <span dir="ltr"><<a href="mailto:rjt@zygous.co.uk" target="_blank">rjt@zygous.co.uk</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class=""><p dir="ltr">
On 18 Aug 2014 20:02, "Elad Alfassa" <<a href="mailto:elad@fedoraproject.org" target="_blank">elad@fedoraproject.org</a>> wrote:<br>
> 3) Do we really need a firewall configuration UI?</p>
</div><p dir="ltr">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.</p>
<span class="HOEnZb"><font color="#888888"></font></span><br></blockquote><div> </div><div>I propose configuration that works out of the box.<br></div><div><br></div><div>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.<br>
<br></div><div>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).<br>
</div></div><br clear="all"><br>-- <br><div dir="ltr">-Elad Alfassa.</div>
</div></div>