3 ms·

Your comment suggests that it is related to users with older, pre-High Sierra directory entries. That is, upgraded rather than freshly installed machines that l

• Asmod4n 9y ago
  Works with El Capitan too.
• jsmthrowaway 9y ago
  No, I reproduced on freshly-installed High Sierra on two machines.
  • arghwhat 9y ago
    Odd. No reasonable amount of attempts would reproduce it on my wife's few-weeks-old work machine, where the root user was visibly disabled. The factors that differed from my laptop, where it worked until I set a root password, as that her machine was a fresh install, and she is not admin (a managed machine).
• AdamJacobMuller 9y ago
  No, sorry, I did not mean that or mean to imply it. I think the feature that caused this is related to upgrading pre-high-sierra user password hashes to high-sierra-style hashes. The fact that it works for situations where the password is null is a/the bug.
  • arghwhat 9y ago
    Ah, yes, but that is what I meant in suggesting that it was related to a High Sierra upgrade. If we assume that ShadowHashData hash was introduced in High Sierra, I thought it was safe to assume that a crypt hash would only origin from a pre-High Sierra install. Unless, of course, they are used as some form of default value (such as when disabling the user)...