News for hackers. Stuff that matters.
Re:Dumb Ideas in Computer Security (2005) by michaelt on Friday January 02, 2015 @03:08PM (#8828254)

  The most recognizable form in which the "Default Permit"
  dumb idea manifests itself is in firewall rules. [...] 
  The opposite of "Default Permit" is "Default Deny" and 
  it is a really good idea.
And now you know why everything from version control systems to video conferencing software tunnel things over HTTP!
Re:Dumb Ideas in Computer Security (2005) by mikey_p on Friday January 02, 2015 @03:26PM (#8828352)
I think there's a significant difference here between inbound and outbound firewalls.

Edit: I think about it like getting into a stadium, only a few entrances with ticket takers, but there are lots of doors that are exit-only.

Re:Dumb Ideas in Computer Security (2005) by zrm on Friday January 02, 2015 @04:36PM (#8828692)
There is an extent to which that's true, but it's still subject to the same consequences. If you block all "incoming" traffic then developers react to it. Apps that need incoming data just maintain a persistent connection to a third party server which passes the incoming data over the open connection.

And the third party server doesn't have any magic logic that couldn't be built into the endpoints, it's effectively just a router to work around the restrictive firewall. But now you have a third party in a position to spy on you or impose censorship.

Re:Dumb Ideas in Computer Security (2005) by corv on Friday January 02, 2015 @03:25PM (#8828346)
I agree with your observation and I think the author was suggesting that whitelisting is a more viable solution compared to blacklisting when it's necessary to open a port.