Control8894

Of course not. They removed it because it saves them money, thus increasing their profit margins.

Should is not does, and also LOL @ anycast for some SMB's internal networking. Yeah, good luck with that bud.

> when it's broken it's broken cuz you broke it

No duh, but that doesn't make it any less broken.

This is a very poor straw man.

In IPv6 world you wouldn't get 2001::/112, you'd get 2001:1234:5678:90ab::/48. So your building might actually be at best something like 2001:1234:5678:90ab:1::.

It doesn't matter if the wifi is encrypted or not. All that matters is that you share the network with an attacker. You can ARP poison just fine, encrypted or open, wifi or wired.

Erm... no.

Don't worry, you're only allowed to see responses to stuff if you're logged in. Hope they don't ban you from having an account for daring to @ musk.

Well, they are really wireless.

Wireless costs more because suddenly you need to deal with antennas and RF and whatever. Adding a wire back on top of that doesn't magically make it cost less again.

Nothing has taken its place, and you didn't even get anything cheaper. The only one who won was Apple.

> These are all big companies out to make a buck.

!= not bad

> The basic idea is that whenever you find yourself memorising an IPv4 address, there's a failure somewhere. Possibly at policy and governance level.

Sorry, but that's a load of manure. It's not just about memorizing.

People break their DNS so often that it's a meme.

Not everything automatically does a reverse lookup on every address it sees, and when it does rDNS could quite easily be broken.

So when you need to figure out if a device is in the same building as you, is it easier to say "1.2.3. - oh, that's my building" or "1234:5678:90ab:cdef:1234:5678:90ab:: - oh, that's my building"?

> Hell, if you run a modern Microsoft domain (think newer than Windows Server 2008), you're hamstringing yourself if your network is IPv4 only, because since NT6 Windows is IPv6 first system, and there are indeed some corporate features that do not work if services aren't available over v6.

Like? I mean I avoid using MS where possible so I probably just haven't seen it but I'm quite curious what's dependent on it.

> for example, an attacker within range of an Wi-Fi access point hosting a network without encryption

The monkey in the middle doesn't get to "relay" anything either, but he can sure see it going over his head.

Perhaps, but the other realistic option is a self-signed cert. Since browsers refuse to implement any kind of TOFU or otherwise 'trust history', a self-signed cert is pretty much exactly equivalent to no TLS at all.

> One day, an intermediary system is hijacked which carries your traffic, and your weather information can be rewritten in transit. Your credibility for providing outstanding data is compromised when you start serving up weather information that predicts sunny skies when a tornado watch is in effect.

Why would they want to do that? Is your weatherman always right?

> Additionally, you have now leaked information related to the traffic of your users. Even if the request is just vanilla HTTP-only, an adversary can see that your users from one region are interested in the weather and can start building a map of that traffic.

Ah, yes, people are interested in the weather. Wow!

Of course, they could get the same info from observing that users are connecting to the IP address of a weather API provider.

> They also inject a javascript payload into your traffic that starts computing bitcoin hashes and you are blamed for spreading malware.

Got there eventually. Crappy ISPs.