Hacker Read top | best | new | newcomments | leaders | about | bookmarklet login

Might be, but that’s not my concern as an operator of my private home network.

It’s completely fine for there to be conflicting goals even held by me. I want to not have my traffic interfered with when I’m on someone else’s network but I don’t want the vulnerable internet of shit stuff to be even more opaque on my network.



sort by: page size:

Indeed not. That's not what I said.

I don't even want them talking out to the internet by default, which is why I have a separate subnet with a different set of firewall rules that only allows whitelisted outbound connections.


I would not want to use your network if that was the case, and I wonder if you similarly would use someone else's network if it was configured like that. I don't think network operators who provide access to the Internet can realistically expect to control what their users do on the Internet, unless the network operator is also the administrator of those workstations.

Yeah, big difference between limiting access to your own network and limiting access to someone else's

I have a minor quibble with "my network". You should have the right to intercept the traffic originating or terminating at your devices, but not to intercept any traffic going between other people's devices just because it's on your network.

Okay, good point, and that's exactly why you isolate your networks. You don't want to be one configuration option from being wide open.

Well, I don't have issues with isolating it in my own network. A separate vlan plus some firewall rules seem to be a good mitigation.

I'm kinda concerned about other people though.


Yeah, no. I'm not letting anyone I don't know access any part of my network/connection.

That is something you can and always could disable. I would however not want someone with a buggy system in some of my networks which makes this choice have side-effects in some scenarios.

You might be right, technically, but I'd much rather have the situation where no parties are allowed to interfere and manufacturers have incentive to develop sharing-friendly systems (spread spectrum, etc.), than the situation where entities can block my Internet access for their own convenience.

Were that not the case, I could enter an arms race with my neighbors where we all compete for the strongest Wi-Fi blockers so that our own signal is strongest, perhaps to the point that one of us might get a business-class connection and start allowing paid access to it. "Too bad our block can't use Wi-Fi. Say, neighbor, for $100 a month I bet I could let you share mine."


I don't want other people to be able to change things on my computer. If my setup is causing problems on their end, they have my contact information and can tell me over traditional routes. An ISP can cut off my internet connection if they detect suspicious traffic.

The flip side is that on a local level (your own network) you want to be able to block all sorts of traffic for entirely good reasons.

Oh heck no. I have enough concerns about the security of those devices, I certainly don't want them hanging off the side of everyone's home network. I have enough expertise to put them on a separate network isolated from anything I care about, but the average punter doesn't.

Maybe, but my rule is: my home network, my rules. I can’t really do this invisibly anyways: any device I don’t control will get certificate validation errors.

And of course it's fine to block connections you don't recognize, or to whitelist connections in the first place. But I maintain that within a network of devices you own, the solution to untrustworthy devices on your network is to use more trustworthy devices, not to weaken internet standards for everyone else.

Messing how?

I mean, yes, it is a problem, but so is any networking device anywhere on the Internet — as soon as the traffic leaves my network, all bets are off.

The point is not to allow operator-managed crappy devices (like cable modems) into my network.


Damn that's terrifying.. I rather obfuscate my traffic inside my network down to a single node at home.

Well if you want to block everything that can't be inspected you will block a lot of common functionality.

The question about if it's in the network owners purview to inspect depends on the network and traffic. It could also be illegal privacy violations.


So make it active only for public wifi, or whatever is labeled as public network by the operating system or firewall? Certainly not all networks.

They might also want to block wifi networks with similar names, to avoid confusion.
next

Legal | privacy