Apple Announces a Mac Event On October 27, Says 'Hello Again'

Apple announced on Wednesday that it will be holding an event on October 27. The tagline of the invite is, "hello again." This suggests that the rumors are true and that the company will indeed announce a fleet of new Mac products. The original Mac was introduced with the word "hello" in 1984. People have waited for years now for Apple to refresh its Macbooks -- some of the products in Mac line haven't received an update in 1000 days. Many expert even said earlier that Apple should stop selling the old MacBooks. The new MacBooks are expected to ship with Intel Skylake processor and a contextual keyboard. Not long ago, the company was also exploring the idea of a MacBook without a 3.5mm audio jack.

Comments

Pretty Dang Exciting

[tsqr]

They're thinking about dropping the headphone jack. Maybe the new MacBook will be waterproof.

Re: mac os now locked down to IOS levels and

[tlhIngan]

True, it's not quite to iOS levels. But you still can't run code that isn't "blessed" by Cupertino and you can't turn that off: macOS removed the ability to disable Gatekeeper. And recent versions of OS X/macOS are "rootless" meaning the user (who clearly is no longer the owner) can't even change "system files" as root. Also no way to turn this off.

You can run code that isn't blessed by Cupertino. In fact, Gatekeeper defaults to signed and Mac App Store apps. Signed apps are apps that a developer makes that have been signed by a key generated by Apple. Apple doesn't get a chance to review those apps - the developer writes it, signs it, and releases it. Apple has revoked a few keys before, because they were used to spread malware (because even developers can't be bothered to secure their keys, so those keys got stolen).

And it's possible to bypass gatekeeper quite easily. First off, it only affects "unsafe" distribution methods, like software downloads from the Internet. So if you install an app from say, a CD, it works just fine (since these will be older, they will be unsigned). And code that the compiler produces is also trusted, presumably you've verified that yourself. Another way is it relies on extended attributes, so clearing those also bypasses it.

Or you can give an unsigned app permission to run permanantly, requiring little more than a few extra seconds to press the Ctrl key and clicking Open.

For file protection, you can disable it easily enough, though it requires a trip through the recovery mode console Even Wikipedia has the basic command you need to disable it.

Honestly, the options are there to take full control of the machine, if you want to. For the vast, vast majority of users, including power users, leaving it at the defaults is just fine.