News for hackers. Stuff that matters.
Re:More awful IoT stuff by Domenic_S on Wednesday June 22, 2016 @03:51PM (#11956500)
Apparently this is kind of a hard thing to handle. I battle with this and PS4 Remote Play -- about 80% of the time, RP will give up looking on my local network and go out to the internet to find my PS4... which is right here on the same network. If I cancel it and retry a few times it always ends up seeing it but man what a pain.
Re:More awful IoT stuff by api on Wednesday June 22, 2016 @04:20PM (#11956665)
We've been using the term "endpoint hostile" to describe how networks are typically deployed, especially with IPv4.

"Endpoint hostile" networks are designed with a single use case in mind: accessing remote servers, usually via HTTP/HTTPS. Other use cases are prohibited or broken.

Here are some of the characteristics that would label a network as endpoint hostile:

- "Device isolation," which prohibits local LAN device communication. This is common on some WiFi networks. It's forgivable on a public WiFi but not elsewhere.

- Symmetric NAT

- Multiple levels of nested NAT e.g. consumer routers plugged into consumer routers. It's important to note that this makes everything flaky due to weird interactions and timeout behaviors. In our experience it's disturbingly common. We talked to one person whose company had at least five levels of this, requiring things like "ServerAliveInterval 10" in ssh_config.

- Lack of support for NAT hairpinning. (NAT can't NAT-traverse with itself.)

- Short NAT/firewall stateful connection timeout (120s is the RFC recommendation, but 30-60s is common and we've seen 15.)

- IPv6 absent (assuming it's available upstream) or deployed in a silly way (e.g. IPv6 NAT).

- Lack of support for local multicast or broadcast

- Aggressive edge firewall rules that prohibit UDP, non-standard TCP ports, etc. or that DPI traffic and attempt to block anything other than HTTP, SSH, and SSL.

- Badly implemented NAT ALGs for things like FTP and SIP that break other traffic.

- Lack of uPnP or NAT-PMP support.

- Mandatory proxy configuration.

- Middle boxes that modify traffic in general. This includes things that bork TCP in a misguided attempt to "optimize" it, things that inject HTTP headers (or worse JavaScript), things that modify DNS to strip A/AAAA records for "private" IPs or strip TXT records, etc.

Some of this stuff is just stupidity or brokenness, but much of it is implemented for "security" reasons.

I personally consider reliance on network edge controls for security to be a borderline-obsolete cargo cult practice, since the vast majority of today's vulnerabilities and attack vectors are unaffected by it and involve things like cloud services, e-mail, web, app updates, etc. I've worked in netsec/infosec and have seen a number of intrusions, and so far I have yet to see one in the past 10 years that was mitigated in any way by the presence of a firewall. Yet a generation of IT people thinks "firewall equals security" and I'm increasingly thinking this generation will have to just pass along.

Re:More awful IoT stuff by ianlevesque on Wednesday June 22, 2016 @05:28PM (#11957175)
This is exactly why the use of a remote server exists in so many IoT devices. Widely deployed home APs, even in USA, come with device isolation on by default or even not disableable.
Re:More awful IoT stuff by api on Wednesday June 22, 2016 @05:48PM (#11957295)
Is there actually a good reason for this "feature" outside of airport and coffee shop WiFi?

Basically you have a 2000 mile data path to your light bulb because routers suck and networking engineers are cargo cult morons.

Re:More awful IoT stuff by CaptSpify on Wednesday June 22, 2016 @06:02PM (#11957387)
IMO: this is actually a good default setting. Home-router designers should assume that things are hostile by default. Of course, it should be dead-simple to turn this off as well.
Re:More awful IoT stuff by api on Wednesday June 22, 2016 @06:08PM (#11957421)
I pretty vehemently disagree. We should be very reluctant to systematically break good things to protect badly written junk.

Let badly written junk burn. Then people will learn it's junk and stop using it or the developers and vendors will be forced to fix it.

Re:More awful IoT stuff by robomc on Wednesday June 22, 2016 @06:58PM (#11957710)
Isn't it more like having a median barrier?

It's unnecessary if everyone drives competently, but it also successfully prevents people crashing through no fault of their own.

It also breaks or complicates use cases like "changing which direction you're going on the highway".

Re:More awful IoT stuff by Godel_unicode on Wednesday June 22, 2016 @07:55PM (#11957956)
So you're in favor of Grandparents getting cryptowall from someone else connected to their WEP-encrypted wifi because screw them for using Windows XP and a cheap router? Off-switches for things like this are cool, because people who need them will find them, and people who don't won't.

This is remarkably similar to defeatable traction-control; people who care enough to figure out what that button does will push it and have fun. People who don't won't and they'll be safe.

Re:More awful IoT stuff by api on Wednesday June 22, 2016 @08:21PM (#11958064)
Yes, if this is the cost. Loss of local connectivity is not a small degradation. It's like losing floating point math from your CPU or the ability of your car to go in reverse.

If we're building endpoint networks to prohibit local traffic, we are forcing a terrible architecture with terrible long-term privacy and security implications. Because of this, we will have a future where the NSA (and vendors, and advertisers, and the Chinese PLA, and ...) will literally know when you flush your toilet. In the future every interaction you have with every device in your house will be broadcast to third parties across multiple national boundaries and clouds.

... because we had to protect Windows XP machines from rare, marginal threat profiles. (Has anyone actually seen malware spread this way in the past 10 years in the wild?)

The potential criminal and totalitarian applications of a cloud-powered IoT world are incredible. Look into "nudge theory" for a starting point, and then consider things like:

http://www.theatlantic.com/technology/archive/2014/02/when-y...

http://www.ibmbigdatahub.com/blog/power-behavioral-fingerpri...

The decision of how to architect our communications infrastructure today and whether to, for example, permit local traffic could in the future determine whether or not we evolve into a borg-like totalitarian collective or a cooperative society of sovereign individuals. Communications infrastructure affects... well... how we communicate... which in turn affects every single aspect of human society and culture over very long spans of time.

It's a special case of a larger phenomenon called path dependence. Small choices that you make today based on what seem like rational reasons today can have huge differences in the long term outcome of things in the distant future. While the future isn't fully knowable, sometimes conceptual reasoning from first principles can tell us what the likely outcome of a particular path might be.

Re:More awful IoT stuff by TeMPOraL on Wednesday June 22, 2016 @08:29PM (#11958097)
Also worth pointing out that the reason everything talks over HTTP now is because companies figured out that the only port on a typical user's computer that can be assumed to be free of bullshit pseudo-security rules is the port 80...
Re:More awful IoT stuff by api on Wednesday June 22, 2016 @08:44PM (#11958152)
Sure. We've degraded the Internet from the Internet to the HTTP-to-AWS-gateway-net. Meanwhile security still sucks.
Re:More awful IoT stuff by Godel_unicode on Wednesday June 22, 2016 @09:12PM (#11958254)
It's closer to losing ECC; if you need it you can get it and if you don't need it you don't even need to know it exists. You're being rather alarmist, don't you think?

> Has anyone actually seen malware spread this way in the past 10 years in the wild

Yup, had several IR cases (trending up) where this was determined to be the initial vector. Related: stop making this argument. Nothing is seen in the wild until it is (go back a few years and realize this argument was made about cryptowall-style malware).

I think you should re-read the end of my first paragraph; isolation should have an off switch. Give people the option and let them choose. Sorry if that's bad for your business model.

Re:More awful IoT stuff by goodplay on Wednesday June 22, 2016 @10:15PM (#11958452)
I also believe that trading real networks for supposed security would be a very bad move.

Network node security should not be delegated to the network. Not only would this necessitate forgoing very useful features that networks enable, you won't improve node security. Devices that are vulnerable by merely sharing a network with other nodes tend to have other more sever security lapses.

I agree that a button is simple way to switch between modes, but it will also make point-to-point the default. People don't change defaults, and companies will eventually cease to implement network capability as a result.

I'm all for better network security, but not at the expense of discarding the network itself.

Re:More awful IoT stuff by mwcampbell on Wednesday June 22, 2016 @07:06PM (#11957761)
I'm surprised that device isolation is common on home APs. Wouldn't that break some fairly mainstream things like Chromecast?
Re:More awful IoT stuff by twr on Wednesday June 22, 2016 @08:02PM (#11957990)
Yes. In fact, the Chromecast setup apps suggest disabling isolation if it cannot be connected to. Broken multicast support also prevents setup.
Re:More awful IoT stuff by voltagex_ on Wednesday June 22, 2016 @07:19PM (#11957824)
Same with the way Xbox One Streaming works. At least Sony has set up some kind of NAT traversal to allow proper remote play.