"Workstation" Product defaults to wide-open firewall
kevin.kofler at chello.at
Mon Dec 8 15:41:35 UTC 2014
Bastien Nocera wrote:
> Yeah, that's so useful. "Oh, you clicked it, it's your fault". That's not
> the type of OS I want to help implement, sorry.
So you rather implement the type of OS that just always assumes "Yes"
without even asking? Because that's what the current "firewall" rules do
(between quotes because it can hardly be called a firewall in that state).
How's that more secure than asking?
> How can users make their own decisions and be responsible for their own
> decisions when they don't know about firewall ports? Or firewalls? Or
> TCP/IP? You're starting with the wrong preconceptions.
The users who don't know about firewall ports will not need to open them up
at all. Developers running a development server (the use case given as a
justification for the change in the release notes) surely know what a port
More information about the devel