We used to need firewalls at the edges of our home networks to keep bad actors out. Now we need firewalls that point the other direction to keep the bad actors on our networks in.
We used to need firewalls at the edges of our home networks to keep bad actors out. Now we need firewalls that point the other direction to keep the bad actors on our networks in.
It was for some kind of internet-cafe. But that we seem to need this nowadays for our private homes, troubles me.
What is this with the attitude, that it is ok, to view into the innermost privacy-sphere of your customers? Sorry, but LG is dead and gone for me. A company, that converts its paying customers into a product, ready to be sold to some advertiser just sickens me.
What comes next? Automatically detecting, when people no longer look at the screen, via a camera, to stop the showing of ads and resume, when people return in front of the screen? Or to detect how many people are watching (as Microsoft had patented)?
What happened to good old: We build one thing, sell it and that is fine. Why does everybody have to be an advertising-company, trying to maximize this revenue stream on the back of the live(data) of its paying customers?
In an answer to German press-inquiries, LG states, that the feature will stay. The only thing, they will change is, that disabling the feature really disables it. They stated, that this was a bug. And I actually believe this. I did not allege, it was malicious intend.
My real argument was, that I am more then happy, to pay good money for a good TV. But that I see no reason, why I should have to pay with my data as well (not being informed on that by the way, when buying this TV) and with this feature being enabled by default.
Sidenote: They told the German press, that the receiving server dropped the information, when the feature was disabled. They never told anyone, how the server should have been able to do that. As far, as I could see, the requests did not change, when deactivating that feature.
Greetings from Germany.
You were probably informed, somewhere between page 1 and 514 in the EULA.
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.
"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."
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.
I am often hesitant to offer this kind of correction because I feel like it sometimes sounds conceited, or as if I am trying to be superior to you somehow. I honestly don't feel that way and am just offering the correction because I feel like I would like to be corrected myself. I respect you for having learned a second language, it's more than I can say for myself.
I wish I knew a name for a homophonic typo which suggests criticism in that way, I used to know a guy who made typos like that all the time, emails from him had a kind of surreal meta-level quality to them. It is kind of a mondegreen, but not quite.
But my witty jokes aside, that reminds me of Little Snitch for Mac OS, which keeps installed programs from opening unauthorized connections to the outside. Is there a firewall setup that works this way for an entire home network? Possibly something that could be run on a small device/router?
That's not recent, most firewall do outbound traffic as well, and there are software solely dedicated to outbound traffic management, e.g. http://www.obdev.at/products/littlesnitch/index.html
Firewalls for Windows (I first saw it in ZoneAlarm) introduced application specific filtering. So you can allow one application to connect to HTTP servers and disallow another application from doing the same.
Edit: I was just reading this article an hour ago, about how to programmatically add rules to Windows built-in firewall using Delphi:
http://theroadtodelphi.wordpress.com/2013/11/21/using-the-wi...