So this is basically saying that we can no longer depend on the OS to protect us against privilege escalation attacks. The bad guys will have to concentrate on breaking out of VMs or, at least in this case, attacking through the access that the Edge VM has to system resources.

No modern OS is immune to privilege escalation attacks. Even a formally verified OS would probably still be susceptible to them due to unexpected interactions. Never mind hardware based attacks such as race conditions and rowhammer. If someone is dedicated enough, and has enough resources, sooner or later they'd find a chink in the armor.

Instead you try to do the best you can, and then you layer on defense in depth on top of that. If someone is going to break in, then you can at least slow them down and force them to fight another kind of complexity.

No, that's not what responsible disclosure is.

It's a shame the Cisco blog is linked second, because it's a great (yet short) read.

Since the end of last month one of my very low volume email accounts has been on the receiving end of a new spam campaign trying to give me malware. The emails I've received exactly match the emails in Cisco's graph So it's neat to see what's behind it - in this case the Necurs botnet running at full tilt.

Considering this account was receiving virtually zero spam before, it's definitely a major uptick in spam.

Interesting. Do you know how long ago that study was done? I"m curious if smaller manufacturing geometries have made newer processors more vulnerable.

To make it even harder to stop.

Laptops have always been pretty fucky.

Ceph is software not IaaS.

What TFS doesn't do a good job of explaining is that with Swift 3, Apple has essentially forked the project into two parts. Besides the newer version 3, Apple is also continuing to develop/support Swift 2.x. The already-released Swift 2.3 is Swift 3's counterpart for developers who would like to stick with Swift 2.x code.

Swift 2.3 is a minor update from Swift 2.2.1. The primary difference between Swift 2.2.1 and Swift 2.3 is that it is intended to be paired with Apple's macOS 10.12, iOS 10, watchOS 3, and tvOS 10 SDKs. It also updates the underlying LLVM and Clang versions to match with those in the Swift 3 compiler.

I don't imagine Apple will support Swift 2.x forever. But for the time being, Swift 3 is only as source-breaking as you want it to be. Developers who need Swift 2 compatibility can roll on with 2.3.

Emacs users have more time for commenting on slashdot.
What else are they going to do while waiting for Emacs to load?

Meanwhile vi users have to post multiple times to make up for their small user base. Otherwise no one would remember that poor vi exists.

Never, but the point is you can't even use the special gloves to do it.

Tests have shown that using gloves designed for touch screens will get an iPhone 6s Plus to unlock but not an iPhone 7 Plus.

"Well you shouldn't have left your car unlocked if you didn't want me stealing your shit"?

That's entirely your and your kids fault, and collections stays on for 7.5 years.

Don't know about you, but my daughter's school has two PokeStops and a PokeGym

One of Snowden's complaints (and the chief reason, according to him, that he has not returned to the US to stand trial) is that he has been charged on two counts under the Espionage Act, which prevents him from defending himself in open court. Presumably you, too, would prefer that he was allowed to make a public interest defense?

My preference is to follow the letter of the law. If that includes charges under the Espionage Act, then so be it.

A pardon is the executive - the leader of the people - granting you leniency for what you did. However to be excused for your actions, one should first admit to them.