On 12/09/2014 10:11 AM, Bastien Nocera wrote:

The defaults for the various products are "packaged" by zones. You just need
to change the firewalld zone to get whatever is the default on the server side.

Ok, so it's another item on my list of "things to fix that fedora didn't get right" after I do an install. 

The release notes are misleading, at best.  All of the arguments I've heard used to justify this change have been boiled down to "end users don't understand networking" -- which means that calling this feature "developer oriented" in the release notes is wrong. 

There should be a far larger warning that any software that opens a non-privileged port is accessible to the world.  If I didn't do development (and if I hadn't read this thread) then I would probably have skipped that section and left my machine open to the world.


Or better, use VMs to deploy test instances which would have the same set of packages
and configuration as a Fedora Server version.

Proposing VMs is just moving the goalposts, especially if I have client-oriented software that wants to open ports.  And for developer things it means maintaining/securing two installations instead of one.



-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct

Reply via email to