undefined | Better HN

Skip to content

Top New Best Ask Show Jobs

undefined | Better HN

0 pointsOkGoDoIt8y ago0 comments

Seems to be something related to a backwards-compatibility code path for upgraded systems. According to multiple posts on this thread it only affects systems upgraded to High Sierra, not fresh installs. See https://news.ycombinator.com/item?id=15802622 for example. Adding extra layers for compatibility complicates testing and debugging. With this many eyes on it hopefully someone will be able to deduce exactly what's going on.

0 comments

nathancahill8y ago

My High Sierra is a fresh install, and it's affected.

princekolt8y ago

Yup. Can confirm. I installed it fresh on a VM from the downloaded installer and it is affected.

xer0x8y ago

My upgraded high sierra doesn't have this problem. The theory could be backwards. Anyways, this is stunning.

rtpg8y ago

But at one point a root account is created with an empty password right?

There's a specific line somewhere that's doing this, in theory.

Maybe they should have opted for "create `root` with unguessable password"

j / k navigate · click thread line to collapse