Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
How do you know it's a bug?

What if this always existed in some obscure command form that no one would ever do, save for those that know about it?

Just sayin'
 
It really seems like the 2017 releases are among the worst Apple has ever had. Flagship feature on the new Watch? Practically DOA, to the point that they wouldn't even sell them in stores until they fixed it. Can't use Outlook accounts in iOS. Key third party apps on the Mac? Totally boned. Can't format blank disks. Your data's root password handed out like candy.

Just a completely joke from start to finish.
 
No need to release new OS every year. Better release them once 2 years with better QA testing.

Especially in the macOS space. A platform many use for their work not just to check instagram and Facebook

Intel has been moving at snail like pace for many years, and redesigns only come about once every 4 years or so.

But even iOS I think major updates, that don't offer tons of features butnopen the door to hindered experience and lots of bugs, don't need to be pegged to yearly cadences

People are way more excited to get new gear than a new control center


Too bad "courage" only extended to removing the headphone jack and not disrupting stockholders timeline expectations. Timmy doesn't have the courage for that
 
eah, but come on... resources are resources... at the end of the day when something this ridiculous happens it's not unreasonable for people to question some of Apple's priorities and/or allocation of resources and focus. If they hired more people to concentrate on security and testing so things like this didn't happen, and we had to wait a little longer for more emoji and other less critical features (however fun for users), would that be a bad thing?

Animoji are an iOS feature. They were most likely developed by a programmer killing some time while waiting for a build or blowing off some steam. The majority of the heavy lifting was there anyway because of FaceID. It's literally a skin to the 3D mesh used for authentication. A manager probably saw it and said "Hey, that's kinda cool. Why don't we put it in as a neat trick?" Disk Utility is part of macOS. It's part of a different (albeit related) product. Taking developer away from Animoji to focus on a completely different product would likely cause resentment and not solve anything.
 
  • Like
Reactions: mudflap
Oops. Something this obvious made it past all the alpha and beta testing? Is any real testing actually being done, or have software testing tools become so automated that things which are unimportant to a machine (doesn't cause a crash or a buffer overflow) but are important to people being completely overlooked?
 
Apple seriously needs to start hiring better QA engineers....

QA engineers are brain dead. They would never catch something like this to begin with. They need more security engineers (not the highschool ones with the CERTs but CS/CE with a security background).
 
While this is easily fixed, the bigger picture is hackers might be able to just archive this version of Disk Utility and use it into perpetuity to unlock any encrypted drive in the future. Apple actually needs to change the encryption/password mechanism, which has all sorts of compatibility issues. This is a bigger deal than I think people even realize.

Has anyone verified this is only on AFPS volumes? If standard HFS volumes act the same way, this is a huge problem, as they would all have to re-encrypted.
 
Last edited:
Animoji are an iOS feature. They were most likely developed by a programmer killing some time while waiting for a build or blowing off some steam. The majority of the heavy lifting was there anyway because of FaceID. It's literally a skin to the 3D mesh used for authentication. A manager probably saw it and said "Hey, that's kinda cool. Why don't we put it in as a neat trick?" Disk Utility is part of macOS. It's part of a different (albeit related) product. Taking developer away from Animoji to focus on a completely different product would likely cause resentment and not solve anything.

I'm not saying move Employee A from Animoji or whatever to work on Disk Utility. I'm saying Add (new) Employee C to Employee B who was working on Disk Utility anyway. Or add to internal testing. Or both. They can afford it.
 
  • Like
Reactions: fairuz
TBF, is it safe to blame QA? I know in some places, they get overruled by management even though they tell them that a release ain't ready yet.

Does showing the password itself as the hint count as a password hint? ;)
It would be cool if trivia night offered the answer to a question when we ask for a hint :D
 
Does showing the password itself as the hint count as a password hint? ;)

Exactly, I don't get what all the fuss is about. It does exactly what password hints usually do:
  1. Provide information so you can recall the password
  2. Weaken security
It excels in both, so it is probably the best possible hint. And maybe it will make some people think about the concept, although I doubt it.
 
  • Like
Reactions: TheWatchfulOne
Brazilian software developer Matheus Mariano appears to have discovered a significant macOS High Sierra vulnerability that exposes the passwords of encrypted Apple File System volumes in plain text in Disk Utility.

In other words this person could well be a hacker as it is only hackers who go searching for such exploits.

No denial it is serious but do not lose sight of the bigger picture. macOS is far more secure than Windows will ever be.

The only platform more secure than macOS is Linux and hackers go searching for exploits there too.
 
I’m not at my machine right now - would be interesting to see if the bug shows itself when logged in as a separate user.

It’s a bug. Should have been caught. It wasn’t.

On the grand scheme of things this isn’t a dealbreaker.

It’ll get sorted. I’m pleased they took a good look at Disk Utility.

F
 
Holy ****, why in gods name is it storing the password in plain text?

And for anyone who is saying it doesn't affect many users, not a big deal, bugs happen, blah blah blah: ****. You would be crucifying Google or Microsoft if they did this, and rightfully so. Take off the Apple colored glasses and stop making excuses for them, because there is not a single excuse in the world that can make this okay.
 
This is clearly not merely a bug in Disk Utility itself - if a password is encrypted, then NO PROGRAM CAN EVER DISPLAY IT - all you can do is encrypt a user given password and compare to see if the encrypted versions match. The fact that Disk Utility COULD show the password means it was NOT ENCRYPTED. (Or else stored somewhere, or the NSA demanded a back door or something.)

Disk Utility has actually revealed a core security issue here!

Nope.

When you create an encrypted volume with a password and a hint, two "store text" functions are called.

One takes the *password* and does all the nifty encryption stuff to make sure it can't be recovered (and uses it to generate a key or key pair for the actual encryption, etc).

The other one takes the *hint* and stores it as plaintext somewhere so it can be displayed when attempting to decrypt the volume.

Someone made a copy-pasta error (or similar) and accidentally made the "store hint" function store the contents of the password box instead of the hint box.

No huge "all encrypted drives have their password stored as plaintext/Apple sux at crypto" issue here.

A very, very simple mistake, with very, very big consequences for a very small number of people.

It *only* affects people who create an encrypted volume with a hint using Disk Util. It doesn't affect the standard full disk encryption, or volumes created by the command line utility.
 
To be clear, the linked Twitter thread suggests that this is a Disk Utility bug, where if you create a password-protected volume in Disk Utility it inadvertently sets the hint to the password itself. It's not a bug that allows the password itself to be uncovered via other means, which is what I originally thought this meant and which was surprising to me since the only way to do that should be computationally expensive brute-force methods (the data itself is encrypted with the password; it's not just artificially protected by one, and it shouldn't be possible to "reverse lookup" the password by any true means).

More than an disk utility bug. Both the hint and password should be encrypted before being stored with separate keys. This prevents a piece of code from getting the hint in clear text. The key to decrypt the hint should be something else the user has to know.
 
For clarification: this only affects Macs running High Sierra, correct?
 
I don't understand why Apple is so terrible at software.

Get computer security right is a tough problem. Even so called "security experts" get it wrong every day. Things we thought made sense, such as password expiration times, turn out to be themselves major causes of security issues. Same with requiring "strong" password with Upper lower case, special characters, etc.
[doublepost=1507221200][/doublepost]
For clarification: this only affects Macs running High Sierra, correct?

That is what the article says.
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.