are you affected?

  • is your sshd running on musl? (alpine, openwrt, buildroot, yocto)
  • is it not using pam? alpine’s openssh-server doesn’t by default, or maybe you set UsePAM no
  • are password logins still on? they are by default
  • is there an account with just * as its password? key-only users, ldap users, root on alpine
  • and some other account with a real password?
  • then that * account takes any password between 257 and 1024 characters

on alpine’s official aws and azure images that’s the default alpine user, and it has passwordless doas. so it’s root

on debian, ubuntu, fedora or anything else with glibc? going through pam? dropbear? openbsd? you’re fine

  • irotsoma@piefed.blahaj.zone
    link
    fedilink
    English
    arrow-up
    1
    ·
    34 minutes ago

    People use * as an account password, or sysadmins allow that? I’d never allow that on any system or service of mine. No surprise, like most of these LLM discovered issues in the media lately, it hasn’t come up before. 💯 Good they’re getting fixed, but nothing so far has really been that urgent to fix for me.

    • smiletolerantly@awful.systemsOP
      link
      fedilink
      English
      arrow-up
      1
      ·
      4 minutes ago

      No, \* is being put as a hash of a password, originally precisely because that would mean no actual hash (over any input) ever matches it.