IPv6 currently has fewer prefixes, but that won't always be the case, and it uses the same TCAM space as everything else. Giving IPv4 a little more space means taking it from something else -- by default that's IPv6 space.

ABSOLUTELY FUCKING WRONG IPv6 addresses are 128bits with a 128bit mask. Every bit counts.

You have fallen to a classic blunder. Just because that bullshit SLAAC requires a 64bit prefix does NOT mean the whole damned world is 64+64. This idiot-assumption makes your entire product line completely useless; you have now bankrupt your company.

RTFA. They downloaded the installable firmware images for many devices and found a self-signed certificate in some of them. That is not a per-device-unique anything. Every device loads the same blob, and has the same certificate. They aren't even competent enough to get the device to generate it's own certificate. (which could have it's own issues, but at least it has a chance of being different from any other device.)

The issue is that it's embedded in the firmware, which means it's the same damned certificate on every device. Hack it once, and every one of them is now hacked. (remember the issue with debian and sshd keys? there were only a handful of keys because they were generated with a guessable random number (seconds from boot) on the first boot.)

Right, because bugs in the cannot-be-replaced version 1.0 firmware will never come back to haunt you. (read: force it to fallback to 1.0, and bob's your uncle.)

And the absence of any pesky gotta-show-you-the-code GPL cruft has nothing to do with it.

There are a few "hacks" that do that in linux as well. Basically the network driver is in userland, with a kernel shim to handle DMA and IRQ which isn't available to userland. (in fact, I use that same mode to deal with broadcom SoC's -- not for network traffic, just to configure and monitor) There are advantages to pulling packets direct to userland.

Right, because they all put $100k worth of tech in a scope for $4k, and get the rest of it when you pay to use that tech. The hardware costs what it costs; if they can afford to put dormant hardware in the thing, then they're just screwing over their customers. It's like a lot of networking vendors being dicks by including a 10G interface put only allowing to link at 100M unless you pay them $$$$$. Or a fiber channel switch with 32 ports, but only 8 enabled in software.

Of course, you have to know exactly where in the eeprom to put the SKU's. (which wouldn't take long to figure out, btw.)

Indeed. Somewhere circa 1997(?) -- It was a dark day for the internet: people too stupid to be on the internet were now pooping all over it.

Did you look at the picture? A magnet is what's holding the "heavy" plate. The worker's hands are merely guides; they aren't supporting the weight at all. (assuming it was balanced when it was lifted.)

It's chain of custody. And it only applies to law enforcement. Tamper with evidence is illegal all the time.

The problem/question here is why was Google nosing through his email in the first place / what right do they have to do so?

Right, because Verizon doesn't do this, or AT&T, or Sprint, or T-mobile. Bottom line, every major cellular operator in the US does this.

Verizon was spanked litely for this. Yet they still do it. However, they aren't allowed to stop you from loading apps to enable it anyway. Except on an Apple device, where the provider lock cannot be broken on a stock device.

BS. You had to root it to get CM loaded. You could've stopped with rooting the stock firmware and used any of the HUNDREDS of apps and tweaks to disable the vendor bloat and security. (are we talking Samsung and KNOX perhaps. There are entire corners of the internet devoted to that shit.)

By "customizing" he means "loaded CM on it" (or someother AOSP based build) that doesn't know how to be efficient.