This is simply false. The link in the opening gives the actual text of the proposed law:

" Article 19. Speed Limiter Technology

28170. As used in this article, “intelligent speed limiter system” means an integrated vehicle system that uses, at minimum, the GPS location of the vehicle compared with a database of posted speed limits, to determine the speed limit, and electronically limits the speed of the vehicle to prevent the driver from exceeding the speed limit by more than 10 miles per hour."

Hmm. Is this something you type in manually? I was operating under the assumption it was a hard-coded URL.

626 IP addresses is a minuscule % of all computers running Windows (what do you think, 10s of billions?), yet the fact that these computers consistently use the wrong domain suggests there's something different about those computers: likely they had bad RAM (or bad cache). If that's the case then the severity of such an attack must be compared to the severity of having bad RAM to begin with, e.g. writing bad data to random places on your hard drive. ECC RAM should fix this problem, though that's rare on desktops; a simpler solution would be to simply use SSL for everything and solve the entire problem completely. But either way it's a rare problem. It's an interesting study, but limited practical application. It'd be a lot more interesting if they got a radiation source and cranked it up to simulate long periods of time/many systems running in parallel. Then they could measure what the probability of this occurring is and determine if it's worth trying to solve or just ignore.

I'm unsure what cable has to do with Fox, ABC, CBS, et cetera. The only cable network listed in the summary was Disneyâ¦

Yes, I was giving it to you personally because you kept using your weird personal configuration in all of your examples.

A rational person would just use Family Sharing and be done with it.

It doesn't "automatically sync" it. Like many other things involving Handoff, it sets a promise. It tells devices in close proximity that there is data available.

Said data isn't actually transferred until used. This significantly reduces the amount of bandwidth (and thus power) involved when no other device actually cares about the Handoff data being advertised.

There is a help button in the dialog that appears when an app is missing a signature that tells you *exactly* how to permit the launch. Is it too much to expect a user to know to click the help button?

Again, why aren't you using Family Sharing? There's zero reason to be sharing your iCloud account. Especially since it gives everyone access to to things like email.

It also seems you need to read up on Handoff. The range of Handoff is about 10 meters (33 feet). All devices must be in this range for Handoff to work.

Handoff (which was added in iOS 8 and Mac OS X 10.10) also shares which webpage you are viewing and which apps you are using to devices logged in with the same Apple ID and in that range. So you have no legitimate reason to suddenly complain about the Universal Clipboard all of a sudden.

If you don't like the security of Handoff due to ignorance, then disable Handoff on your devices. Hell, if one specific shared device must be logged in with the same Apple ID (because you don't know better), then disable Handoff solely on that device.

Bad article is bad. It initiates a man-in-the-middle attack for network requests.

On Windows, this gets NTLM for a pass-the-hash attack if a network share is mounted or set to automatically connect.

The Transmission app uses the Sparkle Software Update mechanism. Sparkle uses certificate pinning to prevent exactly this type of attack. The auto-updater will not permit an application to be updated if the update is signed by a different entity.

So this malware only affected people that manually downloaded the app from the Transmission website.

I read the article.

The Dev ID used to sign it was not Transmission's Dev ID.

The build machine wasn't compromised. The Transmission web server was compromised and the Transmission binary was replaced on the server.

This has absolutely nothing to do with Xcode.

The SSO bug in Ingress was fixed on April 19th. Not enough people use Ingress to notice beforehand, I guess. And Niantic was owned by Google until mid 2015, so they always had access.

If you deny the permission on Android, the Pokémon GO will then ask you to log in manually with Google account credentials. That process also creates the OAuth token with the overzealous scope.

The fact is, all it is trying to do is activate a single sign on authentication method.