5 ms·
Good firewalls should always block unwanted traffic whether it's inbound or outbound. This is not anything new, but you're right that most people trust the devi
by ams6110 13y ago
Good firewalls should always block unwanted traffic whether it's inbound or outbound. This is not anything new, but you're right that most people trust the devices they own. Not anymore.
- mmagin 13y agoGood luck making that easy for the end-user to configure.
- mbillie1 13y agoYep you've basically refuted the idea of personal security due to a vague insinuation of how "most people" trust their electronics. Or did you have anything constructive to add?
- mmagin 13y agoSorry, I should have said: "Historically it's been very difficult to make detailed firewall configuration user-friendly. As a result, we've lived with the simplistic compromise of 'allow outgoing connections, don't allow incoming connections'. It seems like it's going to require some incredible new firewall configuration interface if we hope to make it possible for the ordinary clueless computer user to properly configure outgoing firewall rules."
- w_t_payne 13y agoWe have to assume that our lives are public; and that we have no secrets from those who want to get them the most (i.e. bad actors). We are vulnerable and weak, and had better get used to the idea that we can be f*cked over at will by whosoever takes a fancy to the idea.
- gizmo686 13y agoI think this is something of a chicken and egg problem. The basic firewall UI is allow <computer> to use <port> for <incoming|outgoing>. This interface can be made very easy to use. The problem is that if this was the default then programs would simply not work, and users would not know why. However, if it became standard, then programs would tell users to check their firewall, and can even tell users the information that they need to fill into the firewall (eg. name of computer, port, ...). Conceivably, you could define an protocol for devices to request an opening. This protocol could include a way of sending the password.
- chiph 13y agoThey'll just switch to port 80. No one is going to be willing to block that outgoing.
- Dylan16807 13y agoYou know firewalls work based on port AND host, right? Block all connections coming from the TV.
- piaskal 13y agoIf you have a smart TV you probably want to browse the web on it.
- oasisbob 13y agoRFC 3514 makes this easy: http://www.ietf.org/rfc/rfc3514.txt http://www.ietf.org/rfc/rfc3514.txt
- pit 13y agoI want to try an experiment that goes like this: 1. Block all network traffic, inbound and outbound. 2. When I decide that I need a specific network resource, enable it in a whitelist (i.e. enable traffic to/from news.ycombinator.com on port 80) I wonder what that Internet would look like.